sensors Mode-S transponder
151D6D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73069 · BOEING 737-400
- Hex
- 151D6D
- Octal
- 05216555
- Decimal
- 1,383,789
- Country
- RU
- Tail
- RA-73069
- Type
- B734
- Flights observed
- 192
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 27m ago
Last known position
Country allocation
The ICAO 24-bit address 151D6D falls within the block assigned to Russia (RU) by ICAO Annex 10, Volume III. Every aircraft registered in Russia receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA103 | - | 23 | 2026-07-13 |
| UTA185 | - | 14 | 2026-07-09 |
| UTA186 | UTair Aviation | 11 | 2026-07-04 |
| UTA104 | UTair Aviation | 10 | 2026-07-11 |
| UTA152 | UTair Aviation | 9 | 2026-06-14 |
| UTA6109 | UTair Aviation | 8 | 2026-05-29 |
| UTA6110 | - | 6 | 2026-06-15 |
| UTA6108 | UTair Aviation | 6 | 2026-06-27 |
| UTA574 | UTair Aviation | 6 | 2026-04-22 |
| UTA573 | UTair Aviation | 6 | 2026-04-21 |
| UTA375 | UTair Aviation | 6 | 2026-05-27 |
| UTA398 | - | 5 | 2026-04-19 |
| UTA397 | UTair Aviation | 5 | 2026-04-22 |
| UTA6107 | UTair Aviation | 4 | 2026-06-15 |
| UTA576 | - | 4 | 2026-04-16 |
| UTA575 | UTair Aviation | 4 | 2026-04-16 |
| UTA491 | - | 4 | 2026-07-06 |
| UTA376 | UTair Aviation | 4 | 2026-05-27 |
| UTA363 | UTair Aviation | 3 | 2026-06-12 |
| UTA151 | UTair Aviation | 3 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UTA103 | - | Jul 13, 04:35 UTC | Jul 14, 03:10 UTC | 22h 35m |
| 2026-07-12 | UTA103 | - | Jul 12, 20:25 UTC | Jul 13, 04:35 UTC | 8h 10m |
| 2026-07-12 | UTA509 | TJM → MRV | Jul 12, 15:55 UTC | Jul 12, 16:20 UTC | 25m |
| 2026-07-12 | UTA510 | - | Jul 12, 07:40 UTC | Jul 12, 07:50 UTC | 10m |
| 2026-07-11 | UTA104 | UFA → SGC | Jul 11, 08:40 UTC | Jul 12, 03:15 UTC | 18h 35m |
| 2026-07-11 | UTA103 | - | Jul 11, 04:20 UTC | Jul 12, 03:15 UTC | 22h 55m |
| 2026-07-10 | UTA103 | - | Jul 10, 13:20 UTC | Jul 11, 08:40 UTC | 19h 20m |
| 2026-07-10 | UTA103 | - | Jul 10, 08:30 UTC | Jul 11, 04:25 UTC | 19h 55m |
| 2026-07-10 | UTA103 | - | Jul 10, 04:35 UTC | Jul 10, 16:20 UTC | 11h 45m |
| 2026-07-09 | UTA104 | UFA → SGC | Jul 9, 16:20 UTC | Jul 10, 13:20 UTC | 21h 0m |
| 2026-07-09 | UTA104 | UFA → SGC | Jul 9, 13:15 UTC | Jul 10, 08:30 UTC | 19h 15m |
| 2026-07-09 | UTA185 | - | Jul 9, 08:20 UTC | Jul 10, 04:35 UTC | 20h 15m |
| 2026-07-08 | UTA185 | - | Jul 8, 23:50 UTC | Jul 9, 16:25 UTC | 16h 35m |
| 2026-07-08 | UTA477 | - | Jul 8, 20:15 UTC | Jul 9, 16:25 UTC | 20h 10m |
| 2026-07-08 | UTA104 | UFA → SGC | Jul 8, 16:35 UTC | Jul 9, 13:15 UTC | 20h 40m |
| 2026-07-08 | UTA6184 | NOJ → UFA | Jul 8, 11:55 UTC | Jul 9, 08:25 UTC | 20h 30m |
| 2026-07-06 | UTA1492 | - | Jul 6, 23:30 UTC | Jul 7, 04:30 UTC | 5h 0m |
| 2026-07-06 | UTA491 | - | Jul 6, 20:25 UTC | Jul 6, 20:50 UTC | 25m |
| 2026-07-06 | UTA491 | - | Jul 6, 11:55 UTC | Jul 6, 18:50 UTC | 6h 55m |
| 2026-07-05 | UTA482 | - | Jul 5, 17:25 UTC | Jul 5, 17:35 UTC | 10m |
| 2026-07-05 | UTA481 | - | Jul 5, 05:45 UTC | Jul 5, 05:55 UTC | 10m |
| 2026-07-04 | UTA186 | NUX → UFA | Jul 4, 04:35 UTC | Jul 4, 16:35 UTC | 12h 0m |
| 2026-07-03 | UTA186 | NUX → UFA | Jul 3, 16:20 UTC | Jul 4, 13:50 UTC | 21h 30m |
| 2026-07-03 | UTA186 | NUX → UFA | Jul 3, 13:05 UTC | Jul 4, 09:15 UTC | 20h 10m |
| 2026-07-03 | UTA186 | NUX → UFA | Jul 3, 08:20 UTC | Jul 4, 04:40 UTC | 20h 20m |
| 2026-07-03 | UTA186 | NUX → UFA | Jul 3, 04:20 UTC | Jul 3, 16:25 UTC | 12h 5m |
| 2026-07-02 | UTA186 | NUX → UFA | Jul 2, 16:20 UTC | Jul 3, 13:15 UTC | 20h 55m |
| 2026-07-02 | UTA186 | NUX → UFA | Jul 2, 13:20 UTC | Jul 3, 13:15 UTC | 23h 55m |
| 2026-07-02 | UTA104 | UFA → SGC | Jul 2, 08:35 UTC | Jul 3, 04:25 UTC | 19h 50m |
| 2026-07-01 | UTA104 | UFA → SGC | Jul 1, 17:20 UTC | Jul 2, 16:25 UTC | 23h 5m |
| 2026-07-01 | - | - | Jul 1, 16:55 UTC | Jul 2, 13:20 UTC | 20h 25m |
| 2026-07-01 | UTA103 | - | Jul 1, 04:15 UTC | Jul 1, 15:10 UTC | 10h 55m |
| 2026-06-30 | UTA103 | - | Jun 30, 16:45 UTC | Jul 1, 15:10 UTC | 22h 25m |
| 2026-06-30 | UTA186 | NUX → UFA | Jun 30, 13:55 UTC | Jul 1, 04:20 UTC | 14h 25m |
| 2026-06-30 | UTA185 | - | Jun 30, 08:25 UTC | Jul 1, 04:20 UTC | 19h 55m |
| 2026-06-29 | UTA185 | - | Jun 29, 23:54 UTC | Jun 30, 16:45 UTC | 16h 50m |
| 2026-06-29 | UTA185 | - | Jun 29, 12:20 UTC | Jun 30, 08:30 UTC | 20h 11m |
| 2026-06-28 | 6118 | - | Jun 28, 15:05 UTC | Jun 29, 12:20 UTC | 21h 15m |
| 2026-06-28 | 6118 | - | Jun 28, 00:39 UTC | Jun 28, 15:09 UTC | 14h 30m |
| 2026-06-27 | UTA6108 | IAA → UFA | Jun 27, 15:10 UTC | Jun 28, 00:45 UTC | 9h 35m |
| 2026-06-26 | UTA6108 | IAA → UFA | Jun 26, 23:44 UTC | Jun 27, 15:14 UTC | 15h 30m |
| 2026-06-26 | UTA1492 | - | Jun 26, 18:15 UTC | Jun 27, 15:14 UTC | 21h 0m |
| 2026-06-26 | UTA514 | AER → TJM | Jun 26, 07:39 UTC | Jun 26, 16:24 UTC | 8h 45m |
| 2026-06-26 | UTA491 | UFA → AER | Jun 26, 05:24 UTC | Jun 26, 05:55 UTC | 30m |
| 2026-06-24 | UTA492 | AER → UFA | Jun 24, 12:20 UTC | Jun 24, 13:50 UTC | 1h 30m |
| 2026-06-23 | UTA491 | UFA → AER | Jun 23, 14:29 UTC | Jun 24, 10:35 UTC | 20h 5m |
| 2026-06-23 | UTA6108 | IAA → UFA | Jun 23, 00:45 UTC | Jun 23, 14:35 UTC | 13h 50m |
| 2026-06-22 | UTA476 | KRR → UFA | Jun 22, 13:29 UTC | Jun 23, 00:45 UTC | 11h 15m |
| 2026-06-21 | UTA475 | UFA → KRR | Jun 21, 21:14 UTC | Jun 22, 11:14 UTC | 14h 0m |
| 2026-06-21 | UTA510 | MRV → TJM | Jun 21, 08:15 UTC | Jun 21, 08:25 UTC | 10m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the RA-73069 page for operator, model, and routing details .