sensors Mode-S transponder
507C5A
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32023 · AIRBUS A-320neo
- Hex
- 507C5A
- Octal
- 24076132
- Decimal
- 5,274,714
- Country
- UZ
- Tail
- UK-32023
- Type
- A20N
- Flights observed
- 159
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- Jul 26, 13:10 UTC
Last known position
Country allocation
The ICAO 24-bit address 507C5A 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 |
|---|---|---|---|
| UZB535 | - | 22 | 2026-07-21 |
| UZB281 | - | 14 | 2026-07-04 |
| UZB536 | - | 13 | 2026-07-18 |
| UZB211 | - | 12 | 2026-07-17 |
| UZB282 | - | 11 | 2026-07-05 |
| UZB232 | - | 11 | 2026-07-20 |
| UZB235 | Uzbekistan Airways | 9 | 2026-07-26 |
| UZB231 | - | 7 | 2026-07-13 |
| UZB212 | Uzbekistan Airways | 7 | 2026-07-16 |
| UZB236 | Uzbekistan Airways | 5 | 2026-07-26 |
| UZB634 | Uzbekistan Airways | 4 | 2026-07-23 |
| UZB532 | Uzbekistan Airways | 4 | 2026-05-29 |
| UZB428 | - | 4 | 2026-07-21 |
| UZB3229 | - | 4 | 2026-07-18 |
| UZB645 | Uzbekistan Airways | 3 | 2026-05-13 |
| UZB633 | - | 3 | 2026-06-30 |
| UZB632 | Uzbekistan Airways | 3 | 2026-05-30 |
| UZB3230 | - | 3 | 2026-07-19 |
| UZB631 | Uzbekistan Airways | 2 | 2026-07-22 |
| UZB531 | Uzbekistan Airways | 2 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UZB236 | MUC → TAS | Jul 26, 09:40 UTC | Jul 26, 13:10 UTC | 3h 30m |
| 2026-07-26 | UZB235 | TAS → MUC | Jul 26, 03:25 UTC | Jul 26, 07:20 UTC | 3h 56m |
| 2026-07-23 | UZB634 | LED → TAS | Jul 23, 10:25 UTC | Jul 23, 10:45 UTC | 20m |
| 2026-07-22 | UZB631 | TAS → LED | Jul 22, 18:35 UTC | Jul 22, 18:50 UTC | 15m |
| 2026-07-21 | UZB535 | - | Jul 21, 22:35 UTC | Jul 22, 17:15 UTC | 18h 40m |
| 2026-07-21 | UZB535 | - | Jul 21, 21:45 UTC | Jul 22, 17:15 UTC | 19h 30m |
| 2026-07-21 | UZB535 | - | Jul 21, 00:35 UTC | Jul 22, 00:30 UTC | 23h 55m |
| 2026-07-21 | UZB428 | - | Jul 21, 00:25 UTC | Jul 21, 22:30 UTC | 22h 5m |
| 2026-07-20 | UZB232 | FRA → BOM | Jul 20, 11:05 UTC | Jul 20, 22:55 UTC | 11h 50m |
| 2026-07-19 | UZB3230 | - | Jul 19, 15:10 UTC | Jul 20, 07:50 UTC | 16h 40m |
| 2026-07-18 | UZB3229 | - | Jul 18, 18:35 UTC | Jul 19, 13:25 UTC | 18h 50m |
| 2026-07-18 | UZB536 | - | Jul 18, 05:40 UTC | Jul 18, 18:35 UTC | 12h 55m |
| 2026-07-17 | UZB536 | - | Jul 17, 23:14 UTC | Jul 18, 18:35 UTC | 19h 21m |
| 2026-07-17 | UZB535 | - | Jul 17, 21:25 UTC | Jul 18, 18:35 UTC | 21h 11m |
| 2026-07-17 | UZB535 | - | Jul 17, 12:35 UTC | Jul 18, 08:00 UTC | 19h 26m |
| 2026-07-17 | UZB535 | - | Jul 17, 12:25 UTC | Jul 18, 08:00 UTC | 19h 36m |
| 2026-07-17 | UZB211 | - | Jul 17, 08:40 UTC | Jul 17, 08:49 UTC | 10m |
| 2026-07-16 | UZB212 | RIX → TAS | Jul 16, 12:34 UTC | Jul 17, 06:45 UTC | 18h 10m |
| 2026-07-16 | UZB212 | RIX → TAS | Jul 16, 12:14 UTC | Jul 17, 06:45 UTC | 18h 30m |
| 2026-07-16 | UZB211 | - | Jul 16, 08:30 UTC | Jul 16, 08:50 UTC | 20m |
| 2026-07-16 | UZB211 | - | Jul 16, 06:30 UTC | Jul 16, 06:50 UTC | 20m |
| 2026-07-15 | UZB211 | - | Jul 15, 08:35 UTC | Jul 16, 06:50 UTC | 22h 15m |
| 2026-07-15 | UZB536 | - | Jul 15, 06:35 UTC | Jul 16, 06:30 UTC | 23h 55m |
| 2026-07-14 | UZB535 | - | Jul 14, 21:45 UTC | Jul 15, 08:40 UTC | 10h 54m |
| 2026-07-14 | UZB535 | - | Jul 14, 10:40 UTC | Jul 15, 08:40 UTC | 21h 59m |
| 2026-07-14 | UZB535 | - | Jul 14, 06:35 UTC | Jul 15, 06:30 UTC | 23h 54m |
| 2026-07-13 | UZB232 | - | Jul 13, 13:40 UTC | Jul 14, 10:55 UTC | 21h 15m |
| 2026-07-13 | UZB232 | - | Jul 13, 10:35 UTC | Jul 14, 06:50 UTC | 20h 15m |
| 2026-07-13 | UZB232 | - | Jul 13, 10:10 UTC | Jul 14, 06:50 UTC | 20h 40m |
| 2026-07-13 | UZB231 | - | Jul 13, 03:45 UTC | Jul 13, 07:40 UTC | 3h 55m |
| 2026-07-10 | UZB212 | RIX → TAS | Jul 10, 12:10 UTC | Jul 10, 12:50 UTC | 40m |
| 2026-07-10 | UZB211 | - | Jul 10, 08:25 UTC | Jul 10, 08:40 UTC | 15m |
| 2026-07-09 | UZB212 | RIX → TAS | Jul 9, 12:05 UTC | Jul 9, 12:45 UTC | 40m |
| 2026-07-08 | UZB211 | - | Jul 8, 22:35 UTC | Jul 9, 08:30 UTC | 9h 55m |
| 2026-07-08 | UZB211 | - | Jul 8, 08:35 UTC | Jul 9, 08:30 UTC | 23h 55m |
| 2026-07-08 | UZB536 | - | Jul 8, 05:55 UTC | Jul 8, 22:40 UTC | 16h 45m |
| 2026-07-07 | UZB536 | - | Jul 7, 21:50 UTC | Jul 8, 08:35 UTC | 10h 45m |
| 2026-07-07 | UZB536 | - | Jul 7, 12:35 UTC | Jul 8, 08:35 UTC | 20h 0m |
| 2026-07-06 | UZB232 | - | Jul 6, 14:00 UTC | Jul 7, 12:30 UTC | 22h 30m |
| 2026-07-06 | UZB232 | - | Jul 6, 10:20 UTC | Jul 6, 14:10 UTC | 3h 50m |
| 2026-07-06 | UZB231 | - | Jul 6, 07:00 UTC | Jul 6, 08:05 UTC | 1h 5m |
| 2026-07-05 | UZB282 | - | Jul 5, 03:10 UTC | Jul 5, 05:05 UTC | 1h 55m |
| 2026-07-04 | UZB281 | - | Jul 4, 10:30 UTC | Jul 5, 01:05 UTC | 14h 35m |
| 2026-07-04 | UZB747 | - | Jul 4, 07:55 UTC | Jul 4, 08:55 UTC | 1h 0m |
| 2026-07-02 | UZB212 | RIX → TAS | Jul 2, 12:05 UTC | Jul 2, 12:35 UTC | 30m |
| 2026-07-02 | UZB211 | - | Jul 2, 08:25 UTC | Jul 2, 08:45 UTC | 20m |
| 2026-07-01 | UZB536 | - | Jul 1, 06:25 UTC | Jul 1, 22:35 UTC | 16h 10m |
| 2026-06-30 | UZB535 | - | Jun 30, 21:55 UTC | Jul 1, 08:40 UTC | 10h 45m |
| 2026-06-30 | UZB634 | LED → TAS | Jun 30, 10:35 UTC | Jun 30, 11:25 UTC | 50m |
| 2026-06-30 | UZB633 | - | Jun 30, 08:15 UTC | Jun 30, 08:35 UTC | 20m |
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-32023 page for operator, model, and routing details .