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
- 99
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3d 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UTA783 | UTair Aviation | 18 | 2026-07-22 |
| UTA784 | - | 13 | 2026-07-22 |
| UTA812 | - | 6 | 2026-07-14 |
| UTA469 | UTair Aviation | 6 | 2026-05-18 |
| UTA811 | - | 5 | 2026-07-14 |
| UTA785 | UTair Aviation | 4 | 2026-07-21 |
| UTA572 | UTair Aviation | 4 | 2026-07-21 |
| UTA810 | UTair Aviation | 3 | 2026-05-31 |
| UTA593 | UTair Aviation | 3 | 2026-05-16 |
| UTA295 | - | 3 | 2026-06-30 |
| UTA248 | UTair Aviation | 3 | 2026-05-30 |
| UTA882 | UTair Aviation | 2 | 2026-04-27 |
| UTA876 | - | 2 | 2026-07-12 |
| UTA801 | - | 2 | 2026-06-26 |
| UTA786 | UTair Aviation | 2 | 2026-07-21 |
| UTA712 | - | 2 | 2026-07-08 |
| UTA702 | - | 2 | 2026-07-11 |
| UTA701 | - | 2 | 2026-06-20 |
| UTA433 | UTair Aviation | 2 | 2026-06-22 |
| UTA296 | UTair Aviation | 2 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | UTA784 | - | Jul 22, 14:25 UTC | Jul 22, 16:15 UTC | 1h 50m |
| 2026-07-22 | UTA783 | VKO → AYT | Jul 22, 12:25 UTC | Jul 22, 12:45 UTC | 20m |
| 2026-07-21 | UTA786 | EVN → VKO | Jul 21, 23:10 UTC | Jul 22, 11:35 UTC | 12h 25m |
| 2026-07-21 | UTA785 | VKO → EVN | Jul 21, 20:50 UTC | Jul 21, 21:05 UTC | 15m |
| 2026-07-21 | UTA572 | KJA → VKO | Jul 21, 00:50 UTC | Jul 21, 21:05 UTC | 20h 15m |
| 2026-07-20 | UTA572 | KJA → VKO | Jul 20, 22:35 UTC | Jul 21, 21:05 UTC | 22h 29m |
| 2026-07-19 | UTA726 | AYT → VKO | Jul 19, 03:40 UTC | Jul 19, 17:35 UTC | 13h 55m |
| 2026-07-18 | UTA784 | - | Jul 18, 14:55 UTC | Jul 19, 01:45 UTC | 10h 50m |
| 2026-07-18 | UTA783 | - | Jul 18, 12:30 UTC | Jul 18, 13:10 UTC | 40m |
| 2026-07-17 | UTA571 | VKO → KJA | Jul 17, 19:45 UTC | Jul 18, 11:55 UTC | 16h 11m |
| 2026-07-15 | UTA572 | - | Jul 15, 22:15 UTC | Jul 16, 14:40 UTC | 16h 25m |
| 2026-07-15 | UTA572 | - | Jul 15, 14:50 UTC | Jul 16, 08:55 UTC | 18h 5m |
| 2026-07-14 | UTA812 | - | Jul 14, 11:50 UTC | Jul 14, 13:35 UTC | 1h 45m |
| 2026-07-14 | UTA811 | - | Jul 14, 09:20 UTC | Jul 14, 10:10 UTC | 50m |
| 2026-07-12 | UTA876 | - | Jul 12, 07:50 UTC | Jul 12, 08:20 UTC | 30m |
| 2026-07-11 | UTA702 | - | Jul 11, 08:25 UTC | Jul 11, 08:50 UTC | 25m |
| 2026-07-10 | UTA812 | - | Jul 10, 10:50 UTC | Jul 10, 12:30 UTC | 1h 40m |
| 2026-07-08 | UTA712 | - | Jul 8, 06:10 UTC | Jul 8, 06:40 UTC | 30m |
| 2026-07-07 | UTA812 | AYT → TJM | Jul 7, 12:10 UTC | Jul 7, 13:50 UTC | 1h 40m |
| 2026-07-07 | UTA811 | - | Jul 7, 10:10 UTC | Jul 7, 10:40 UTC | 30m |
| 2026-07-04 | UTA6132 | SGC → VKO | Jul 4, 18:30 UTC | Jul 4, 18:55 UTC | 25m |
| 2026-07-03 | UTA784 | - | Jul 3, 14:35 UTC | Jul 3, 16:25 UTC | 1h 50m |
| 2026-07-03 | - | - | Jul 3, 11:50 UTC | Jul 3, 13:10 UTC | 1h 20m |
| 2026-07-01 | UTA786 | - | Jul 1, 23:40 UTC | Jul 2, 06:15 UTC | 6h 35m |
| 2026-07-01 | UTA785 | - | Jul 1, 21:00 UTC | Jul 1, 21:10 UTC | 10m |
| 2026-06-30 | UTA295 | - | Jun 30, 09:40 UTC | Jun 30, 10:00 UTC | 20m |
| 2026-06-28 | UA786 | - | Jun 28, 08:50 UTC | Jun 28, 14:34 UTC | 5h 45m |
| 2026-06-28 | UTA785 | - | Jun 28, 06:30 UTC | Jun 28, 06:49 UTC | 20m |
| 2026-06-26 | UTA801 | - | Jun 26, 23:49 UTC | Jun 27, 06:30 UTC | 6h 40m |
| 2026-06-26 | UTA785 | - | Jun 26, 21:20 UTC | Jun 26, 21:39 UTC | 20m |
| 2026-06-25 | UTA295 | - | Jun 25, 09:50 UTC | Jun 25, 10:04 UTC | 15m |
| 2026-06-24 | UTA295 | - | Jun 24, 14:24 UTC | Jun 25, 10:04 UTC | 19h 40m |
| 2026-06-24 | UTA801 | - | Jun 24, 00:25 UTC | Jun 24, 14:34 UTC | 14h 10m |
| 2026-06-22 | UTA433 | TJM → KRR | Jun 22, 06:45 UTC | Jun 22, 07:34 UTC | 50m |
| 2026-06-21 | UTA433 | TJM → KRR | Jun 21, 08:04 UTC | Jun 22, 07:34 UTC | 23h 30m |
| 2026-06-21 | UTA876 | EVN → TJM | Jun 21, 07:59 UTC | Jun 21, 08:25 UTC | 25m |
| 2026-06-20 | UTA702 | IST → TJM | Jun 20, 08:34 UTC | Jun 20, 09:05 UTC | 30m |
| 2026-06-20 | UTA701 | - | Jun 20, 06:29 UTC | Jun 20, 06:49 UTC | 20m |
| 2026-06-20 | UTA701 | - | Jun 20, 04:49 UTC | Jun 20, 05:44 UTC | 55m |
| 2026-06-12 | UTA812 | AYT → TJM | Jun 12, 11:20 UTC | Jun 12, 14:05 UTC | 2h 45m |
| 2026-06-12 | UTA811 | TJM → AYT | Jun 12, 08:35 UTC | Jun 12, 08:55 UTC | 20m |
| 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 |
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 .