sensors Mode-S transponder
507C5E
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32101 · AIRBUS A-321neo
- Hex
- 507C5E
- Octal
- 24076136
- Decimal
- 5,274,718
- Country
- UZ
- Tail
- UK-32101
- Type
- A21N
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 7h ago
Current position
Country allocation
The ICAO 24-bit address 507C5E falls within the block assigned to Uzbekistan (UZ) by ICAO Annex 10, Volume III. Every aircraft registered in Uzbekistan 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 |
|---|---|---|---|
| UZB562 | Uzbekistan Airways | 23 | 2026-06-24 |
| UZB561 | Uzbekistan Airways | 15 | 2026-06-27 |
| UZB531 | - | 10 | 2026-06-25 |
| UZB510 | - | 8 | 2026-06-24 |
| UZB342 | - | 8 | 2026-07-04 |
| UZB532 | - | 6 | 2026-06-26 |
| UZB341 | - | 5 | 2026-07-03 |
| UZB251 | Uzbekistan Airways | 5 | 2026-07-03 |
| UZB211 | - | 4 | 2026-06-29 |
| UZB3223 | - | 3 | 2026-07-02 |
| UZB281 | - | 3 | 2026-06-13 |
| UZB212 | Uzbekistan Airways | 3 | 2026-05-25 |
| UZB633 | Uzbekistan Airways | 2 | 2026-05-27 |
| UZB536 | Uzbekistan Airways | 2 | 2026-05-26 |
| UZB3224 | Uzbekistan Airways | 2 | 2026-06-14 |
| UZB282 | - | 2 | 2026-06-13 |
| UZB271 | Uzbekistan Airways | 2 | 2026-06-04 |
| UZB252 | Uzbekistan Airways | 2 | 2026-06-30 |
| UZB231 | Uzbekistan Airways | 2 | 2026-05-22 |
| UZB613 | Uzbekistan Airways | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-04 | UZB342 | - | Jul 4, 12:25 UTC | Jul 4, 15:25 UTC | 3h 0m |
| 2026-07-03 | UZB341 | - | Jul 3, 18:25 UTC | Jul 4, 10:20 UTC | 15h 55m |
| 2026-07-03 | UZB251 | TAS → CDG | Jul 3, 13:35 UTC | Jul 3, 16:20 UTC | 2h 45m |
| 2026-07-02 | UZB251 | TAS → CDG | Jul 2, 17:35 UTC | Jul 3, 16:20 UTC | 22h 45m |
| 2026-07-02 | UZB251 | TAS → CDG | Jul 2, 16:05 UTC | Jul 3, 15:30 UTC | 23h 25m |
| 2026-07-02 | UZB3223 | - | Jul 2, 12:05 UTC | Jul 2, 14:25 UTC | 2h 20m |
| 2026-06-30 | UZB252 | CDG → TAS | Jun 30, 19:25 UTC | Jun 30, 23:15 UTC | 3h 50m |
| 2026-06-30 | UZB251 | TAS → CDG | Jun 30, 02:10 UTC | Jun 30, 16:25 UTC | 14h 15m |
| 2026-06-29 | UZB3221 | - | Jun 29, 12:24 UTC | Jun 30, 00:35 UTC | 12h 10m |
| 2026-06-29 | UZB211 | - | Jun 29, 08:39 UTC | Jun 29, 08:54 UTC | 15m |
| 2026-06-27 | UZB561 | TAS → CXR | Jun 27, 15:34 UTC | Jun 28, 09:50 UTC | 18h 15m |
| 2026-06-27 | UZB561 | TAS → CXR | Jun 27, 13:35 UTC | Jun 28, 09:50 UTC | 20h 15m |
| 2026-06-27 | UZB561 | TAS → CXR | Jun 27, 12:45 UTC | Jun 28, 09:50 UTC | 21h 5m |
| 2026-06-26 | UZB252 | CDG → TAS | Jun 26, 19:20 UTC | Jun 27, 10:25 UTC | 15h 5m |
| 2026-06-26 | UZB532 | - | Jun 26, 01:39 UTC | Jun 26, 16:54 UTC | 15h 15m |
| 2026-06-25 | UZB531 | LHE → BKK | Jun 25, 19:20 UTC | Jun 25, 23:39 UTC | 4h 20m |
| 2026-06-25 | UZB531 | - | Jun 25, 03:34 UTC | Jun 25, 23:39 UTC | 20h 5m |
| 2026-06-25 | UZB531 | - | Jun 25, 00:49 UTC | Jun 25, 23:30 UTC | 22h 40m |
| 2026-06-24 | UZB510 | - | Jun 24, 20:44 UTC | Jun 25, 19:24 UTC | 22h 40m |
| 2026-06-24 | UZB510 | - | Jun 24, 07:34 UTC | Jun 25, 04:54 UTC | 21h 20m |
| 2026-06-24 | UZB562 | CXR → TAS | Jun 24, 05:34 UTC | Jun 25, 04:54 UTC | 23h 20m |
| 2026-06-24 | UZB562 | CXR → TAS | Jun 24, 04:59 UTC | Jun 25, 03:29 UTC | 22h 30m |
| 2026-06-23 | UZB562 | CXR → TAS | Jun 23, 23:44 UTC | Jun 24, 21:09 UTC | 21h 25m |
| 2026-06-23 | UZB562 | CXR → TAS | Jun 23, 21:34 UTC | Jun 24, 21:09 UTC | 23h 35m |
| 2026-06-23 | UZB561 | TAS → CXR | Jun 23, 20:29 UTC | Jun 24, 09:24 UTC | 12h 55m |
| 2026-06-23 | UZB561 | TAS → CXR | Jun 23, 05:34 UTC | Jun 24, 05:29 UTC | 23h 55m |
| 2026-06-23 | UZB561 | TAS → CXR | Jun 23, 03:34 UTC | Jun 24, 00:59 UTC | 21h 25m |
| 2026-06-23 | UZB561 | TAS → CXR | Jun 23, 01:54 UTC | Jun 24, 00:59 UTC | 23h 5m |
| 2026-06-22 | UZB531 | - | Jun 22, 19:49 UTC | Jun 22, 23:55 UTC | 4h 5m |
| 2026-06-20 | UZB561 | TAS → CXR | Jun 20, 13:34 UTC | Jun 21, 09:40 UTC | 20h 5m |
| 2026-06-20 | UZB561 | TAS → CXR | Jun 20, 12:30 UTC | Jun 21, 09:40 UTC | 21h 10m |
| 2026-06-20 | UZB561 | TAS → CXR | Jun 20, 09:34 UTC | Jun 21, 09:24 UTC | 23h 50m |
| 2026-06-20 | UZB561 | TAS → CXR | Jun 20, 07:44 UTC | Jun 21, 07:29 UTC | 23h 45m |
| 2026-06-20 | UZB561 | TAS → CXR | Jun 20, 06:45 UTC | Jun 21, 05:30 UTC | 22h 45m |
| 2026-06-19 | UZB256 | - | Jun 19, 19:19 UTC | Jun 20, 15:19 UTC | 20h 0m |
| 2026-06-19 | UZB532 | - | Jun 19, 01:29 UTC | Jun 19, 17:19 UTC | 15h 50m |
| 2026-06-18 | UZB531 | - | Jun 18, 19:35 UTC | Jun 18, 23:40 UTC | 4h 5m |
| 2026-06-18 | UZB531 | - | Jun 18, 02:15 UTC | Jun 18, 23:40 UTC | 21h 25m |
| 2026-06-18 | UZB531 | - | Jun 18, 00:35 UTC | Jun 18, 23:30 UTC | 22h 55m |
| 2026-06-17 | UZB510 | - | Jun 17, 09:35 UTC | Jun 18, 04:45 UTC | 19h 10m |
| 2026-06-17 | UZB510 | - | Jun 17, 07:35 UTC | Jun 18, 04:45 UTC | 21h 10m |
| 2026-06-17 | UZB562 | CXR → TAS | Jun 17, 05:35 UTC | Jun 18, 04:45 UTC | 23h 10m |
| 2026-06-17 | UZB562 | CXR → TAS | Jun 17, 05:15 UTC | Jun 18, 03:30 UTC | 22h 15m |
| 2026-06-17 | UZB562 | CXR → TAS | Jun 17, 00:15 UTC | Jun 17, 21:30 UTC | 21h 15m |
| 2026-06-16 | UZB562 | CXR → TAS | Jun 16, 21:35 UTC | Jun 17, 21:30 UTC | 23h 55m |
| 2026-06-16 | UZB562 | CXR → TAS | Jun 16, 21:05 UTC | Jun 17, 09:35 UTC | 12h 30m |
| 2026-06-16 | UZB561 | TAS → CXR | Jun 16, 05:34 UTC | Jun 17, 05:30 UTC | 23h 56m |
| 2026-06-16 | UZB561 | TAS → CXR | Jun 16, 03:39 UTC | Jun 17, 01:25 UTC | 21h 46m |
| 2026-06-16 | UZB532 | BKK → TAS | Jun 16, 02:04 UTC | Jun 17, 01:25 UTC | 23h 21m |
| 2026-06-15 | UZB531 | - | Jun 15, 11:30 UTC | Jun 16, 00:10 UTC | 12h 40m |
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 UK-32101 page for operator, model, and routing details .