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
- 65
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 17h ago
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 |
|---|---|---|---|
| UZB281 | Uzbekistan Airways | 10 | 2026-06-02 |
| UZB282 | Uzbekistan Airways | 8 | 2026-06-02 |
| UZB535 | - | 7 | 2026-05-29 |
| UZB532 | Uzbekistan Airways | 4 | 2026-05-29 |
| UZB232 | Uzbekistan Airways | 4 | 2026-06-01 |
| UZB231 | Uzbekistan Airways | 4 | 2026-05-31 |
| UZB645 | Uzbekistan Airways | 3 | 2026-05-13 |
| UZB632 | Uzbekistan Airways | 3 | 2026-05-30 |
| UZB235 | Uzbekistan Airways | 3 | 2026-04-24 |
| UZB536 | Uzbekistan Airways | 2 | 2026-05-22 |
| UZB531 | Uzbekistan Airways | 2 | 2026-05-28 |
| UZB428 | - | 2 | 2026-05-26 |
| UZB427 | - | 2 | 2026-05-25 |
| UZB423 | Uzbekistan Airways | 2 | 2026-04-23 |
| UZB236 | Uzbekistan Airways | 2 | 2026-04-24 |
| UZB633 | Uzbekistan Airways | 1 | 2026-05-07 |
| UZB604 | Uzbekistan Airways | 1 | 2026-05-06 |
| UZB424 | Uzbekistan Airways | 1 | 2026-04-16 |
| UZB212 | Uzbekistan Airways | 1 | 2026-05-15 |
| UZB211 | Uzbekistan Airways | 1 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | UZB282 | IST → TAS | Jun 2, 03:10 UTC | Jun 2, 05:05 UTC | 1h 55m |
| 2026-06-02 | UZB281 | TAS → IST | Jun 2, 01:05 UTC | Jun 2, 01:20 UTC | 15m |
| 2026-06-01 | UZB232 | FRA → TAS | Jun 1, 10:05 UTC | Jun 2, 00:10 UTC | 14h 5m |
| 2026-05-31 | UZB231 | TAS → FRA | May 31, 20:00 UTC | Jun 1, 07:15 UTC | 11h 15m |
| 2026-05-30 | UZB632 | LED → TAS | May 30, 22:00 UTC | May 31, 20:10 UTC | 22h 10m |
| 2026-05-30 | UZB632 | LED → TAS | May 30, 20:30 UTC | May 30, 20:45 UTC | 15m |
| 2026-05-29 | UZB535 | - | May 29, 21:05 UTC | May 30, 08:15 UTC | 11h 10m |
| 2026-05-29 | UZB535 | - | May 29, 04:35 UTC | May 29, 22:45 UTC | 18h 10m |
| 2026-05-29 | UZB532 | BKK → TAS | May 29, 03:05 UTC | May 29, 22:45 UTC | 19h 40m |
| 2026-05-29 | UZB532 | BKK → TAS | May 29, 01:20 UTC | May 29, 22:45 UTC | 21h 25m |
| 2026-05-28 | UZB531 | TAS → BKK | May 28, 10:00 UTC | May 28, 23:30 UTC | 13h 30m |
| 2026-05-26 | UZB428 | - | May 26, 00:39 UTC | May 26, 12:40 UTC | 12h 0m |
| 2026-05-25 | UZB427 | - | May 25, 06:25 UTC | May 25, 22:44 UTC | 16h 20m |
| 2026-05-22 | UZB536 | HKT → TAS | May 22, 21:25 UTC | May 23, 08:00 UTC | 10h 34m |
| 2026-05-22 | UZB532 | BKK → TAS | May 22, 02:35 UTC | May 22, 22:15 UTC | 19h 40m |
| 2026-05-22 | UZB532 | BKK → TAS | May 22, 01:30 UTC | May 22, 22:15 UTC | 20h 45m |
| 2026-05-21 | UZB531 | TAS → BKK | May 21, 19:45 UTC | May 21, 23:50 UTC | 4h 5m |
| 2026-05-20 | UZB536 | HKT → TAS | May 20, 05:55 UTC | May 20, 13:15 UTC | 7h 20m |
| 2026-05-19 | UZB535 | - | May 19, 12:45 UTC | May 20, 04:10 UTC | 15h 25m |
| 2026-05-19 | UZB535 | - | May 19, 02:45 UTC | May 19, 23:00 UTC | 20h 15m |
| 2026-05-19 | UZB535 | - | May 19, 00:50 UTC | May 19, 23:00 UTC | 22h 10m |
| 2026-05-18 | UZB232 | FRA → TAS | May 18, 10:15 UTC | May 18, 23:05 UTC | 12h 49m |
| 2026-05-17 | UZB231 | TAS → FRA | May 17, 20:05 UTC | May 18, 07:30 UTC | 11h 25m |
| 2026-05-15 | UZB212 | RIX → TAS | May 15, 12:15 UTC | May 15, 15:00 UTC | 2h 44m |
| 2026-05-15 | UZB211 | TAS → RIX | May 15, 08:25 UTC | May 15, 08:40 UTC | 15m |
| 2026-05-13 | UZB645 | TAS → MRV | May 13, 16:10 UTC | May 13, 20:50 UTC | 4h 40m |
| 2026-05-11 | UZB232 | FRA → TAS | May 11, 10:15 UTC | May 11, 22:05 UTC | 11h 51m |
| 2026-05-10 | UZB231 | TAS → FRA | May 10, 17:20 UTC | May 11, 07:50 UTC | 14h 30m |
| 2026-05-09 | UZB645 | TAS → MRV | May 9, 22:34 UTC | May 10, 18:05 UTC | 19h 30m |
| 2026-05-09 | UZB645 | TAS → MRV | May 9, 22:25 UTC | May 10, 18:05 UTC | 19h 40m |
| 2026-05-07 | UZB282 | IST → TAS | May 7, 22:45 UTC | May 8, 05:35 UTC | 6h 50m |
| 2026-05-07 | UZB633 | TAS → LED | May 7, 08:40 UTC | May 7, 08:50 UTC | 10m |
| 2026-05-06 | UZB604 | DME → TAS | May 6, 10:10 UTC | May 6, 10:20 UTC | 10m |
| 2026-05-05 | UZB428 | - | May 5, 00:25 UTC | May 5, 00:35 UTC | 10m |
| 2026-05-04 | UZB427 | - | May 4, 22:00 UTC | May 4, 22:35 UTC | 35m |
| 2026-05-04 | UZB232 | FRA → TAS | May 4, 10:05 UTC | May 4, 20:20 UTC | 10h 16m |
| 2026-05-03 | UZB231 | TAS → FRA | May 3, 20:10 UTC | May 4, 07:55 UTC | 11h 45m |
| 2026-05-01 | UZB282 | IST → TAS | May 1, 03:35 UTC | May 1, 22:30 UTC | 18h 55m |
| 2026-04-30 | UZB281 | TAS → IST | Apr 30, 22:45 UTC | May 1, 00:10 UTC | 1h 25m |
| 2026-04-29 | UZB282 | IST → TAS | Apr 29, 03:30 UTC | Apr 29, 16:45 UTC | 13h 16m |
| 2026-04-28 | UZB281 | TAS → IST | Apr 28, 04:35 UTC | Apr 29, 00:20 UTC | 19h 45m |
| 2026-04-28 | UZB282 | IST → TAS | Apr 28, 03:10 UTC | Apr 29, 00:20 UTC | 21h 10m |
| 2026-04-27 | UZB281 | TAS → IST | Apr 27, 22:55 UTC | Apr 28, 00:05 UTC | 1h 10m |
| 2026-04-26 | UZB204 | LHR → TAS | Apr 26, 17:25 UTC | Apr 26, 20:35 UTC | 3h 10m |
| 2026-04-26 | UZB203 | TAS → LHR | Apr 26, 11:35 UTC | Apr 26, 15:25 UTC | 3h 50m |
| 2026-04-24 | UZB535 | - | Apr 24, 12:35 UTC | Apr 25, 08:15 UTC | 19h 40m |
| 2026-04-24 | UZB535 | - | Apr 24, 10:35 UTC | Apr 25, 08:15 UTC | 21h 40m |
| 2026-04-24 | UZB236 | MUC → TAS | Apr 24, 09:05 UTC | Apr 25, 08:15 UTC | 23h 10m |
| 2026-04-24 | UZB235 | TAS → MUC | Apr 24, 04:30 UTC | Apr 24, 06:45 UTC | 2h 15m |
| 2026-04-23 | UZB235 | TAS → MUC | Apr 23, 09:01 UTC | Apr 24, 06:45 UTC | 21h 44m |
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 .