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
- 198
- Distinct callsigns
- 20
- Country
- UA
- Last broadcast
- 11m ago
Current 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 | - | 28 | 2026-07-11 |
| UTN9121 | - | 23 | 2026-07-14 |
| UTN9124 | - | 13 | 2026-07-13 |
| UTN7422 | - | 12 | 2026-07-10 |
| UTN7421 | - | 11 | 2026-07-10 |
| UTN2226 | - | 9 | 2026-07-12 |
| UTN2225 | - | 9 | 2026-07-12 |
| UTN9123 | Trans-Ulgii | 7 | 2026-05-06 |
| UTN3624 | - | 7 | 2026-07-06 |
| UTN9148 | - | 6 | 2026-07-08 |
| UTN9147 | - | 6 | 2026-07-01 |
| UTN9126 | - | 5 | 2026-07-05 |
| UTN7022 | - | 5 | 2026-05-26 |
| UTN7021 | Trans-Ulgii | 5 | 2026-05-26 |
| UTN7126 | Trans-Ulgii | 4 | 2026-04-15 |
| UTN7125 | Trans-Ulgii | 4 | 2026-04-15 |
| UTN3623 | - | 4 | 2026-07-06 |
| UTN2323 | - | 4 | 2026-06-25 |
| UTN2248 | Trans-Ulgii | 4 | 2026-06-13 |
| UTN9178 | Trans-Ulgii | 3 | 2026-06-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UTN9121 | - | Jul 14, 02:00 UTC | Jul 14, 02:30 UTC | 30m |
| 2026-07-13 | UTN9124 | - | Jul 13, 13:55 UTC | Jul 13, 22:30 UTC | 8h 35m |
| 2026-07-13 | UTN9127 | - | Jul 13, 03:01 UTC | Jul 13, 12:30 UTC | 9h 30m |
| 2026-07-12 | UTN2225 | - | Jul 12, 12:55 UTC | Jul 13, 00:05 UTC | 11h 10m |
| 2026-07-12 | UTN2226 | - | Jul 12, 07:40 UTC | Jul 12, 11:25 UTC | 3h 45m |
| 2026-07-12 | UTN9125 | - | Jul 12, 02:05 UTC | Jul 12, 05:30 UTC | 3h 25m |
| 2026-07-11 | UTN9122 | BUD → KTW | Jul 11, 12:45 UTC | Jul 11, 23:20 UTC | 10h 35m |
| 2026-07-11 | UTN9121 | - | Jul 11, 02:15 UTC | Jul 11, 11:15 UTC | 9h 0m |
| 2026-07-10 | UTN9124 | - | Jul 10, 19:25 UTC | Jul 10, 23:00 UTC | 3h 35m |
| 2026-07-10 | UTN7421 | - | Jul 10, 12:55 UTC | Jul 10, 16:35 UTC | 3h 40m |
| 2026-07-10 | UTN7422 | - | Jul 10, 01:55 UTC | Jul 10, 11:30 UTC | 9h 35m |
| 2026-07-09 | UTN9122 | - | Jul 9, 12:55 UTC | Jul 9, 22:30 UTC | 9h 35m |
| 2026-07-09 | UTN9121 | - | Jul 9, 02:05 UTC | Jul 9, 11:30 UTC | 9h 25m |
| 2026-07-08 | UTN9148 | - | Jul 8, 01:00 UTC | Jul 8, 10:30 UTC | 9h 30m |
| 2026-07-07 | UTN9122 | HRG → KTW | Jul 7, 12:20 UTC | Jul 7, 23:20 UTC | 11h 0m |
| 2026-07-07 | UTN9121 | - | Jul 7, 02:10 UTC | Jul 7, 11:10 UTC | 9h 0m |
| 2026-07-06 | UTN9124 | - | Jul 6, 20:15 UTC | Jul 6, 23:05 UTC | 2h 50m |
| 2026-07-06 | UTN3623 | - | Jul 6, 14:20 UTC | Jul 6, 20:10 UTC | 5h 50m |
| 2026-07-06 | UTN3624 | - | Jul 6, 08:50 UTC | Jul 6, 11:55 UTC | 3h 5m |
| 2026-07-05 | UTN9126 | - | Jul 5, 14:40 UTC | Jul 6, 00:10 UTC | 9h 30m |
| 2026-07-05 | UTN2226 | - | Jul 5, 01:50 UTC | Jul 5, 11:25 UTC | 9h 35m |
| 2026-07-04 | UTN9122 | HRG → KTW | Jul 4, 12:40 UTC | Jul 4, 23:20 UTC | 10h 40m |
| 2026-07-04 | UTN3624 | - | Jul 4, 01:55 UTC | Jul 4, 11:10 UTC | 9h 15m |
| 2026-07-03 | UTN7421 | - | Jul 3, 13:15 UTC | Jul 3, 22:45 UTC | 9h 30m |
| 2026-07-03 | UTN7422 | - | Jul 3, 02:00 UTC | Jul 3, 12:00 UTC | 10h 0m |
| 2026-07-02 | UTN9122 | HRG → KTW | Jul 2, 13:00 UTC | Jul 2, 22:25 UTC | 9h 25m |
| 2026-07-02 | UTN9121 | - | Jul 2, 02:35 UTC | Jul 2, 11:45 UTC | 9h 10m |
| 2026-07-01 | UTN9147 | - | Jul 1, 01:05 UTC | Jul 1, 10:55 UTC | 9h 50m |
| 2026-06-30 | UTN9122 | HRG → KTW | Jun 30, 19:45 UTC | Jun 30, 23:00 UTC | 3h 15m |
| 2026-06-30 | UTN4223 | - | Jun 30, 12:25 UTC | Jun 30, 15:40 UTC | 3h 15m |
| 2026-06-30 | UTN9121 | - | Jun 30, 02:10 UTC | Jun 30, 10:55 UTC | 8h 45m |
| 2026-06-29 | UTN3623 | - | Jun 29, 13:24 UTC | Jun 29, 22:30 UTC | 9h 5m |
| 2026-06-29 | UTN9127 | - | Jun 29, 02:30 UTC | Jun 29, 11:45 UTC | 9h 15m |
| 2026-06-28 | UTN2225 | - | Jun 28, 13:40 UTC | Jun 29, 00:24 UTC | 10h 45m |
| 2026-06-28 | UTN2226 | - | Jun 28, 02:05 UTC | Jun 28, 11:39 UTC | 9h 35m |
| 2026-06-27 | UTN3623 | BUD → KTW | Jun 27, 12:29 UTC | Jun 27, 23:39 UTC | 11h 10m |
| 2026-06-27 | UTN3624 | - | Jun 27, 07:59 UTC | Jun 27, 11:14 UTC | 3h 15m |
| 2026-06-27 | UTN9121 | - | Jun 27, 02:09 UTC | Jun 27, 05:39 UTC | 3h 30m |
| 2026-06-26 | UTN7421 | POZ → POZ | Jun 26, 12:59 UTC | Jun 26, 23:04 UTC | 10h 5m |
| 2026-06-26 | UTN7422 | KTW → POZ | Jun 26, 02:00 UTC | Jun 26, 11:40 UTC | 9h 40m |
| 2026-06-25 | UTN2323 | - | Jun 25, 12:54 UTC | Jun 25, 22:39 UTC | 9h 45m |
| 2026-06-25 | UTN9121 | - | Jun 25, 01:59 UTC | Jun 25, 11:35 UTC | 9h 35m |
| 2026-06-24 | UTN9148 | - | Jun 24, 08:45 UTC | Jun 24, 17:55 UTC | 9h 10m |
| 2026-06-23 | UTN9122 | HRG → KTW | Jun 23, 12:55 UTC | Jun 23, 23:00 UTC | 10h 5m |
| 2026-06-23 | UTN9121 | - | Jun 23, 01:59 UTC | Jun 23, 11:04 UTC | 9h 5m |
| 2026-06-22 | UTN9124 | - | Jun 22, 13:14 UTC | Jun 22, 22:30 UTC | 9h 15m |
| 2026-06-22 | UTN9127 | - | Jun 22, 02:25 UTC | Jun 22, 11:35 UTC | 9h 10m |
| 2026-06-21 | UTN2225 | WAW → HRG | Jun 21, 13:20 UTC | Jun 22, 00:04 UTC | 10h 45m |
| 2026-06-21 | UTN9125 | KTW → HRG | Jun 21, 02:10 UTC | Jun 21, 11:55 UTC | 9h 45m |
| 2026-06-20 | UTN9122 | HRG → KTW | Jun 20, 12:34 UTC | Jun 20, 23:29 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 UR-AZE page for operator, model, and routing details .