sensors Mode-S transponder
507C9D
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32029 · AIRBUS A-320neo
- Hex
- 507C9D
- Octal
- 24076235
- Decimal
- 5,274,781
- Country
- UZ
- Tail
- UK32029
- Type
- A20N
- Flights observed
- 23
- Distinct callsigns
- 9
- Country
- UZ
- Last broadcast
- 15d ago
Last known position
Country allocation
The ICAO 24-bit address 507C9D 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 9 distinct
Recent flights last 23
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UZB601 | TAS → DME | Jul 25, 17:10 UTC | Jul 25, 17:35 UTC | 25m |
| 2026-07-19 | UZB634 | LED → TAS | Jul 19, 10:30 UTC | Jul 19, 10:55 UTC | 25m |
| 2026-07-15 | UZB601 | TAS → DME | Jul 15, 17:10 UTC | Jul 15, 17:30 UTC | 20m |
| 2026-07-13 | UZB291 | - | Jul 13, 04:45 UTC | Jul 13, 20:45 UTC | 16h 0m |
| 2026-07-12 | UZB282 | - | Jul 12, 03:15 UTC | Jul 12, 05:10 UTC | 1h 55m |
| 2026-07-11 | UZB281 | - | Jul 11, 22:40 UTC | Jul 12, 01:15 UTC | 2h 35m |
| 2026-07-09 | UZB282 | - | Jul 9, 03:15 UTC | Jul 9, 05:15 UTC | 2h 0m |
| 2026-07-08 | UZB281 | - | Jul 8, 05:20 UTC | Jul 9, 01:10 UTC | 19h 50m |
| 2026-07-08 | UZB281 | - | Jul 8, 02:50 UTC | Jul 8, 03:10 UTC | 20m |
| 2026-07-08 | UZB281 | - | Jul 8, 00:35 UTC | Jul 8, 01:20 UTC | 45m |
| 2026-07-06 | UZB291 | - | Jul 6, 04:40 UTC | Jul 6, 20:55 UTC | 16h 15m |
| 2026-07-04 | UZB9684 | - | Jul 4, 03:25 UTC | Jul 4, 09:00 UTC | 5h 35m |
| 2026-07-03 | UZB282 | - | Jul 3, 03:20 UTC | Jul 3, 05:15 UTC | 1h 55m |
| 2026-07-03 | UZB281 | - | Jul 3, 00:50 UTC | Jul 3, 01:10 UTC | 20m |
| 2026-07-02 | UZB281 | - | Jul 2, 22:40 UTC | Jul 2, 23:55 UTC | 1h 15m |
| 2026-06-29 | UZB668 | - | Jun 29, 20:24 UTC | Jun 29, 21:30 UTC | 1h 5m |
| 2026-06-29 | UZB291 | - | Jun 29, 04:50 UTC | Jun 29, 10:10 UTC | 5h 20m |
| 2026-06-26 | UZB3222 | - | Jun 26, 14:19 UTC | Jun 26, 16:05 UTC | 1h 45m |
| 2026-06-26 | UZB3221 | - | Jun 26, 09:59 UTC | Jun 26, 12:34 UTC | 2h 35m |
| 2026-06-21 | UZB634 | LED → TAS | Jun 21, 10:14 UTC | Jun 21, 10:40 UTC | 25m |
| 2026-06-19 | UZB3222 | - | Jun 19, 14:09 UTC | Jun 19, 15:59 UTC | 1h 50m |
| 2026-06-19 | UZB3221 | - | Jun 19, 09:24 UTC | Jun 19, 12:14 UTC | 2h 50m |
| 2026-06-18 | UZB291 | - | Jun 18, 04:55 UTC | Jun 18, 10:20 UTC | 5h 25m |
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 UK32029 page for operator, model, and routing details .