sensors Mode-S transponder
507C60
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32103 · AIRBUS A-321neo
- Hex
- 507C60
- Octal
- 24076140
- Decimal
- 5,274,720
- Country
- UZ
- Tail
- UK-32103
- Type
- A21N
- Flights observed
- 98
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 55m ago
Last known position
Country allocation
The ICAO 24-bit address 507C60 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 |
|---|---|---|---|
| UZB342 | Uzbekistan Airways | 18 | 2026-06-06 |
| UZB252 | Uzbekistan Airways | 11 | 2026-06-05 |
| UZB510 | - | 8 | 2026-06-02 |
| UZB341 | - | 8 | 2026-06-05 |
| UZB562 | Uzbekistan Airways | 6 | 2026-06-10 |
| UZB561 | Uzbekistan Airways | 6 | 2026-06-13 |
| UZB251 | Uzbekistan Airways | 6 | 2026-06-05 |
| UZB203 | Uzbekistan Airways | 6 | 2026-06-07 |
| UZB554 | Uzbekistan Airways | 5 | 2026-06-04 |
| UZB531 | Uzbekistan Airways | 4 | 2026-06-11 |
| UZB204 | Uzbekistan Airways | 4 | 2026-06-07 |
| UZB613 | Uzbekistan Airways | 2 | 2026-06-10 |
| UZB553 | Uzbekistan Airways | 2 | 2026-05-28 |
| UZB532 | Uzbekistan Airways | 2 | 2026-06-09 |
| UZB281 | Uzbekistan Airways | 2 | 2026-06-05 |
| UZB746 | Uzbekistan Airways | 1 | 2026-04-26 |
| UZB745 | Uzbekistan Airways | 1 | 2026-04-25 |
| UZB612 | Uzbekistan Airways | 1 | 2026-05-14 |
| UZB282 | Uzbekistan Airways | 1 | 2026-05-25 |
| UZB256 | - | 1 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-13 | UZB561 | TAS → CXR | Jun 13, 12:35 UTC | Jun 14, 01:35 UTC | 13h 0m |
| 2026-06-12 | UZB256 | - | Jun 12, 19:30 UTC | Jun 13, 10:35 UTC | 15h 4m |
| 2026-06-12 | UZB255 | TAS → MXP | Jun 12, 01:30 UTC | Jun 12, 17:50 UTC | 16h 20m |
| 2026-06-11 | UZB531 | TAS → BKK | Jun 11, 11:00 UTC | Jun 11, 23:40 UTC | 12h 40m |
| 2026-06-10 | UZB531 | TAS → BKK | Jun 10, 21:15 UTC | Jun 11, 20:00 UTC | 22h 45m |
| 2026-06-10 | UZB613 | TAS → VKO | Jun 10, 16:05 UTC | Jun 11, 11:00 UTC | 18h 55m |
| 2026-06-10 | UZB613 | TAS → VKO | Jun 10, 15:55 UTC | Jun 11, 11:00 UTC | 19h 5m |
| 2026-06-10 | UZB562 | CXR → TAS | Jun 10, 05:00 UTC | Jun 10, 21:20 UTC | 16h 20m |
| 2026-06-10 | UZB562 | CXR → TAS | Jun 10, 00:15 UTC | Jun 10, 21:20 UTC | 21h 5m |
| 2026-06-09 | UZB562 | CXR → TAS | Jun 9, 22:05 UTC | Jun 10, 21:20 UTC | 23h 15m |
| 2026-06-09 | UZB562 | CXR → TAS | Jun 9, 21:00 UTC | Jun 10, 16:35 UTC | 19h 35m |
| 2026-06-09 | UZB561 | TAS → CXR | Jun 9, 04:05 UTC | Jun 10, 01:25 UTC | 21h 20m |
| 2026-06-09 | UZB532 | BKK → TAS | Jun 9, 02:05 UTC | Jun 10, 01:25 UTC | 23h 20m |
| 2026-06-09 | UZB532 | BKK → TAS | Jun 9, 01:45 UTC | Jun 9, 23:30 UTC | 21h 45m |
| 2026-06-08 | UZB531 | TAS → BKK | Jun 8, 19:45 UTC | Jun 8, 23:50 UTC | 4h 5m |
| 2026-06-07 | UZB531 | TAS → BKK | Jun 7, 20:05 UTC | Jun 8, 20:00 UTC | 23h 55m |
| 2026-06-07 | UZB204 | LHR → TAS | Jun 7, 17:35 UTC | Jun 7, 20:05 UTC | 2h 30m |
| 2026-06-07 | UZB203 | TAS → LHR | Jun 7, 10:40 UTC | Jun 7, 15:25 UTC | 4h 45m |
| 2026-06-06 | UZB203 | TAS → LHR | Jun 6, 14:30 UTC | Jun 7, 14:00 UTC | 23h 30m |
| 2026-06-06 | UZB342 | SSH → TAS | Jun 6, 12:30 UTC | Jun 7, 11:55 UTC | 23h 25m |
| 2026-06-05 | UZB341 | - | Jun 5, 20:05 UTC | Jun 6, 15:39 UTC | 19h 35m |
| 2026-06-05 | UZB252 | CDG → TAS | Jun 5, 18:25 UTC | Jun 6, 15:39 UTC | 21h 15m |
| 2026-06-05 | UZB251 | TAS → CDG | Jun 5, 03:35 UTC | Jun 5, 17:00 UTC | 13h 25m |
| 2026-06-05 | UZB281 | TAS → IST | Jun 5, 01:20 UTC | Jun 5, 01:45 UTC | 25m |
| 2026-06-04 | UZB281 | TAS → IST | Jun 4, 09:05 UTC | Jun 5, 00:35 UTC | 15h 30m |
| 2026-06-04 | UZB554 | KUL → TAS | Jun 4, 04:40 UTC | Jun 5, 00:35 UTC | 19h 55m |
| 2026-06-03 | UZB342 | SSH → TAS | Jun 3, 08:05 UTC | Jun 4, 02:20 UTC | 18h 15m |
| 2026-06-03 | UZB341 | - | Jun 3, 06:55 UTC | Jun 4, 02:20 UTC | 19h 25m |
| 2026-06-02 | UZB341 | - | Jun 2, 22:15 UTC | Jun 3, 21:40 UTC | 23h 25m |
| 2026-06-02 | UZB341 | - | Jun 2, 20:05 UTC | Jun 3, 15:05 UTC | 19h 0m |
| 2026-06-02 | UZB252 | CDG → TAS | Jun 2, 18:45 UTC | Jun 3, 15:05 UTC | 20h 20m |
| 2026-06-02 | UZB510 | - | Jun 2, 01:20 UTC | Jun 2, 16:15 UTC | 14h 55m |
| 2026-06-01 | UZB510 | - | Jun 1, 21:30 UTC | Jun 2, 16:15 UTC | 18h 45m |
| 2026-05-31 | UZB562 | CXR → TAS | May 31, 08:25 UTC | May 31, 21:35 UTC | 13h 10m |
| 2026-05-31 | UZB562 | CXR → TAS | May 31, 00:15 UTC | May 31, 21:35 UTC | 21h 20m |
| 2026-05-30 | UZB561 | TAS → CXR | May 30, 22:05 UTC | May 31, 21:35 UTC | 23h 30m |
| 2026-05-30 | UZB561 | TAS → CXR | May 30, 20:30 UTC | May 31, 09:50 UTC | 13h 20m |
| 2026-05-30 | UZB561 | TAS → CXR | May 30, 12:05 UTC | May 31, 09:50 UTC | 21h 45m |
| 2026-05-30 | UZB561 | TAS → CXR | May 30, 10:25 UTC | May 31, 09:50 UTC | 23h 25m |
| 2026-05-30 | UZB231 | TAS → FRA | May 30, 06:35 UTC | May 30, 07:15 UTC | 40m |
| 2026-05-28 | UZB554 | KUL → TAS | May 28, 08:45 UTC | May 28, 09:50 UTC | 1h 5m |
| 2026-05-28 | UZB554 | KUL → TAS | May 28, 04:30 UTC | May 28, 04:40 UTC | 10m |
| 2026-05-28 | UZB553 | TAS → KUL | May 28, 02:10 UTC | May 28, 02:30 UTC | 20m |
| 2026-05-27 | UZB342 | SSH → TAS | May 27, 07:15 UTC | May 27, 22:30 UTC | 15h 15m |
| 2026-05-26 | UZB342 | SSH → TAS | May 26, 22:29 UTC | May 27, 22:00 UTC | 23h 31m |
| 2026-05-26 | UZB342 | SSH → TAS | May 26, 20:05 UTC | May 27, 15:40 UTC | 19h 36m |
| 2026-05-26 | UZB342 | SSH → TAS | May 26, 18:45 UTC | May 27, 15:40 UTC | 20h 56m |
| 2026-05-26 | UZB510 | - | May 26, 02:00 UTC | May 26, 16:45 UTC | 14h 45m |
| 2026-05-25 | UZB510 | - | May 25, 04:15 UTC | May 26, 04:00 UTC | 23h 44m |
| 2026-05-25 | UZB282 | IST → TAS | May 25, 03:15 UTC | May 26, 02:00 UTC | 22h 45m |
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-32103 page for operator, model, and routing details .