sensors Mode-S transponder
151D7F
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73087 · BOEING 737-800
- Hex
- 151D7F
- Octal
- 05216577
- Decimal
- 1,383,807
- Country
- RU
- Tail
- RA-73087
- Type
- B738
- Flights observed
- 57
- Distinct callsigns
- 19
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151D7F 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA469 | UTair Aviation | 12 | 2026-05-16 |
| UTA806 | UTair Aviation | 11 | 2026-05-31 |
| UTA248 | UTair Aviation | 6 | 2026-05-17 |
| UTA728 | UTair Aviation | 4 | 2026-05-28 |
| UTA470 | UTair Aviation | 4 | 2026-05-13 |
| UTA746 | UTair Aviation | 3 | 2026-05-19 |
| UTA731 | UTair Aviation | 3 | 2026-05-16 |
| UTA786 | UTair Aviation | 2 | 2026-05-24 |
| UTA291 | UTair Aviation | 2 | 2026-05-10 |
| UTA882 | UTair Aviation | 1 | 2026-05-11 |
| UTA881 | UTair Aviation | 1 | 2026-04-20 |
| UTA805 | UTair Aviation | 1 | 2026-05-02 |
| UTA786B | - | 1 | 2026-05-04 |
| UTA785B | - | 1 | 2026-05-04 |
| UTA785 | UTair Aviation | 1 | 2026-04-14 |
| UTA784 | UTair Aviation | 1 | 2026-04-27 |
| UTA745 | UTair Aviation | 1 | 2026-04-16 |
| UTA727 | UTair Aviation | 1 | 2026-05-28 |
| UTA572 | UTair Aviation | 1 | 2026-05-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | UTA806 | TAS → VKO | May 31, 23:45 UTC | Jun 1, 17:45 UTC | 18h 0m |
| 2026-05-31 | UTA806 | TAS → VKO | May 31, 17:05 UTC | Jun 1, 00:20 UTC | 7h 15m |
| 2026-05-28 | UTA728 | TLV → KUF | May 28, 07:20 UTC | May 28, 07:50 UTC | 30m |
| 2026-05-28 | UTA727 | KUF → TLV | May 28, 05:25 UTC | May 28, 05:45 UTC | 20m |
| 2026-05-24 | UTA786 | EVN → VKO | May 24, 23:15 UTC | May 24, 23:46 UTC | 31m |
| 2026-05-24 | UTA728 | TLV → KUF | May 24, 01:35 UTC | May 24, 01:45 UTC | 10m |
| 2026-05-23 | UTA806 | TAS → VKO | May 23, 00:15 UTC | May 23, 00:50 UTC | 35m |
| 2026-05-22 | UTA806 | TAS → VKO | May 22, 04:25 UTC | May 23, 00:50 UTC | 20h 25m |
| 2026-05-21 | UTA806 | TAS → VKO | May 21, 01:20 UTC | May 21, 01:50 UTC | 30m |
| 2026-05-19 | UTA746 | GYD → VKO | May 19, 09:40 UTC | May 19, 18:05 UTC | 8h 25m |
| 2026-05-17 | UTA248 | SGC → VKO | May 17, 07:25 UTC | May 18, 00:40 UTC | 17h 15m |
| 2026-05-16 | UTA248 | SGC → VKO | May 16, 21:50 UTC | May 17, 17:05 UTC | 19h 15m |
| 2026-05-16 | UTA248 | SGC → VKO | May 16, 13:51 UTC | May 17, 08:05 UTC | 18h 15m |
| 2026-05-16 | UTA731 | LED → GYD | May 16, 08:26 UTC | May 16, 08:41 UTC | 15m |
| 2026-05-16 | UTA469 | SGC → LED | May 16, 03:35 UTC | May 16, 05:05 UTC | 1h 30m |
| 2026-05-15 | UTA469 | SGC → LED | May 15, 03:55 UTC | May 16, 03:45 UTC | 23h 49m |
| 2026-05-14 | UTA469 | SGC → LED | May 14, 14:55 UTC | May 15, 05:20 UTC | 14h 25m |
| 2026-05-13 | UTA470 | LED → SGC | May 13, 21:30 UTC | May 14, 15:20 UTC | 17h 50m |
| 2026-05-13 | UTA470 | LED → SGC | May 13, 16:00 UTC | May 14, 15:20 UTC | 23h 20m |
| 2026-05-13 | UTA470 | LED → SGC | May 13, 14:30 UTC | May 14, 04:10 UTC | 13h 40m |
| 2026-05-12 | UTA470 | LED → SGC | May 12, 21:55 UTC | May 13, 21:45 UTC | 23h 50m |
| 2026-05-12 | UTA469 | SGC → LED | May 12, 04:00 UTC | May 12, 22:01 UTC | 18h 0m |
| 2026-05-11 | UTA882 | SKD → LED | May 11, 19:30 UTC | May 11, 19:40 UTC | 10m |
| 2026-05-11 | UTA469 | SGC → LED | May 11, 06:15 UTC | May 11, 10:40 UTC | 4h 25m |
| 2026-05-10 | UTA291 | LED → GDZ | May 10, 11:05 UTC | May 10, 12:05 UTC | 1h 0m |
| 2026-05-10 | UTA291 | LED → GDZ | May 10, 08:25 UTC | May 10, 09:30 UTC | 1h 5m |
| 2026-05-09 | UTA469 | SGC → LED | May 9, 13:40 UTC | May 10, 05:20 UTC | 15h 40m |
| 2026-05-09 | UTA469 | SGC → LED | May 9, 04:30 UTC | May 9, 14:15 UTC | 9h 45m |
| 2026-05-08 | UTA469 | SGC → LED | May 8, 05:54 UTC | May 9, 05:20 UTC | 23h 25m |
| 2026-05-08 | UTA469 | SGC → LED | May 8, 01:29 UTC | May 8, 07:14 UTC | 5h 45m |
| 2026-05-06 | UTA572 | KJA → VKO | May 6, 00:40 UTC | May 6, 01:25 UTC | 45m |
| 2026-05-04 | UTA786B | - | May 4, 05:50 UTC | May 4, 06:10 UTC | 20m |
| 2026-05-04 | UTA785B | - | May 4, 03:24 UTC | May 4, 03:54 UTC | 30m |
| 2026-05-02 | UTA805 | VKO → TAS | May 2, 17:30 UTC | May 3, 00:45 UTC | 7h 15m |
| 2026-05-02 | UTA806 | TAS → VKO | May 2, 00:25 UTC | May 2, 18:10 UTC | 17h 45m |
| 2026-04-29 | UTA746 | GYD → VKO | Apr 29, 14:10 UTC | Apr 29, 20:45 UTC | 6h 35m |
| 2026-04-28 | UTA746 | GYD → VKO | Apr 28, 18:00 UTC | Apr 29, 14:35 UTC | 20h 36m |
| 2026-04-28 | UTA728 | TLV → KUF | Apr 28, 08:05 UTC | Apr 28, 18:05 UTC | 10h 0m |
| 2026-04-27 | UTA784 | AYT → VKO | Apr 27, 16:40 UTC | Apr 28, 08:10 UTC | 15h 30m |
| 2026-04-26 | UTA806 | TAS → VKO | Apr 26, 16:20 UTC | Apr 27, 00:35 UTC | 8h 15m |
| 2026-04-26 | UTA806 | TAS → VKO | Apr 26, 03:50 UTC | Apr 27, 00:35 UTC | 20h 45m |
| 2026-04-26 | UTA248 | SGC → VKO | Apr 26, 03:30 UTC | Apr 27, 00:35 UTC | 21h 5m |
| 2026-04-25 | UTA248 | SGC → VKO | Apr 25, 13:40 UTC | Apr 26, 04:10 UTC | 14h 30m |
| 2026-04-25 | UTA731 | LED → GYD | Apr 25, 08:25 UTC | Apr 26, 04:10 UTC | 19h 45m |
| 2026-04-25 | UTA731 | LED → GYD | Apr 25, 04:20 UTC | Apr 26, 03:45 UTC | 23h 25m |
| 2026-04-22 | UTA469 | SGC → LED | Apr 22, 04:00 UTC | Apr 22, 21:55 UTC | 17h 55m |
| 2026-04-21 | UTA469 | SGC → LED | Apr 21, 07:40 UTC | Apr 22, 04:55 UTC | 21h 15m |
| 2026-04-20 | UTA248 | SGC → VKO | Apr 20, 21:50 UTC | Apr 21, 07:45 UTC | 9h 55m |
| 2026-04-20 | UTA881 | LED → SKD | Apr 20, 08:15 UTC | Apr 21, 07:45 UTC | 23h 31m |
| 2026-04-19 | UTA469 | SGC → LED | Apr 19, 18:15 UTC | Apr 20, 05:10 UTC | 10h 55m |
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-73087 page for operator, model, and routing details .