sensors Mode-S transponder
151D6B
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73067 · BOEING 737-400
- Hex
- 151D6B
- Octal
- 05216553
- Decimal
- 1,383,787
- Country
- RU
- Tail
- RA-73067
- Type
- B734
- Flights observed
- 130
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 18:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 151D6B 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 |
|---|---|---|---|
| UTA491 | UTair Aviation | 13 | 2026-07-26 |
| UTA103 | - | 11 | 2026-07-16 |
| UTA576 | - | 10 | 2026-07-23 |
| UTA575 | UTair Aviation | 9 | 2026-07-23 |
| UTA186 | UTair Aviation | 7 | 2026-07-14 |
| UTA248 | UTair Aviation | 6 | 2026-06-12 |
| UTA185 | - | 6 | 2026-07-14 |
| UTA363 | UTair Aviation | 5 | 2026-07-23 |
| UTA492 | UTair Aviation | 4 | 2026-07-21 |
| UTA478 | - | 4 | 2026-07-17 |
| UTA475 | - | 4 | 2026-07-19 |
| UTA398 | - | 4 | 2026-07-09 |
| UTA374 | - | 4 | 2026-06-25 |
| UTA364 | UTair Aviation | 4 | 2026-07-23 |
| UTA6128 | - | 3 | 2026-07-07 |
| UTA6114 | - | 3 | 2026-07-13 |
| UTA6110 | - | 3 | 2026-06-19 |
| UTA397 | - | 3 | 2026-07-09 |
| UTA373 | - | 3 | 2026-06-25 |
| UTA514 | - | 2 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UTA1492 | - | Jul 26, 17:45 UTC | Jul 26, 18:15 UTC | 30m |
| 2026-07-26 | UTA491 | UFA → AER | Jul 26, 08:25 UTC | Jul 26, 16:00 UTC | 7h 35m |
| 2026-07-25 | UTA493 | UFA → GDZ | Jul 25, 22:10 UTC | Jul 26, 06:30 UTC | 8h 20m |
| 2026-07-25 | UTA513 | TJM → AER | Jul 25, 11:40 UTC | Jul 25, 20:40 UTC | 9h 0m |
| 2026-07-24 | UTA491 | UFA → AER | Jul 24, 16:30 UTC | Jul 25, 05:30 UTC | 13h 0m |
| 2026-07-24 | UTA491 | UFA → AER | Jul 24, 08:20 UTC | Jul 25, 05:30 UTC | 21h 10m |
| 2026-07-23 | UTA363 | VKO → UFA | Jul 23, 21:40 UTC | Jul 23, 21:55 UTC | 15m |
| 2026-07-23 | UTA363 | VKO → UFA | Jul 23, 18:15 UTC | Jul 23, 18:55 UTC | 40m |
| 2026-07-23 | UTA576 | - | Jul 23, 15:30 UTC | Jul 23, 15:55 UTC | 25m |
| 2026-07-23 | UTA576 | - | Jul 23, 12:45 UTC | Jul 23, 14:50 UTC | 2h 5m |
| 2026-07-23 | UTA575 | VKO → KRR | Jul 23, 07:15 UTC | Jul 23, 10:35 UTC | 3h 20m |
| 2026-07-23 | UTA364 | UFA → VKO | Jul 23, 04:55 UTC | Jul 23, 05:10 UTC | 15m |
| 2026-07-23 | UTA364 | UFA → VKO | Jul 23, 03:30 UTC | Jul 23, 04:10 UTC | 40m |
| 2026-07-21 | UTA492 | AER → UFA | Jul 21, 10:20 UTC | Jul 21, 10:40 UTC | 20m |
| 2026-07-21 | UTA491 | UFA → AER | Jul 21, 08:00 UTC | Jul 21, 08:30 UTC | 30m |
| 2026-07-20 | UTA491 | UFA → AER | Jul 20, 18:00 UTC | Jul 21, 06:20 UTC | 12h 19m |
| 2026-07-20 | UTA476 | - | Jul 20, 08:55 UTC | Jul 20, 16:00 UTC | 7h 5m |
| 2026-07-19 | UTA475 | - | Jul 19, 16:35 UTC | Jul 20, 06:50 UTC | 14h 15m |
| 2026-07-17 | UTA478 | - | Jul 17, 23:25 UTC | Jul 18, 16:45 UTC | 17h 21m |
| 2026-07-17 | UTA478 | - | Jul 17, 20:29 UTC | Jul 18, 16:45 UTC | 20h 16m |
| 2026-07-17 | UTA478 | - | Jul 17, 13:20 UTC | Jul 18, 00:00 UTC | 10h 40m |
| 2026-07-17 | UTA478 | - | Jul 17, 04:39 UTC | Jul 18, 00:00 UTC | 19h 20m |
| 2026-07-16 | UTA103 | SGC → UFA | Jul 16, 16:15 UTC | Jul 17, 13:25 UTC | 21h 10m |
| 2026-07-16 | UTA103 | - | Jul 16, 04:30 UTC | Jul 16, 16:19 UTC | 11h 50m |
| 2026-07-15 | UTA103 | - | Jul 15, 13:10 UTC | Jul 16, 04:35 UTC | 15h 25m |
| 2026-07-15 | UTA103 | - | Jul 15, 04:25 UTC | Jul 15, 16:25 UTC | 12h 0m |
| 2026-07-14 | UTA104 | - | Jul 14, 17:20 UTC | Jul 15, 16:25 UTC | 23h 4m |
| 2026-07-14 | UTA186 | NUX → UFA | Jul 14, 14:50 UTC | Jul 15, 13:10 UTC | 22h 19m |
| 2026-07-14 | UTA185 | - | Jul 14, 10:05 UTC | Jul 15, 04:30 UTC | 18h 24m |
| 2026-07-14 | UTA103 | - | Jul 14, 07:20 UTC | Jul 15, 04:30 UTC | 21h 9m |
| 2026-07-13 | UTA103 | - | Jul 13, 23:05 UTC | Jul 14, 17:25 UTC | 18h 20m |
| 2026-07-13 | UTA6114 | - | Jul 13, 17:40 UTC | Jul 14, 14:55 UTC | 21h 15m |
| 2026-07-12 | UTA6114 | - | Jul 12, 21:40 UTC | Jul 13, 17:45 UTC | 20h 5m |
| 2026-07-12 | UTA185 | - | Jul 12, 08:25 UTC | Jul 12, 21:40 UTC | 13h 15m |
| 2026-07-11 | UTA363 | - | Jul 11, 21:35 UTC | Jul 12, 13:15 UTC | 15h 40m |
| 2026-07-11 | UTA576 | - | Jul 11, 17:10 UTC | Jul 11, 19:55 UTC | 2h 45m |
| 2026-07-11 | UTA575 | - | Jul 11, 11:20 UTC | Jul 11, 15:15 UTC | 3h 55m |
| 2026-07-11 | UTA576 | - | Jul 11, 06:35 UTC | Jul 11, 09:15 UTC | 2h 40m |
| 2026-07-10 | UTA575 | - | Jul 10, 14:15 UTC | Jul 10, 19:45 UTC | 5h 30m |
| 2026-07-10 | UTA575 | - | Jul 10, 08:25 UTC | Jul 10, 11:55 UTC | 3h 30m |
| 2026-07-09 | UTA356 | - | Jul 9, 17:50 UTC | Jul 10, 05:10 UTC | 11h 20m |
| 2026-07-09 | UTA398 | - | Jul 9, 15:25 UTC | Jul 9, 16:05 UTC | 40m |
| 2026-07-09 | UTA398 | - | Jul 9, 13:00 UTC | Jul 9, 13:25 UTC | 25m |
| 2026-07-09 | UTA397 | - | Jul 9, 07:55 UTC | Jul 9, 11:10 UTC | 3h 15m |
| 2026-07-08 | UTA364 | - | Jul 8, 14:05 UTC | Jul 9, 05:05 UTC | 15h 0m |
| 2026-07-07 | UTA6128 | - | Jul 7, 16:40 UTC | Jul 8, 14:05 UTC | 21h 25m |
| 2026-07-06 | UTA6128 | - | Jul 6, 23:20 UTC | Jul 7, 16:45 UTC | 17h 25m |
| 2026-07-06 | UTA476 | KRR → UFA | Jul 6, 16:20 UTC | Jul 6, 23:25 UTC | 7h 5m |
| 2026-07-05 | UTA475 | UFA → KRR | Jul 5, 19:55 UTC | Jul 6, 14:30 UTC | 18h 35m |
| 2026-07-05 | UTA475 | UFA → KRR | Jul 5, 15:25 UTC | Jul 6, 14:30 UTC | 23h 5m |
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-73067 page for operator, model, and routing details .