sensors Mode-S transponder
151D7D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73085 · BOEING 737-800
- Hex
- 151D7D
- Octal
- 05216575
- Decimal
- 1,383,805
- Country
- RU
- Tail
- RA-73085
- Type
- B738
- Flights observed
- 61
- Distinct callsigns
- 17
- Country
- RU
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 151D7D 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA469 | UTair Aviation | 16 | 2026-05-29 |
| UTA746 | UTair Aviation | 7 | 2026-05-17 |
| UTA805 | UTair Aviation | 5 | 2026-05-14 |
| UTA745 | UTair Aviation | 5 | 2026-05-12 |
| UTA731 | UTair Aviation | 5 | 2026-05-22 |
| UTA470 | UTair Aviation | 4 | 2026-05-06 |
| UTA806 | UTair Aviation | 3 | 2026-05-14 |
| UTA785 | UTair Aviation | 3 | 2026-05-09 |
| UTA881 | UTair Aviation | 2 | 2026-05-25 |
| UTA786 | UTair Aviation | 2 | 2026-05-09 |
| UTA364 | UTair Aviation | 2 | 2026-04-13 |
| UTA248 | UTair Aviation | 2 | 2026-05-28 |
| UTA807 | - | 1 | 2026-04-13 |
| UTA732 | UTair Aviation | 1 | 2026-05-23 |
| UTA296 | - | 1 | 2026-04-13 |
| UTA247 | - | 1 | 2026-04-14 |
| 464 | - | 1 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UTA469 | SGC → LED | May 29, 03:40 UTC | May 29, 22:10 UTC | 18h 30m |
| 2026-05-28 | UTA248 | SGC → VKO | May 28, 03:40 UTC | May 28, 04:00 UTC | 20m |
| 2026-05-26 | UTA469 | SGC → LED | May 26, 20:40 UTC | May 27, 04:59 UTC | 8h 20m |
| 2026-05-25 | UTA469 | SGC → LED | May 25, 16:55 UTC | May 26, 05:05 UTC | 12h 10m |
| 2026-05-25 | UTA881 | LED → SKD | May 25, 08:35 UTC | May 25, 09:35 UTC | 1h 0m |
| 2026-05-25 | UTA469 | SGC → LED | May 25, 03:45 UTC | May 25, 05:10 UTC | 1h 25m |
| 2026-05-24 | UTA248 | SGC → VKO | May 24, 03:55 UTC | May 24, 04:20 UTC | 25m |
| 2026-05-23 | UTA732 | GYD → LED | May 23, 08:10 UTC | May 23, 16:50 UTC | 8h 40m |
| 2026-05-22 | UTA469 | SGC → LED | May 22, 20:40 UTC | May 23, 05:15 UTC | 8h 34m |
| 2026-05-22 | UTA731 | LED → GYD | May 22, 08:20 UTC | May 22, 08:55 UTC | 35m |
| 2026-05-22 | UTA469 | SGC → LED | May 22, 06:00 UTC | May 22, 06:10 UTC | 10m |
| 2026-05-22 | UTA469 | SGC → LED | May 22, 03:50 UTC | May 22, 05:20 UTC | 1h 30m |
| 2026-05-21 | UTA469 | SGC → LED | May 21, 03:35 UTC | May 21, 05:05 UTC | 1h 30m |
| 2026-05-18 | UTA469 | SGC → LED | May 18, 11:45 UTC | May 19, 05:20 UTC | 17h 34m |
| 2026-05-17 | UTA746 | GYD → VKO | May 17, 14:40 UTC | May 18, 12:20 UTC | 21h 40m |
| 2026-05-17 | UTA746 | GYD → VKO | May 17, 01:30 UTC | May 17, 15:15 UTC | 13h 45m |
| 2026-05-16 | UTA746 | GYD → VKO | May 16, 09:56 UTC | May 17, 02:00 UTC | 16h 5m |
| 2026-05-15 | UTA746 | GYD → VKO | May 15, 19:35 UTC | May 16, 13:01 UTC | 17h 26m |
| 2026-05-14 | UTA805 | VKO → TAS | May 14, 17:55 UTC | May 15, 09:35 UTC | 15h 40m |
| 2026-05-14 | UTA806 | TAS → VKO | May 14, 02:05 UTC | May 15, 01:05 UTC | 23h 0m |
| 2026-05-13 | UTA806 | TAS → VKO | May 13, 11:00 UTC | May 14, 02:45 UTC | 15h 45m |
| 2026-05-12 | UTA745 | VKO → GYD | May 12, 17:20 UTC | May 13, 16:15 UTC | 22h 55m |
| 2026-05-12 | UTA805 | VKO → TAS | May 12, 16:55 UTC | May 13, 11:30 UTC | 18h 35m |
| 2026-05-11 | UTA805 | VKO → TAS | May 11, 17:00 UTC | May 12, 09:40 UTC | 16h 40m |
| 2026-05-11 | UTA746 | GYD → VKO | May 11, 11:45 UTC | May 11, 12:25 UTC | 40m |
| 2026-05-09 | UTA786 | EVN → VKO | May 9, 23:20 UTC | May 10, 12:34 UTC | 13h 15m |
| 2026-05-09 | UTA785 | VKO → EVN | May 9, 08:10 UTC | May 9, 21:25 UTC | 13h 15m |
| 2026-05-08 | UTA805 | VKO → TAS | May 8, 17:45 UTC | May 9, 08:20 UTC | 14h 35m |
| 2026-05-08 | UTA745 | VKO → GYD | May 8, 08:09 UTC | May 8, 18:20 UTC | 10h 10m |
| 2026-05-06 | UTA470 | LED → SGC | May 6, 21:45 UTC | May 6, 21:55 UTC | 10m |
| 2026-05-05 | UTA470 | LED → SGC | May 5, 22:15 UTC | May 5, 22:30 UTC | 15m |
| 2026-05-04 | UTA470 | LED → SGC | May 4, 23:30 UTC | May 5, 22:30 UTC | 23h 0m |
| 2026-05-04 | UTA470 | LED → SGC | May 4, 22:15 UTC | May 5, 00:10 UTC | 1h 55m |
| 2026-05-04 | UTA881 | LED → SKD | May 4, 09:55 UTC | May 4, 10:10 UTC | 15m |
| 2026-05-04 | UTA469 | SGC → LED | May 4, 03:40 UTC | May 4, 05:20 UTC | 1h 40m |
| 2026-05-02 | UTA469 | SGC → LED | May 2, 03:40 UTC | May 2, 09:00 UTC | 5h 20m |
| 2026-05-01 | UTA731 | LED → GYD | May 1, 08:05 UTC | May 1, 08:30 UTC | 25m |
| 2026-05-01 | UTA469 | SGC → LED | May 1, 04:25 UTC | May 1, 05:00 UTC | 35m |
| 2026-04-29 | UTA469 | SGC → LED | Apr 29, 03:45 UTC | Apr 29, 16:50 UTC | 13h 6m |
| 2026-04-27 | UTA746 | GYD → VKO | Apr 27, 16:25 UTC | Apr 27, 16:35 UTC | 10m |
| 2026-04-27 | UTA786 | EVN → VKO | Apr 27, 00:50 UTC | Apr 27, 14:40 UTC | 13h 50m |
| 2026-04-26 | UTA785 | VKO → EVN | Apr 26, 22:10 UTC | Apr 26, 23:05 UTC | 55m |
| 2026-04-26 | UTA785 | VKO → EVN | Apr 26, 00:35 UTC | Apr 26, 23:05 UTC | 22h 30m |
| 2026-04-25 | UTA806 | TAS → VKO | Apr 25, 17:45 UTC | Apr 26, 01:15 UTC | 7h 30m |
| 2026-04-23 | UTA805 | VKO → TAS | Apr 23, 17:10 UTC | Apr 24, 00:45 UTC | 7h 34m |
| 2026-04-21 | UTA746 | GYD → VKO | Apr 21, 17:35 UTC | Apr 22, 12:25 UTC | 18h 50m |
| 2026-04-21 | UTA745 | VKO → GYD | Apr 21, 09:20 UTC | Apr 22, 09:15 UTC | 23h 55m |
| 2026-04-21 | UTA745 | VKO → GYD | Apr 21, 09:00 UTC | Apr 21, 17:50 UTC | 8h 50m |
| 2026-04-20 | UTA745 | VKO → GYD | Apr 20, 17:00 UTC | Apr 21, 09:35 UTC | 16h 35m |
| 2026-04-18 | UTA731 | LED → GYD | Apr 18, 10:00 UTC | Apr 18, 11:10 UTC | 1h 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-73085 page for operator, model, and routing details .