sensors Mode-S transponder
151D7C
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73084 · BOEING 737-800
- Hex
- 151D7C
- Octal
- 05216574
- Decimal
- 1,383,804
- Country
- RU
- Tail
- RA-73084
- Type
- B738
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 151D7C 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 |
|---|---|---|---|
| UTA783 | UTair Aviation | 13 | 2026-05-18 |
| UTA784 | UTair Aviation | 11 | 2026-05-21 |
| UTA810 | UTair Aviation | 8 | 2026-05-06 |
| UTA295 | UTair Aviation | 6 | 2026-05-30 |
| UTA785 | UTair Aviation | 4 | 2026-05-19 |
| UTA786 | UTair Aviation | 3 | 2026-05-19 |
| UTA727 | UTair Aviation | 3 | 2026-05-03 |
| UTA728 | UTair Aviation | 2 | 2026-05-04 |
| UTA454 | UTair Aviation | 2 | 2026-04-28 |
| UTA453 | UTair Aviation | 2 | 2026-05-09 |
| UTA812 | UTair Aviation | 1 | 2026-05-26 |
| UTA811 | UTair Aviation | 1 | 2026-05-26 |
| UTA809 | - | 1 | 2026-04-14 |
| UTA808 | UTair Aviation | 1 | 2026-05-22 |
| UTA806 | UTair Aviation | 1 | 2026-05-29 |
| UTA751 | UTair Aviation | 1 | 2026-05-24 |
| UTA575 | UTair Aviation | 1 | 2026-04-22 |
| UTA464 | UTair Aviation | 1 | 2026-05-23 |
| UTA400 | UTair Aviation | 1 | 2026-05-16 |
| UTA373 | UTair Aviation | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UTA295 | VKO → SGC | May 30, 09:50 UTC | May 30, 10:15 UTC | 25m |
| 2026-05-30 | UTA295 | VKO → SGC | May 30, 09:05 UTC | May 30, 09:20 UTC | 15m |
| 2026-05-29 | UTA806 | TAS → VKO | May 29, 17:10 UTC | May 30, 00:20 UTC | 7h 10m |
| 2026-05-26 | UTA812 | AYT → TJM | May 26, 10:29 UTC | May 26, 12:30 UTC | 2h 0m |
| 2026-05-26 | UTA811 | TJM → AYT | May 26, 08:30 UTC | May 26, 08:50 UTC | 20m |
| 2026-05-24 | UTA751 | TJM → LBD | May 24, 14:25 UTC | May 25, 03:30 UTC | 13h 5m |
| 2026-05-23 | UTA464 | TJM → VKO | May 23, 08:55 UTC | May 23, 14:35 UTC | 5h 40m |
| 2026-05-22 | UTA808 | BHK → VKO | May 22, 14:55 UTC | May 23, 05:35 UTC | 14h 39m |
| 2026-05-21 | UTA784 | AYT → VKO | May 21, 15:10 UTC | May 22, 15:00 UTC | 23h 50m |
| 2026-05-21 | UTA784 | AYT → VKO | May 21, 14:10 UTC | May 21, 16:15 UTC | 2h 5m |
| 2026-05-19 | UTA786 | EVN → VKO | May 19, 23:05 UTC | May 20, 15:25 UTC | 16h 21m |
| 2026-05-19 | UTA785 | VKO → EVN | May 19, 20:50 UTC | May 19, 21:00 UTC | 10m |
| 2026-05-19 | UTA785 | VKO → EVN | May 19, 18:20 UTC | May 19, 18:35 UTC | 15m |
| 2026-05-18 | UTA784 | AYT → VKO | May 18, 17:05 UTC | May 19, 13:00 UTC | 19h 54m |
| 2026-05-18 | UTA784 | AYT → VKO | May 18, 15:25 UTC | May 19, 13:00 UTC | 21h 34m |
| 2026-05-18 | UTA783 | VKO → AYT | May 18, 11:55 UTC | May 18, 12:15 UTC | 20m |
| 2026-05-16 | UTA400 | GRV → VKO | May 16, 15:20 UTC | May 16, 15:45 UTC | 25m |
| 2026-05-15 | UTA784 | AYT → VKO | May 15, 13:55 UTC | May 16, 01:40 UTC | 11h 44m |
| 2026-05-15 | UTA783 | VKO → AYT | May 15, 12:15 UTC | May 15, 12:30 UTC | 15m |
| 2026-05-14 | UTA295 | VKO → SGC | May 14, 14:35 UTC | May 15, 04:40 UTC | 14h 5m |
| 2026-05-14 | UTA295 | VKO → SGC | May 14, 05:15 UTC | May 15, 04:40 UTC | 23h 25m |
| 2026-05-13 | UTA295 | VKO → SGC | May 13, 22:00 UTC | May 14, 15:25 UTC | 17h 25m |
| 2026-05-13 | UTA295 | VKO → SGC | May 13, 17:05 UTC | May 14, 15:25 UTC | 22h 20m |
| 2026-05-13 | UTA784 | AYT → VKO | May 13, 15:20 UTC | May 14, 15:01 UTC | 23h 40m |
| 2026-05-09 | UTA453 | VKO → TJM | May 9, 19:05 UTC | May 9, 20:10 UTC | 1h 5m |
| 2026-05-08 | UTA249 | VKO → AER | May 8, 17:05 UTC | May 9, 11:20 UTC | 18h 15m |
| 2026-05-08 | UTA784 | AYT → VKO | May 8, 15:10 UTC | May 9, 11:20 UTC | 20h 10m |
| 2026-05-08 | UTA783 | VKO → AYT | May 8, 13:15 UTC | May 8, 13:35 UTC | 20m |
| 2026-05-07 | UTA784 | AYT → VKO | May 7, 21:45 UTC | May 8, 12:30 UTC | 14h 45m |
| 2026-05-07 | UTA783 | VKO → AYT | May 7, 19:45 UTC | May 7, 20:05 UTC | 20m |
| 2026-05-07 | UTA783 | VKO → AYT | May 7, 04:25 UTC | May 7, 18:55 UTC | 14h 31m |
| 2026-05-06 | UTA783 | VKO → AYT | May 6, 22:20 UTC | May 7, 18:55 UTC | 20h 35m |
| 2026-05-06 | UTA810 | SKD → VKO | May 6, 17:35 UTC | May 7, 06:20 UTC | 12h 45m |
| 2026-05-06 | UTA810 | SKD → VKO | May 6, 05:30 UTC | May 7, 04:45 UTC | 23h 14m |
| 2026-05-06 | UTA785 | VKO → EVN | May 6, 03:25 UTC | May 6, 03:45 UTC | 20m |
| 2026-05-04 | UTA728 | TLV → KUF | May 4, 12:30 UTC | May 4, 12:40 UTC | 10m |
| 2026-05-03 | UTA727 | KUF → TLV | May 3, 15:05 UTC | May 4, 10:00 UTC | 18h 55m |
| 2026-05-03 | UTA727 | KUF → TLV | May 3, 14:30 UTC | May 4, 10:00 UTC | 19h 30m |
| 2026-05-02 | UTA784 | AYT → VKO | May 2, 15:15 UTC | May 3, 15:00 UTC | 23h 44m |
| 2026-05-02 | UTA784 | AYT → VKO | May 2, 14:25 UTC | May 2, 16:15 UTC | 1h 50m |
| 2026-05-02 | UTA783 | VKO → AYT | May 2, 12:35 UTC | May 2, 12:50 UTC | 15m |
| 2026-05-02 | UTA783 | VKO → AYT | May 2, 10:15 UTC | May 2, 11:40 UTC | 1h 25m |
| 2026-05-01 | UTA783 | VKO → AYT | May 1, 11:05 UTC | May 2, 11:00 UTC | 23h 55m |
| 2026-04-30 | UTA783 | VKO → AYT | Apr 30, 21:00 UTC | May 1, 11:40 UTC | 14h 40m |
| 2026-04-30 | UTA783 | VKO → AYT | Apr 30, 15:05 UTC | May 1, 11:40 UTC | 20h 35m |
| 2026-04-30 | UTA784 | AYT → VKO | Apr 30, 14:15 UTC | May 1, 11:40 UTC | 21h 25m |
| 2026-04-30 | UTA783 | VKO → AYT | Apr 30, 12:20 UTC | Apr 30, 12:50 UTC | 30m |
| 2026-04-30 | UTA783 | VKO → AYT | Apr 30, 10:55 UTC | Apr 30, 11:30 UTC | 35m |
| 2026-04-28 | UTA786 | EVN → VKO | Apr 28, 23:00 UTC | Apr 29, 11:00 UTC | 12h 1m |
| 2026-04-28 | UTA454 | TJM → VKO | Apr 28, 03:20 UTC | Apr 28, 21:19 UTC | 18h 0m |
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-73084 page for operator, model, and routing details .