sensors Mode-S transponder
5084E2
ICAO 24-bit transponder address · allocated to Ukraine
Currently assigned to UR-SLH · BOEING 737-800
- Hex
- 5084E2
- Octal
- 24102342
- Decimal
- 5,276,898
- Country
- UA
- Tail
- UR-SLH
- Type
- B738
- Flights observed
- 82
- Distinct callsigns
- 20
- Country
- UA
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 5084E2 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 |
|---|---|---|---|
| UTN9123 | Trans-Ulgii | 10 | 2026-05-27 |
| UTN9148 | Trans-Ulgii | 9 | 2026-05-29 |
| UTN9122 | Trans-Ulgii | 8 | 2026-05-23 |
| UTN9124 | Trans-Ulgii | 7 | 2026-05-08 |
| UTN9147 | Trans-Ulgii | 6 | 2026-05-24 |
| UTN9178 | Trans-Ulgii | 5 | 2026-04-30 |
| UTN9121 | Trans-Ulgii | 5 | 2026-05-23 |
| UTN3623 | Trans-Ulgii | 5 | 2026-05-27 |
| UTN9177 | Trans-Ulgii | 4 | 2026-05-30 |
| UTN7422 | Trans-Ulgii | 3 | 2026-05-15 |
| UTN4225 | Trans-Ulgii | 3 | 2026-05-25 |
| UTN2248 | Trans-Ulgii | 3 | 2026-04-25 |
| UTN7421 | Trans-Ulgii | 2 | 2026-05-15 |
| UTN3624 | Trans-Ulgii | 2 | 2026-05-16 |
| UTN2247 | Trans-Ulgii | 2 | 2026-04-25 |
| UTN2225 | Trans-Ulgii | 2 | 2026-05-03 |
| UTN9125 | Trans-Ulgii | 1 | 2026-05-03 |
| UTN4278 | - | 1 | 2026-05-29 |
| UTN4277 | Trans-Ulgii | 1 | 2026-05-22 |
| UTN3648 | - | 1 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UTN9177 | KTW → KTW | May 30, 00:55 UTC | May 30, 04:00 UTC | 3h 5m |
| 2026-05-29 | UTN9148 | RMF → KTW | May 29, 18:10 UTC | May 29, 22:05 UTC | 3h 55m |
| 2026-05-29 | UTN4278 | - | May 29, 01:00 UTC | May 29, 10:50 UTC | 9h 50m |
| 2026-05-28 | UTN3647 | - | May 28, 12:10 UTC | May 28, 21:40 UTC | 9h 30m |
| 2026-05-28 | UTN3648 | - | May 28, 01:15 UTC | May 28, 10:35 UTC | 9h 20m |
| 2026-05-27 | UTN3623 | BUD → HRG | May 27, 12:45 UTC | May 27, 23:10 UTC | 10h 25m |
| 2026-05-27 | UTN9123 | KTW → HRG | May 27, 01:59 UTC | May 27, 11:25 UTC | 9h 26m |
| 2026-05-25 | UTN4225 | BTS → HRG | May 25, 13:05 UTC | May 25, 22:10 UTC | 9h 4m |
| 2026-05-25 | UTN9123 | KTW → HRG | May 25, 02:20 UTC | May 25, 11:45 UTC | 9h 25m |
| 2026-05-24 | UTN9147 | KTW → RMF | May 24, 05:20 UTC | May 24, 14:45 UTC | 9h 25m |
| 2026-05-23 | UTN9122 | HRG → KTW | May 23, 13:05 UTC | May 24, 00:15 UTC | 11h 10m |
| 2026-05-23 | UTN9121 | KTW → HRG | May 23, 02:15 UTC | May 23, 11:25 UTC | 9h 9m |
| 2026-05-22 | UTN4277 | BTS → RMF | May 22, 12:25 UTC | May 22, 21:40 UTC | 9h 15m |
| 2026-05-22 | UTN9147 | KTW → RMF | May 22, 00:50 UTC | May 22, 10:50 UTC | 10h 0m |
| 2026-05-21 | UTN9122 | HRG → KTW | May 21, 02:35 UTC | May 21, 22:25 UTC | 19h 50m |
| 2026-05-21 | UTN9121 | KTW → HRG | May 21, 02:05 UTC | May 21, 22:25 UTC | 20h 20m |
| 2026-05-20 | UTN3623 | BUD → HRG | May 20, 15:25 UTC | May 21, 00:35 UTC | 9h 10m |
| 2026-05-20 | UTN9123 | KTW → HRG | May 20, 04:10 UTC | May 20, 13:20 UTC | 9h 11m |
| 2026-05-18 | UTN4225 | BTS → HRG | May 18, 13:20 UTC | May 18, 23:05 UTC | 9h 44m |
| 2026-05-18 | UTN9123 | KTW → HRG | May 18, 02:15 UTC | May 18, 12:05 UTC | 9h 50m |
| 2026-05-17 | UTN9148 | RMF → KTW | May 17, 02:50 UTC | May 17, 12:30 UTC | 9h 40m |
| 2026-05-16 | UTN3623 | BUD → HRG | May 16, 15:40 UTC | May 17, 01:15 UTC | 9h 35m |
| 2026-05-16 | UTN3624 | HRG → BUD | May 16, 02:10 UTC | May 16, 11:41 UTC | 9h 31m |
| 2026-05-15 | UTN7421 | POZ → POZ | May 15, 13:15 UTC | May 15, 23:30 UTC | 10h 14m |
| 2026-05-15 | UTN7422 | POZ → POZ | May 15, 02:00 UTC | May 15, 12:05 UTC | 10h 5m |
| 2026-05-14 | UTN9122 | HRG → KTW | May 14, 04:35 UTC | May 14, 22:35 UTC | 18h 0m |
| 2026-05-14 | UTN9122 | HRG → KTW | May 14, 02:35 UTC | May 14, 22:35 UTC | 20h 0m |
| 2026-05-14 | UTN9121 | KTW → HRG | May 14, 02:10 UTC | May 14, 22:35 UTC | 20h 25m |
| 2026-05-13 | UTN3623 | BUD → HRG | May 13, 13:45 UTC | May 13, 23:05 UTC | 9h 20m |
| 2026-05-13 | UTN3624 | HRG → BUD | May 13, 02:00 UTC | May 13, 12:20 UTC | 10h 20m |
| 2026-05-11 | UTN4225 | BTS → HRG | May 11, 13:30 UTC | May 11, 22:35 UTC | 9h 5m |
| 2026-05-11 | UTN9123 | KTW → HRG | May 11, 02:20 UTC | May 11, 12:15 UTC | 9h 55m |
| 2026-05-10 | UTN9148 | RMF → KTW | May 10, 02:45 UTC | May 10, 12:34 UTC | 9h 50m |
| 2026-05-09 | UTN9122 | HRG → KTW | May 9, 12:45 UTC | May 9, 23:35 UTC | 10h 50m |
| 2026-05-09 | UTN9121 | KTW → HRG | May 9, 02:05 UTC | May 9, 11:15 UTC | 9h 10m |
| 2026-05-08 | UTN9124 | HRG → KTW | May 8, 20:05 UTC | May 8, 23:35 UTC | 3h 30m |
| 2026-05-08 | UTN7422 | POZ → POZ | May 8, 01:55 UTC | May 8, 12:00 UTC | 10h 5m |
| 2026-05-07 | UTN9122 | HRG → KTW | May 7, 04:35 UTC | May 7, 23:09 UTC | 18h 35m |
| 2026-05-07 | UTN9122 | HRG → KTW | May 7, 02:35 UTC | May 7, 23:09 UTC | 20h 35m |
| 2026-05-07 | UTN9122 | HRG → KTW | May 7, 02:10 UTC | May 7, 23:09 UTC | 21h 0m |
| 2026-05-06 | UTN9148 | RMF → KTW | May 6, 08:50 UTC | May 6, 18:40 UTC | 9h 49m |
| 2026-05-04 | UTN9124 | HRG → KTW | May 4, 13:10 UTC | May 5, 00:15 UTC | 11h 6m |
| 2026-05-04 | UTN9123 | KTW → HRG | May 4, 02:30 UTC | May 4, 11:45 UTC | 9h 15m |
| 2026-05-03 | UTN2225 | WAW → HRG | May 3, 14:00 UTC | May 4, 00:15 UTC | 10h 15m |
| 2026-05-03 | UTN9125 | KTW → HRG | May 3, 02:00 UTC | May 3, 12:10 UTC | 10h 9m |
| 2026-05-02 | UTN3623 | BUD → HRG | May 2, 13:30 UTC | May 3, 00:01 UTC | 10h 30m |
| 2026-05-02 | UTN9121 | KTW → HRG | May 2, 02:00 UTC | May 2, 11:10 UTC | 9h 10m |
| 2026-05-01 | UTN7421 | POZ → POZ | May 1, 12:40 UTC | May 2, 00:20 UTC | 11h 40m |
| 2026-05-01 | UTN7422 | POZ → POZ | May 1, 01:45 UTC | May 1, 11:25 UTC | 9h 40m |
| 2026-04-30 | UTN9178 | RMF → KTW | Apr 30, 07:55 UTC | Apr 30, 18:05 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-SLH page for operator, model, and routing details .