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
- 165
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 23d 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 | - | 29 | 2026-07-15 |
| UZB561 | Uzbekistan Airways | 24 | 2026-07-25 |
| UZB531 | Uzbekistan Airways | 20 | 2026-07-23 |
| UZB532 | Uzbekistan Airways | 9 | 2026-07-24 |
| UZB510 | - | 9 | 2026-07-08 |
| UZB342 | - | 8 | 2026-07-22 |
| UZB251 | - | 8 | 2026-07-21 |
| UZB341 | - | 7 | 2026-07-24 |
| UZB211 | - | 6 | 2026-07-20 |
| UZB3223 | - | 4 | 2026-07-06 |
| UZB252 | Uzbekistan Airways | 4 | 2026-07-21 |
| UZB212 | Uzbekistan Airways | 4 | 2026-07-20 |
| UZB3224 | - | 3 | 2026-07-06 |
| UZB281 | - | 3 | 2026-06-13 |
| UZB256 | Uzbekistan Airways | 3 | 2026-07-24 |
| UZB633 | Uzbekistan Airways | 2 | 2026-05-27 |
| UZB536 | Uzbekistan Airways | 2 | 2026-05-26 |
| UZB3234 | - | 2 | 2026-07-11 |
| UZB282 | - | 2 | 2026-06-13 |
| UZB271 | Uzbekistan Airways | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UZB561 | TAS → CXR | Jul 25, 15:35 UTC | Jul 26, 10:00 UTC | 18h 26m |
| 2026-07-25 | UZB561 | TAS → CXR | Jul 25, 13:35 UTC | Jul 26, 10:00 UTC | 20h 26m |
| 2026-07-25 | UZB561 | TAS → CXR | Jul 25, 13:00 UTC | Jul 26, 10:00 UTC | 21h 1m |
| 2026-07-25 | UZB561 | TAS → CXR | Jul 25, 09:35 UTC | Jul 26, 09:30 UTC | 23h 56m |
| 2026-07-25 | UZB561 | TAS → CXR | Jul 25, 07:35 UTC | Jul 26, 07:25 UTC | 23h 51m |
| 2026-07-25 | UZB561 | TAS → CXR | Jul 25, 07:05 UTC | Jul 26, 02:00 UTC | 18h 55m |
| 2026-07-24 | UZB341 | - | Jul 24, 23:35 UTC | Jul 25, 23:30 UTC | 23h 55m |
| 2026-07-24 | UZB341 | - | Jul 24, 21:35 UTC | Jul 25, 21:30 UTC | 23h 55m |
| 2026-07-24 | UZB256 | MXP → TAS | Jul 24, 19:55 UTC | Jul 25, 15:50 UTC | 19h 55m |
| 2026-07-24 | UZB255 | TAS → MXP | Jul 24, 05:00 UTC | Jul 24, 17:50 UTC | 12h 50m |
| 2026-07-24 | UZB532 | BKK → TAS | Jul 24, 01:50 UTC | Jul 24, 04:25 UTC | 2h 35m |
| 2026-07-23 | UZB531 | TAS → BKK | Jul 23, 09:00 UTC | Jul 24, 00:10 UTC | 15h 10m |
| 2026-07-22 | UZB342 | - | Jul 22, 12:10 UTC | Jul 23, 06:45 UTC | 18h 35m |
| 2026-07-21 | UZB252 | CDG → TAS | Jul 21, 18:50 UTC | Jul 22, 10:25 UTC | 15h 35m |
| 2026-07-21 | UZB251 | - | Jul 21, 12:10 UTC | Jul 21, 16:25 UTC | 4h 15m |
| 2026-07-20 | UZB212 | RIX → TAS | Jul 20, 12:20 UTC | Jul 20, 13:35 UTC | 1h 15m |
| 2026-07-20 | UZB211 | - | Jul 20, 08:35 UTC | Jul 20, 08:50 UTC | 15m |
| 2026-07-20 | UZB211 | - | Jul 20, 06:35 UTC | Jul 20, 06:45 UTC | 10m |
| 2026-07-17 | UZB532 | BKK → TAS | Jul 17, 01:35 UTC | Jul 17, 05:39 UTC | 4h 5m |
| 2026-07-16 | UZB531 | - | Jul 16, 19:35 UTC | Jul 16, 23:49 UTC | 4h 15m |
| 2026-07-16 | UZB531 | - | Jul 16, 04:00 UTC | Jul 16, 23:49 UTC | 19h 50m |
| 2026-07-16 | UZB531 | - | Jul 16, 03:25 UTC | Jul 16, 23:49 UTC | 20h 25m |
| 2026-07-15 | UZB562 | - | Jul 15, 07:35 UTC | Jul 16, 03:20 UTC | 19h 45m |
| 2026-07-15 | UZB562 | - | Jul 15, 06:15 UTC | Jul 16, 03:20 UTC | 21h 5m |
| 2026-07-15 | UZB562 | - | Jul 15, 01:35 UTC | Jul 16, 01:30 UTC | 23h 55m |
| 2026-07-14 | UZB561 | - | Jul 14, 21:50 UTC | Jul 15, 10:25 UTC | 12h 34m |
| 2026-07-14 | UZB561 | - | Jul 14, 05:35 UTC | Jul 15, 02:05 UTC | 20h 29m |
| 2026-07-14 | UZB561 | - | Jul 14, 03:35 UTC | Jul 15, 02:05 UTC | 22h 29m |
| 2026-07-14 | UZB532 | - | Jul 14, 02:10 UTC | Jul 15, 01:30 UTC | 23h 19m |
| 2026-07-13 | UZB531 | - | Jul 13, 20:20 UTC | Jul 14, 00:30 UTC | 4h 10m |
| 2026-07-12 | UZB531 | - | Jul 12, 22:25 UTC | Jul 13, 21:15 UTC | 22h 50m |
| 2026-07-12 | UZB204 | LHR → TAS | Jul 12, 18:20 UTC | Jul 12, 22:50 UTC | 4h 30m |
| 2026-07-12 | UZB203 | TAS → LHR | Jul 12, 13:01 UTC | Jul 12, 15:50 UTC | 2h 50m |
| 2026-07-11 | UZB203 | TAS → LHR | Jul 11, 15:45 UTC | Jul 12, 15:30 UTC | 23h 45m |
| 2026-07-11 | UZB3234 | - | Jul 11, 13:35 UTC | Jul 12, 13:30 UTC | 23h 55m |
| 2026-07-11 | UZB3234 | - | Jul 11, 12:00 UTC | Jul 11, 15:50 UTC | 3h 50m |
| 2026-07-10 | UZB256 | - | Jul 10, 20:15 UTC | Jul 11, 10:30 UTC | 14h 15m |
| 2026-07-10 | UZB255 | TAS → MXP | Jul 10, 01:50 UTC | Jul 10, 18:15 UTC | 16h 25m |
| 2026-07-09 | UZB531 | - | Jul 9, 19:40 UTC | Jul 9, 23:50 UTC | 4h 10m |
| 2026-07-09 | UZB531 | - | Jul 9, 03:50 UTC | Jul 9, 23:50 UTC | 20h 0m |
| 2026-07-09 | UZB531 | - | Jul 9, 01:35 UTC | Jul 9, 23:50 UTC | 22h 15m |
| 2026-07-09 | UZB531 | - | Jul 9, 01:05 UTC | Jul 9, 23:30 UTC | 22h 25m |
| 2026-07-08 | UZB510 | - | Jul 8, 10:05 UTC | Jul 9, 04:45 UTC | 18h 40m |
| 2026-07-07 | UZB252 | CDG → TAS | Jul 7, 18:35 UTC | Jul 8, 10:10 UTC | 15h 35m |
| 2026-07-07 | UZB251 | TAS → CDG | Jul 7, 11:35 UTC | Jul 7, 16:20 UTC | 4h 45m |
| 2026-07-06 | UZB251 | TAS → CDG | Jul 6, 15:35 UTC | Jul 7, 15:30 UTC | 23h 55m |
| 2026-07-06 | UZB3224 | - | Jul 6, 14:25 UTC | Jul 7, 11:50 UTC | 21h 25m |
| 2026-07-06 | UZB3223 | - | Jul 6, 10:00 UTC | Jul 6, 12:35 UTC | 2h 35m |
| 2026-07-04 | UZB562 | CXR → TAS | Jul 4, 20:50 UTC | Jul 5, 10:25 UTC | 13h 35m |
| 2026-07-04 | UZB562 | CXR → TAS | Jul 4, 13:35 UTC | Jul 5, 10:25 UTC | 20h 50m |
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 .