sensors Mode-S transponder
50840A
ICAO 24-bit transponder address · allocated to Ukraine
Currently assigned to UR-AZE · BOEING 737-800
- Hex
- 50840A
- Octal
- 24102012
- Decimal
- 5,276,682
- Country
- UA
- Tail
- UR-AZE
- Type
- B738
- Flights observed
- 112
- Distinct callsigns
- 20
- Country
- UA
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 50840A falls within the block assigned to Ukraine (UA) by ICAO Annex 10, Volume III. Every aircraft registered in Ukraine 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 |
|---|---|---|---|
| UTN9122 | Trans-Ulgii | 15 | 2026-05-28 |
| UTN9124 | Trans-Ulgii | 8 | 2026-05-29 |
| UTN9123 | Trans-Ulgii | 7 | 2026-05-06 |
| UTN9121 | Trans-Ulgii | 7 | 2026-04-25 |
| UTN7422 | Trans-Ulgii | 6 | 2026-05-29 |
| UTN7421 | Trans-Ulgii | 5 | 2026-05-22 |
| UTN7022 | - | 5 | 2026-05-26 |
| UTN7021 | Trans-Ulgii | 5 | 2026-05-26 |
| UTN2225 | Trans-Ulgii | 5 | 2026-05-24 |
| UTN9147 | Trans-Ulgii | 4 | 2026-05-27 |
| UTN7126 | Trans-Ulgii | 4 | 2026-04-15 |
| UTN7125 | Trans-Ulgii | 4 | 2026-04-15 |
| UTN5822 | Trans-Ulgii | 3 | 2026-04-16 |
| UTN5821 | - | 3 | 2026-04-16 |
| UTN3647 | - | 3 | 2026-05-21 |
| UTN3624 | Trans-Ulgii | 3 | 2026-04-18 |
| UTN2248 | Trans-Ulgii | 3 | 2026-05-23 |
| UTN2247 | Trans-Ulgii | 3 | 2026-05-23 |
| UTN2226 | Trans-Ulgii | 3 | 2026-05-17 |
| UTN9178 | Trans-Ulgii | 2 | 2026-05-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UTN9124 | HRG → KTW | May 29, 13:15 UTC | May 29, 23:35 UTC | 10h 21m |
| 2026-05-29 | UTN7422 | POZ → POZ | May 29, 02:05 UTC | May 29, 11:55 UTC | 9h 50m |
| 2026-05-28 | UTN9122 | HRG → KTW | May 28, 04:35 UTC | May 28, 22:55 UTC | 18h 20m |
| 2026-05-28 | UTN9122 | HRG → KTW | May 28, 02:35 UTC | May 28, 22:55 UTC | 20h 20m |
| 2026-05-28 | UTN9122 | HRG → KTW | May 28, 02:05 UTC | May 28, 22:55 UTC | 20h 50m |
| 2026-05-27 | UTN9147 | KTW → RMF | May 27, 07:30 UTC | May 27, 17:15 UTC | 9h 45m |
| 2026-05-26 | UTN7021 | VNO → HRG | May 26, 12:14 UTC | May 26, 23:05 UTC | 10h 50m |
| 2026-05-26 | UTN7022 | - | May 26, 00:44 UTC | May 26, 10:39 UTC | 9h 55m |
| 2026-05-24 | UTN2225 | WAW → HRG | May 24, 13:15 UTC | May 24, 23:46 UTC | 10h 31m |
| 2026-05-24 | UTN9125 | KTW → HRG | May 24, 02:15 UTC | May 24, 11:40 UTC | 9h 25m |
| 2026-05-23 | UTN2247 | WAW → RMF | May 23, 13:50 UTC | May 23, 23:45 UTC | 9h 56m |
| 2026-05-23 | UTN2248 | WAW → RMF | May 23, 01:00 UTC | May 23, 11:45 UTC | 10h 44m |
| 2026-05-22 | UTN7421 | POZ → POZ | May 22, 13:10 UTC | May 22, 23:00 UTC | 9h 50m |
| 2026-05-22 | UTN7422 | POZ → POZ | May 22, 01:55 UTC | May 22, 11:40 UTC | 9h 45m |
| 2026-05-21 | UTN3647 | - | May 21, 12:25 UTC | May 21, 21:35 UTC | 9h 10m |
| 2026-05-21 | UTN9177 | KTW → KTW | May 21, 01:10 UTC | May 21, 10:35 UTC | 9h 25m |
| 2026-05-20 | UTN9147 | KTW → RMF | May 20, 07:30 UTC | May 20, 17:25 UTC | 9h 55m |
| 2026-05-19 | UTN7021 | VNO → HRG | May 19, 12:15 UTC | May 19, 23:00 UTC | 10h 45m |
| 2026-05-19 | UTN7022 | - | May 19, 00:40 UTC | May 19, 10:50 UTC | 10h 10m |
| 2026-05-17 | UTN2225 | WAW → HRG | May 17, 13:35 UTC | May 18, 00:35 UTC | 11h 0m |
| 2026-05-17 | UTN2226 | HRG → WAW | May 17, 02:10 UTC | May 17, 11:40 UTC | 9h 30m |
| 2026-05-16 | UTN2247 | WAW → RMF | May 16, 14:11 UTC | May 17, 00:20 UTC | 10h 10m |
| 2026-05-16 | UTN2248 | WAW → RMF | May 16, 01:05 UTC | May 16, 11:55 UTC | 10h 51m |
| 2026-05-14 | UTN3647 | - | May 14, 12:15 UTC | May 14, 21:50 UTC | 9h 35m |
| 2026-05-14 | UTN3648 | - | May 14, 01:05 UTC | May 14, 10:45 UTC | 9h 40m |
| 2026-05-13 | UTN9148 | RMF → KTW | May 13, 16:35 UTC | May 13, 17:05 UTC | 30m |
| 2026-05-13 | UTN9147 | KTW → RMF | May 13, 07:30 UTC | May 13, 16:30 UTC | 9h 0m |
| 2026-05-12 | UTN7021 | VNO → HRG | May 12, 12:20 UTC | May 12, 23:30 UTC | 11h 10m |
| 2026-05-12 | UTN7022 | - | May 12, 02:45 UTC | May 12, 10:50 UTC | 8h 5m |
| 2026-05-10 | UTN2225 | WAW → HRG | May 10, 13:19 UTC | May 11, 00:30 UTC | 11h 10m |
| 2026-05-10 | UTN2226 | HRG → WAW | May 10, 02:14 UTC | May 10, 11:55 UTC | 9h 40m |
| 2026-05-09 | UTN2247 | WAW → RMF | May 9, 14:20 UTC | May 10, 00:24 UTC | 10h 5m |
| 2026-05-09 | UTN2248 | WAW → RMF | May 9, 00:50 UTC | May 9, 11:35 UTC | 10h 45m |
| 2026-05-07 | UTN9178 | RMF → KTW | May 7, 18:00 UTC | May 7, 21:40 UTC | 3h 40m |
| 2026-05-07 | UTN3647 | - | May 7, 12:10 UTC | May 7, 14:55 UTC | 2h 45m |
| 2026-05-07 | UTN3648 | - | May 7, 01:15 UTC | May 7, 10:50 UTC | 9h 35m |
| 2026-05-06 | UTN9124 | HRG → KTW | May 6, 12:35 UTC | May 6, 23:35 UTC | 10h 59m |
| 2026-05-06 | UTN9123 | KTW → HRG | May 6, 02:01 UTC | May 6, 11:15 UTC | 9h 14m |
| 2026-05-05 | UTN7021 | VNO → HRG | May 5, 12:15 UTC | May 5, 23:50 UTC | 11h 35m |
| 2026-05-05 | UTN7022 | - | May 5, 00:35 UTC | May 5, 10:45 UTC | 10h 10m |
| 2026-05-03 | UTN9147 | KTW → RMF | May 3, 10:40 UTC | May 3, 20:25 UTC | 9h 45m |
| 2026-05-02 | UTN9178 | RMF → KTW | May 2, 14:50 UTC | May 2, 23:55 UTC | 9h 5m |
| 2026-05-02 | UTN9177 | KTW → KTW | May 2, 01:25 UTC | May 2, 11:55 UTC | 10h 30m |
| 2026-04-30 | UTN9122 | HRG → KTW | Apr 30, 04:35 UTC | May 1, 00:05 UTC | 19h 30m |
| 2026-04-30 | UTN9122 | HRG → KTW | Apr 30, 02:35 UTC | May 1, 00:05 UTC | 21h 30m |
| 2026-04-30 | UTN9122 | HRG → KTW | Apr 30, 02:20 UTC | May 1, 00:05 UTC | 21h 45m |
| 2026-04-29 | UTN9124 | HRG → KTW | Apr 29, 13:25 UTC | Apr 29, 22:30 UTC | 9h 5m |
| 2026-04-29 | UTN9123 | KTW → HRG | Apr 29, 01:50 UTC | Apr 29, 11:35 UTC | 9h 46m |
| 2026-04-28 | UTN7021 | VNO → HRG | Apr 28, 12:30 UTC | Apr 29, 00:30 UTC | 12h 0m |
| 2026-04-28 | UTN7022 | - | Apr 28, 00:50 UTC | Apr 28, 11:00 UTC | 10h 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 UR-AZE page for operator, model, and routing details .