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
- 185
- Distinct callsigns
- 20
- Country
- UA
- Last broadcast
- Jul 20, 21:50 UTC
Current 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 | - | 19 | 2026-07-20 |
| UTN9148 | Trans-Ulgii | 18 | 2026-07-19 |
| UTN9178 | Trans-Ulgii | 12 | 2026-07-18 |
| UTN9147 | - | 12 | 2026-07-12 |
| UTN9124 | - | 11 | 2026-07-15 |
| UTN2248 | Trans-Ulgii | 10 | 2026-07-18 |
| UTN9177 | - | 9 | 2026-07-09 |
| UTN9122 | Trans-Ulgii | 9 | 2026-06-13 |
| UTN3623 | - | 8 | 2026-07-01 |
| UTN4225 | - | 7 | 2026-07-20 |
| UTN9121 | Trans-Ulgii | 6 | 2026-06-13 |
| UTN7022 | - | 6 | 2026-07-06 |
| UTN2247 | Trans-Ulgii | 6 | 2026-07-11 |
| UTN7021 | Trans-Ulgii | 5 | 2026-06-30 |
| UTN4278 | - | 5 | 2026-07-17 |
| UTN4277 | Trans-Ulgii | 5 | 2026-06-26 |
| UTN4256 | - | 5 | 2026-07-20 |
| UTN4255 | - | 5 | 2026-07-20 |
| UTN4226 | - | 5 | 2026-07-13 |
| UTN3647 | - | 4 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | UTN4225 | - | Jul 20, 18:35 UTC | Jul 20, 21:50 UTC | 3h 15m |
| 2026-07-20 | UTN4256 | - | Jul 20, 15:35 UTC | Jul 20, 17:05 UTC | 1h 30m |
| 2026-07-20 | UTN4255 | - | Jul 20, 13:05 UTC | Jul 20, 14:20 UTC | 1h 15m |
| 2026-07-20 | UTN9123 | - | Jul 20, 02:20 UTC | Jul 20, 11:40 UTC | 9h 20m |
| 2026-07-19 | UTN9148 | RMF → KTW | Jul 19, 02:55 UTC | Jul 19, 12:25 UTC | 9h 30m |
| 2026-07-18 | UTN9178 | RMF → KTW | Jul 18, 14:05 UTC | Jul 19, 00:00 UTC | 9h 55m |
| 2026-07-18 | UTN2248 | WAW → RMF | Jul 18, 01:20 UTC | Jul 18, 12:00 UTC | 10h 41m |
| 2026-07-17 | UTN9148 | - | Jul 17, 12:10 UTC | Jul 17, 22:00 UTC | 9h 50m |
| 2026-07-17 | UTN4278 | - | Jul 17, 01:20 UTC | Jul 17, 10:25 UTC | 9h 5m |
| 2026-07-16 | UTN9178 | - | Jul 16, 12:30 UTC | Jul 16, 21:40 UTC | 9h 10m |
| 2026-07-16 | UTN3648 | - | Jul 16, 01:20 UTC | Jul 16, 10:35 UTC | 9h 15m |
| 2026-07-15 | UTN9124 | - | Jul 15, 12:50 UTC | Jul 15, 23:50 UTC | 11h 0m |
| 2026-07-15 | UTN3624 | - | Jul 15, 02:05 UTC | Jul 15, 11:20 UTC | 9h 15m |
| 2026-07-14 | UTN9130 | - | Jul 14, 12:35 UTC | Jul 14, 23:45 UTC | 11h 9m |
| 2026-07-13 | UTN4225 | BTS → BUD | Jul 13, 18:35 UTC | Jul 14, 11:10 UTC | 16h 35m |
| 2026-07-13 | UTN4256 | - | Jul 13, 15:40 UTC | Jul 13, 17:10 UTC | 1h 30m |
| 2026-07-13 | UTN4255 | BTS → BOJ | Jul 13, 13:10 UTC | Jul 13, 14:35 UTC | 1h 25m |
| 2026-07-13 | UTN4226 | - | Jul 13, 02:30 UTC | Jul 13, 11:50 UTC | 9h 20m |
| 2026-07-12 | UTN9147 | - | Jul 12, 02:45 UTC | Jul 12, 12:01 UTC | 9h 15m |
| 2026-07-11 | UTN2247 | WAW → RMF | Jul 11, 14:05 UTC | Jul 11, 23:45 UTC | 9h 40m |
| 2026-07-11 | UTN2248 | - | Jul 11, 01:35 UTC | Jul 11, 11:45 UTC | 10h 10m |
| 2026-07-10 | UTN9148 | - | Jul 10, 12:20 UTC | Jul 10, 21:40 UTC | 9h 20m |
| 2026-07-10 | UTN4278 | - | Jul 10, 01:05 UTC | Jul 10, 10:55 UTC | 9h 50m |
| 2026-07-09 | UTN9178 | - | Jul 9, 12:20 UTC | Jul 9, 21:30 UTC | 9h 10m |
| 2026-07-09 | UTN9177 | - | Jul 9, 02:05 UTC | Jul 9, 11:05 UTC | 9h 0m |
| 2026-07-08 | UTN9124 | - | Jul 8, 12:45 UTC | Jul 9, 00:15 UTC | 11h 30m |
| 2026-07-08 | UTN9123 | - | Jul 8, 01:50 UTC | Jul 8, 11:20 UTC | 9h 30m |
| 2026-07-07 | UTN9130 | - | Jul 7, 13:00 UTC | Jul 7, 23:55 UTC | 10h 55m |
| 2026-07-07 | UTN4001 | VNO → BUD | Jul 7, 10:20 UTC | Jul 7, 11:45 UTC | 1h 25m |
| 2026-07-06 | UTN7022 | BTS → VNO | Jul 6, 18:30 UTC | Jul 7, 08:55 UTC | 14h 25m |
| 2026-07-06 | UTN4256 | - | Jul 6, 15:45 UTC | Jul 6, 17:10 UTC | 1h 25m |
| 2026-07-06 | UTN4255 | BTS → BOJ | Jul 6, 12:55 UTC | Jul 6, 14:25 UTC | 1h 30m |
| 2026-07-06 | UTN9123 | - | Jul 6, 02:05 UTC | Jul 6, 11:20 UTC | 9h 15m |
| 2026-07-05 | UTN9148 | - | Jul 5, 02:40 UTC | Jul 5, 12:20 UTC | 9h 40m |
| 2026-07-04 | UTN2247 | WAW → RMF | Jul 4, 13:55 UTC | Jul 4, 23:55 UTC | 10h 0m |
| 2026-07-04 | UTN2248 | - | Jul 4, 01:20 UTC | Jul 4, 11:40 UTC | 10h 20m |
| 2026-07-03 | UTN9148 | - | Jul 3, 12:10 UTC | Jul 3, 21:40 UTC | 9h 30m |
| 2026-07-03 | UTN4278 | - | Jul 3, 01:10 UTC | Jul 3, 10:40 UTC | 9h 30m |
| 2026-07-02 | UTN9178 | - | Jul 2, 12:25 UTC | Jul 2, 21:50 UTC | 9h 25m |
| 2026-07-02 | UTN9177 | - | Jul 2, 01:15 UTC | Jul 2, 10:35 UTC | 9h 20m |
| 2026-07-01 | UTN3623 | - | Jul 1, 12:45 UTC | Jul 1, 23:15 UTC | 10h 30m |
| 2026-07-01 | UTN9123 | - | Jul 1, 02:15 UTC | Jul 1, 11:25 UTC | 9h 10m |
| 2026-06-30 | UTN7021 | VNO → HRG | Jun 30, 11:55 UTC | Jun 30, 23:55 UTC | 12h 0m |
| 2026-06-29 | UTN7022 | BTS → VNO | Jun 29, 19:29 UTC | Jun 30, 10:10 UTC | 14h 40m |
| 2026-06-29 | UTN4256 | - | Jun 29, 16:50 UTC | Jun 29, 18:14 UTC | 1h 25m |
| 2026-06-29 | UTN4255 | - | Jun 29, 13:39 UTC | Jun 29, 15:14 UTC | 1h 35m |
| 2026-06-29 | UTN4226 | - | Jun 29, 02:14 UTC | Jun 29, 11:29 UTC | 9h 15m |
| 2026-06-28 | UTN9147 | - | Jun 28, 02:34 UTC | Jun 28, 12:15 UTC | 9h 40m |
| 2026-06-27 | UTN2247 | WAW → RMF | Jun 27, 14:00 UTC | Jun 27, 23:55 UTC | 9h 55m |
| 2026-06-27 | UTN2248 | - | Jun 27, 01:24 UTC | Jun 27, 11:55 UTC | 10h 30m |
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 .