sensors Mode-S transponder
151D80
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73088 · BOEING 737-800
- Hex
- 151D80
- Octal
- 05216600
- Decimal
- 1,383,808
- Country
- RU
- Tail
- RA-73088
- Type
- B738
- Flights observed
- 58
- Distinct callsigns
- 18
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151D80 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA783 | UTair Aviation | 16 | 2026-06-03 |
| UTA784 | UTair Aviation | 10 | 2026-06-03 |
| UTA469 | UTair Aviation | 6 | 2026-05-18 |
| UTA810 | UTair Aviation | 3 | 2026-05-31 |
| UTA593 | UTair Aviation | 3 | 2026-05-16 |
| UTA248 | UTair Aviation | 3 | 2026-05-30 |
| UTA882 | UTair Aviation | 2 | 2026-04-27 |
| UTA812 | UTair Aviation | 2 | 2026-06-09 |
| UTA811 | UTair Aviation | 2 | 2026-06-09 |
| UTA296 | UTair Aviation | 2 | 2026-05-20 |
| UTA249 | UTair Aviation | 2 | 2026-05-02 |
| UTA806 | UTair Aviation | 1 | 2026-05-27 |
| UTA728 | UTair Aviation | 1 | 2026-05-26 |
| UTA727 | UTair Aviation | 1 | 2026-05-26 |
| UTA712 | UTair Aviation | 1 | 2026-06-10 |
| UTA575 | UTair Aviation | 1 | 2026-05-03 |
| UTA507 | UTair Aviation | 1 | 2026-06-06 |
| UTA470 | UTair Aviation | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | UTA712 | EVN → SGC | Jun 10, 06:15 UTC | Jun 10, 07:30 UTC | 1h 15m |
| 2026-06-09 | UTA812 | AYT → TJM | Jun 9, 10:35 UTC | Jun 10, 04:30 UTC | 17h 55m |
| 2026-06-09 | UTA811 | TJM → AYT | Jun 9, 07:20 UTC | Jun 9, 08:50 UTC | 1h 30m |
| 2026-06-06 | UTA507 | LED → KRR | Jun 6, 14:54 UTC | Jun 6, 15:19 UTC | 25m |
| 2026-06-05 | UTA812 | AYT → TJM | Jun 5, 10:35 UTC | Jun 5, 13:25 UTC | 2h 50m |
| 2026-06-05 | UTA811 | TJM → AYT | Jun 5, 07:40 UTC | Jun 5, 08:40 UTC | 1h 0m |
| 2026-06-03 | UTA784 | AYT → VKO | Jun 3, 14:10 UTC | Jun 3, 16:40 UTC | 2h 30m |
| 2026-06-03 | UTA783 | VKO → AYT | Jun 3, 11:55 UTC | Jun 3, 12:20 UTC | 25m |
| 2026-06-02 | UTA784 | AYT → VKO | Jun 2, 13:55 UTC | Jun 2, 15:50 UTC | 1h 55m |
| 2026-06-02 | UTA783 | VKO → AYT | Jun 2, 10:45 UTC | Jun 2, 12:15 UTC | 1h 30m |
| 2026-06-01 | UTA783 | VKO → AYT | Jun 1, 16:05 UTC | Jun 2, 12:15 UTC | 20h 10m |
| 2026-06-01 | UTA784 | AYT → VKO | Jun 1, 14:10 UTC | Jun 2, 12:15 UTC | 22h 5m |
| 2026-06-01 | UTA783 | VKO → AYT | Jun 1, 12:15 UTC | Jun 1, 12:40 UTC | 25m |
| 2026-05-31 | UTA810 | SKD → VKO | May 31, 18:00 UTC | Jun 1, 11:30 UTC | 17h 30m |
| 2026-05-30 | UTA248 | SGC → VKO | May 30, 03:40 UTC | May 30, 08:15 UTC | 4h 35m |
| 2026-05-27 | UTA806 | TAS → VKO | May 27, 00:25 UTC | May 27, 18:40 UTC | 18h 15m |
| 2026-05-26 | UTA728 | TLV → KUF | May 26, 07:24 UTC | May 27, 00:39 UTC | 17h 15m |
| 2026-05-26 | UTA727 | KUF → TLV | May 26, 05:20 UTC | May 26, 05:34 UTC | 15m |
| 2026-05-25 | UTA784 | AYT → VKO | May 25, 14:00 UTC | May 25, 15:55 UTC | 1h 55m |
| 2026-05-25 | UTA783 | VKO → AYT | May 25, 12:05 UTC | May 25, 12:25 UTC | 20m |
| 2026-05-25 | UTA783 | VKO → AYT | May 25, 10:45 UTC | May 25, 11:20 UTC | 35m |
| 2026-05-23 | UTA810 | SKD → VKO | May 23, 14:40 UTC | May 24, 07:20 UTC | 16h 41m |
| 2026-05-23 | UTA810 | SKD → VKO | May 23, 08:15 UTC | May 24, 07:20 UTC | 23h 6m |
| 2026-05-20 | UTA296 | SGC → VKO | May 20, 14:30 UTC | May 20, 15:10 UTC | 40m |
| 2026-05-19 | UTA296 | SGC → VKO | May 19, 16:05 UTC | May 20, 15:10 UTC | 23h 6m |
| 2026-05-19 | UTA784 | AYT → VKO | May 19, 14:10 UTC | May 19, 16:30 UTC | 2h 20m |
| 2026-05-18 | UTA783 | VKO → AYT | May 18, 17:40 UTC | May 19, 11:20 UTC | 17h 39m |
| 2026-05-18 | UTA469 | SGC → LED | May 18, 03:45 UTC | May 18, 17:50 UTC | 14h 5m |
| 2026-05-17 | UTA469 | SGC → LED | May 17, 07:00 UTC | May 18, 06:01 UTC | 23h 0m |
| 2026-05-16 | UTA593 | SGC → GRV | May 16, 19:45 UTC | May 17, 07:55 UTC | 12h 10m |
| 2026-05-16 | UTA593 | SGC → GRV | May 16, 11:35 UTC | May 17, 07:55 UTC | 20h 20m |
| 2026-05-16 | UTA593 | SGC → GRV | May 16, 07:05 UTC | May 16, 20:45 UTC | 13h 40m |
| 2026-05-12 | UTA784 | AYT → VKO | May 12, 14:10 UTC | May 13, 09:55 UTC | 19h 45m |
| 2026-05-12 | UTA783 | VKO → AYT | May 12, 12:10 UTC | May 12, 12:25 UTC | 15m |
| 2026-05-11 | UTA783 | VKO → AYT | May 11, 16:05 UTC | May 12, 11:15 UTC | 19h 11m |
| 2026-05-11 | UTA784 | AYT → VKO | May 11, 14:10 UTC | May 12, 11:15 UTC | 21h 6m |
| 2026-05-11 | UTA783 | VKO → AYT | May 11, 12:00 UTC | May 11, 12:20 UTC | 20m |
| 2026-05-10 | UTA783 | VKO → AYT | May 10, 18:39 UTC | May 11, 11:15 UTC | 16h 35m |
| 2026-05-10 | UTA783 | VKO → AYT | May 10, 14:04 UTC | May 11, 11:15 UTC | 21h 10m |
| 2026-05-10 | UTA783 | VKO → AYT | May 10, 13:49 UTC | May 11, 11:15 UTC | 21h 25m |
| 2026-05-05 | UTA784 | AYT → VKO | May 5, 18:25 UTC | May 6, 11:35 UTC | 17h 10m |
| 2026-05-05 | UTA783 | VKO → AYT | May 5, 11:50 UTC | May 5, 12:10 UTC | 20m |
| 2026-05-05 | UTA783 | VKO → AYT | May 5, 10:20 UTC | May 5, 11:05 UTC | 45m |
| 2026-05-04 | UTA783 | VKO → AYT | May 4, 15:30 UTC | May 5, 11:05 UTC | 19h 36m |
| 2026-05-03 | UTA575 | VKO → KRR | May 3, 14:55 UTC | May 3, 15:15 UTC | 20m |
| 2026-05-02 | UTA249 | VKO → AER | May 2, 03:50 UTC | May 2, 11:15 UTC | 7h 25m |
| 2026-04-30 | UTA470 | LED → SGC | Apr 30, 22:15 UTC | Apr 30, 22:25 UTC | 10m |
| 2026-04-29 | UTA249 | VKO → AER | Apr 29, 10:35 UTC | Apr 29, 10:45 UTC | 10m |
| 2026-04-28 | UTA784 | AYT → VKO | Apr 28, 14:05 UTC | Apr 29, 10:45 UTC | 20h 40m |
| 2026-04-28 | UTA784 | AYT → VKO | Apr 28, 13:55 UTC | Apr 29, 10:45 UTC | 20h 50m |
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-73088 page for operator, model, and routing details .