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
- 186
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 2d ago
Current 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 |
|---|---|---|---|
| UZB561 | Uzbekistan Airways | 20 | 2026-07-21 |
| UZB342 | - | 20 | 2026-07-23 |
| UZB562 | Uzbekistan Airways | 17 | 2026-07-01 |
| UZB341 | - | 14 | 2026-07-23 |
| UZB251 | - | 14 | 2026-07-24 |
| UZB252 | Uzbekistan Airways | 13 | 2026-07-24 |
| UZB510 | - | 11 | 2026-07-01 |
| UZB203 | Uzbekistan Airways | 11 | 2026-07-05 |
| UZB531 | - | 9 | 2026-07-20 |
| UZB554 | - | 7 | 2026-06-25 |
| UZB281 | - | 6 | 2026-06-25 |
| UZB204 | Uzbekistan Airways | 6 | 2026-07-05 |
| UZB532 | Uzbekistan Airways | 5 | 2026-07-21 |
| UZB553 | - | 3 | 2026-06-24 |
| UZB3234 | - | 3 | 2026-07-25 |
| UZB613 | Uzbekistan Airways | 2 | 2026-06-10 |
| UZB601 | Uzbekistan Airways | 2 | 2026-07-26 |
| UZB3223 | - | 2 | 2026-06-28 |
| UZB282 | - | 2 | 2026-06-26 |
| UZB271 | - | 2 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UZB602 | DME → TAS | Jul 26, 21:35 UTC | Jul 26, 21:45 UTC | 10m |
| 2026-07-26 | UZB601 | TAS → DME | Jul 26, 18:05 UTC | Jul 26, 18:30 UTC | 25m |
| 2026-07-26 | UZB601 | TAS → DME | Jul 26, 17:15 UTC | Jul 26, 17:35 UTC | 20m |
| 2026-07-25 | UZB3234 | - | Jul 25, 12:45 UTC | Jul 25, 16:15 UTC | 3h 30m |
| 2026-07-24 | UZB252 | CDG → TAS | Jul 24, 18:35 UTC | Jul 25, 10:45 UTC | 16h 10m |
| 2026-07-24 | UZB251 | - | Jul 24, 11:50 UTC | Jul 24, 16:25 UTC | 4h 35m |
| 2026-07-23 | UZB251 | - | Jul 23, 18:05 UTC | Jul 24, 16:25 UTC | 22h 20m |
| 2026-07-23 | UZB251 | - | Jul 23, 16:05 UTC | Jul 24, 16:00 UTC | 23h 55m |
| 2026-07-23 | UZB342 | - | Jul 23, 15:25 UTC | Jul 24, 14:00 UTC | 22h 35m |
| 2026-07-23 | UZB341 | - | Jul 23, 09:20 UTC | Jul 23, 12:50 UTC | 3h 30m |
| 2026-07-21 | UZB561 | TAS → CXR | Jul 21, 20:35 UTC | Jul 22, 10:25 UTC | 13h 50m |
| 2026-07-21 | UZB561 | TAS → CXR | Jul 21, 05:00 UTC | Jul 22, 01:05 UTC | 20h 5m |
| 2026-07-21 | UZB532 | BKK → TAS | Jul 21, 01:55 UTC | Jul 21, 04:30 UTC | 2h 35m |
| 2026-07-20 | UZB531 | - | Jul 20, 19:35 UTC | Jul 21, 00:05 UTC | 4h 29m |
| 2026-07-18 | UZB561 | TAS → CXR | Jul 18, 21:35 UTC | Jul 19, 10:30 UTC | 12h 55m |
| 2026-07-18 | UZB561 | TAS → CXR | Jul 18, 14:05 UTC | Jul 19, 10:30 UTC | 20h 25m |
| 2026-07-18 | UZB561 | TAS → CXR | Jul 18, 12:55 UTC | Jul 19, 10:30 UTC | 21h 35m |
| 2026-07-17 | UZB341 | - | Jul 17, 19:30 UTC | Jul 18, 10:40 UTC | 15h 11m |
| 2026-07-17 | UZB251 | - | Jul 17, 11:55 UTC | Jul 17, 16:24 UTC | 4h 30m |
| 2026-07-11 | UZB561 | - | Jul 11, 14:25 UTC | Jul 12, 10:01 UTC | 19h 35m |
| 2026-07-11 | UZB561 | - | Jul 11, 12:40 UTC | Jul 12, 10:01 UTC | 21h 20m |
| 2026-07-11 | UZB561 | - | Jul 11, 10:05 UTC | Jul 12, 10:01 UTC | 23h 55m |
| 2026-07-11 | UZB561 | - | Jul 11, 08:05 UTC | Jul 12, 08:01 UTC | 23h 55m |
| 2026-07-11 | UZB561 | - | Jul 11, 06:50 UTC | Jul 12, 06:01 UTC | 23h 10m |
| 2026-07-10 | UZB341 | - | Jul 10, 20:05 UTC | Jul 11, 15:30 UTC | 19h 25m |
| 2026-07-10 | UZB341 | - | Jul 10, 18:25 UTC | Jul 11, 15:30 UTC | 21h 5m |
| 2026-07-10 | UZB251 | TAS → CDG | Jul 10, 13:35 UTC | Jul 10, 16:10 UTC | 2h 35m |
| 2026-07-07 | UZB561 | TAS → CXR | Jul 7, 20:45 UTC | Jul 8, 10:25 UTC | 13h 40m |
| 2026-07-07 | UZB561 | TAS → CXR | Jul 7, 06:05 UTC | Jul 8, 06:00 UTC | 23h 55m |
| 2026-07-07 | UZB561 | TAS → CXR | Jul 7, 04:05 UTC | Jul 8, 01:25 UTC | 21h 20m |
| 2026-07-07 | UZB561 | TAS → CXR | Jul 7, 02:05 UTC | Jul 8, 01:25 UTC | 23h 20m |
| 2026-07-07 | UZB532 | - | Jul 7, 01:55 UTC | Jul 8, 00:00 UTC | 22h 5m |
| 2026-07-06 | UZB531 | - | Jul 6, 13:10 UTC | Jul 6, 23:55 UTC | 10h 45m |
| 2026-07-06 | UZB633 | - | Jul 6, 08:15 UTC | Jul 6, 08:55 UTC | 40m |
| 2026-07-05 | UZB204 | LHR → TAS | Jul 5, 17:30 UTC | Jul 5, 19:55 UTC | 2h 25m |
| 2026-07-05 | UZB203 | TAS → LHR | Jul 5, 13:20 UTC | Jul 5, 15:15 UTC | 1h 55m |
| 2026-07-04 | UZB203 | TAS → LHR | Jul 4, 16:05 UTC | Jul 5, 15:15 UTC | 23h 10m |
| 2026-07-04 | UZB203 | TAS → LHR | Jul 4, 14:05 UTC | Jul 5, 14:00 UTC | 23h 55m |
| 2026-07-04 | UZB3234 | - | Jul 4, 12:50 UTC | Jul 4, 16:05 UTC | 3h 15m |
| 2026-07-03 | UZB256 | - | Jul 3, 19:40 UTC | Jul 4, 10:25 UTC | 14h 45m |
| 2026-07-03 | UZB255 | TAS → MXP | Jul 3, 01:45 UTC | Jul 3, 17:30 UTC | 15h 45m |
| 2026-07-02 | UZB531 | - | Jul 2, 02:05 UTC | Jul 3, 00:00 UTC | 21h 55m |
| 2026-07-02 | UZB531 | - | Jul 2, 00:25 UTC | Jul 3, 00:00 UTC | 23h 35m |
| 2026-07-01 | UZB510 | - | Jul 1, 21:05 UTC | Jul 2, 20:00 UTC | 22h 55m |
| 2026-07-01 | UZB510 | - | Jul 1, 08:05 UTC | Jul 2, 04:35 UTC | 20h 30m |
| 2026-07-01 | UZB510 | - | Jul 1, 06:05 UTC | Jul 2, 04:35 UTC | 22h 30m |
| 2026-07-01 | UZB562 | CXR → TAS | Jul 1, 05:35 UTC | Jul 2, 04:00 UTC | 22h 25m |
| 2026-07-01 | UZB562 | CXR → TAS | Jul 1, 00:15 UTC | Jul 1, 21:15 UTC | 21h 0m |
| 2026-06-30 | UZB562 | CXR → TAS | Jun 30, 22:30 UTC | Jul 1, 21:15 UTC | 22h 45m |
| 2026-06-30 | UZB562 | CXR → TAS | Jun 30, 21:00 UTC | Jul 1, 09:40 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-32103 page for operator, model, and routing details .