sensors Mode-S transponder
507C57
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32022 · AIRBUS A-320neo
- Hex
- 507C57
- Octal
- 24076127
- Decimal
- 5,274,711
- Country
- UZ
- Tail
- UK-32022
- Type
- A20N
- Flights observed
- 57
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 507C57 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 | 6 | 2026-05-14 |
| UZB279 | Uzbekistan Airways | 5 | 2026-05-26 |
| UZB645 | Uzbekistan Airways | 4 | 2026-05-20 |
| UZB282 | Uzbekistan Airways | 4 | 2026-05-15 |
| UZB288 | - | 3 | 2026-04-16 |
| UZB287 | Uzbekistan Airways | 3 | 2026-04-16 |
| UZB280 | Uzbekistan Airways | 3 | 2026-05-26 |
| UZB212 | Uzbekistan Airways | 3 | 2026-05-18 |
| UZB9684 | - | 2 | 2026-04-18 |
| UZB9652 | Uzbekistan Airways | 2 | 2026-05-08 |
| UZB8673 | - | 2 | 2026-05-27 |
| UZB631 | Uzbekistan Airways | 2 | 2026-05-06 |
| UZB603 | Uzbekistan Airways | 2 | 2026-05-13 |
| UZB536 | Uzbekistan Airways | 2 | 2026-05-15 |
| UZB304 | - | 2 | 2026-04-14 |
| UZB303 | - | 2 | 2026-04-14 |
| UZB236 | Uzbekistan Airways | 2 | 2026-05-01 |
| UZB211 | Uzbekistan Airways | 2 | 2026-05-11 |
| UZB204 | Uzbekistan Airways | 2 | 2026-05-24 |
| UZB9683 | - | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | UZB8673 | - | May 27, 04:14 UTC | May 27, 12:25 UTC | 8h 11m |
| 2026-05-26 | UZB8673 | - | May 26, 11:50 UTC | May 27, 11:30 UTC | 23h 40m |
| 2026-05-26 | UZB280 | IST → UGC | May 26, 10:29 UTC | May 27, 05:24 UTC | 18h 55m |
| 2026-05-26 | UZB279 | UGC → IST | May 26, 08:10 UTC | May 26, 08:24 UTC | 15m |
| 2026-05-25 | UZB279 | UGC → IST | May 25, 16:55 UTC | May 26, 07:19 UTC | 14h 25m |
| 2026-05-24 | UZB204 | LHR → TAS | May 24, 19:50 UTC | May 25, 17:30 UTC | 21h 40m |
| 2026-05-24 | UZB204 | LHR → TAS | May 24, 18:30 UTC | May 25, 17:30 UTC | 23h 0m |
| 2026-05-24 | UZB203 | TAS → LHR | May 24, 10:35 UTC | May 24, 11:00 UTC | 25m |
| 2026-05-20 | UZB645 | TAS → MRV | May 20, 16:25 UTC | May 21, 11:15 UTC | 18h 50m |
| 2026-05-20 | UZB645 | TAS → MRV | May 20, 06:00 UTC | May 21, 04:20 UTC | 22h 20m |
| 2026-05-18 | UZB212 | RIX → TAS | May 18, 12:15 UTC | May 18, 12:55 UTC | 40m |
| 2026-05-17 | UZB645 | TAS → MRV | May 17, 17:01 UTC | May 18, 09:25 UTC | 16h 25m |
| 2026-05-15 | UZB536 | HKT → TAS | May 15, 21:50 UTC | May 16, 16:55 UTC | 19h 6m |
| 2026-05-15 | UZB536 | HKT → TAS | May 15, 21:25 UTC | May 16, 16:55 UTC | 19h 31m |
| 2026-05-15 | UZB282 | IST → TAS | May 15, 04:40 UTC | May 15, 22:20 UTC | 17h 39m |
| 2026-05-14 | UZB281 | TAS → IST | May 14, 06:05 UTC | May 15, 00:50 UTC | 18h 45m |
| 2026-05-13 | UZB633 | TAS → LED | May 13, 11:50 UTC | May 14, 06:45 UTC | 18h 55m |
| 2026-05-13 | UZB603 | TAS → DME | May 13, 07:50 UTC | May 14, 06:45 UTC | 22h 55m |
| 2026-05-13 | UZB603 | TAS → DME | May 13, 07:30 UTC | May 13, 11:55 UTC | 4h 25m |
| 2026-05-11 | UZB212 | RIX → TAS | May 11, 12:05 UTC | May 11, 14:15 UTC | 2h 10m |
| 2026-05-11 | UZB211 | TAS → RIX | May 11, 09:00 UTC | May 11, 09:10 UTC | 10m |
| 2026-05-10 | UZB613 | TAS → VKO | May 10, 15:39 UTC | May 11, 06:45 UTC | 15h 5m |
| 2026-05-08 | UZB9652 | KZN → FEG | May 8, 09:59 UTC | May 8, 13:10 UTC | 3h 10m |
| 2026-05-07 | UZB9652 | KZN → FEG | May 7, 14:40 UTC | May 8, 13:10 UTC | 22h 30m |
| 2026-05-06 | UZB631 | TAS → LED | May 6, 16:40 UTC | May 7, 14:45 UTC | 22h 5m |
| 2026-05-06 | UZB282 | IST → TAS | May 6, 03:20 UTC | May 6, 17:15 UTC | 13h 55m |
| 2026-05-05 | UZB281 | TAS → IST | May 5, 11:35 UTC | May 6, 00:10 UTC | 12h 35m |
| 2026-05-04 | UZB279 | UGC → IST | May 4, 12:10 UTC | May 5, 07:25 UTC | 19h 16m |
| 2026-05-04 | UZB211 | TAS → RIX | May 4, 08:45 UTC | May 4, 09:00 UTC | 15m |
| 2026-05-02 | UZB631 | TAS → LED | May 2, 04:35 UTC | May 2, 22:35 UTC | 18h 0m |
| 2026-05-01 | UZB236 | MUC → TAS | May 1, 09:50 UTC | May 2, 04:45 UTC | 18h 55m |
| 2026-05-01 | UZB236 | MUC → TAS | May 1, 08:55 UTC | May 2, 04:45 UTC | 19h 50m |
| 2026-04-30 | UZB282 | IST → TAS | Apr 30, 03:35 UTC | Apr 30, 15:35 UTC | 12h 0m |
| 2026-04-29 | UZB281 | TAS → IST | Apr 29, 22:45 UTC | Apr 30, 00:05 UTC | 1h 19m |
| 2026-04-28 | UZB280 | IST → UGC | Apr 28, 10:35 UTC | Apr 28, 12:40 UTC | 2h 5m |
| 2026-04-28 | UZB279 | UGC → IST | Apr 28, 06:05 UTC | Apr 28, 07:30 UTC | 1h 25m |
| 2026-04-26 | UZB645 | TAS → MRV | Apr 26, 17:15 UTC | Apr 26, 18:00 UTC | 45m |
| 2026-04-23 | UZB281 | TAS → IST | Apr 23, 22:50 UTC | Apr 24, 05:30 UTC | 6h 40m |
| 2026-04-22 | UZB212 | RIX → TAS | Apr 22, 12:10 UTC | Apr 22, 14:25 UTC | 2h 15m |
| 2026-04-21 | UZB280 | IST → UGC | Apr 21, 10:35 UTC | Apr 21, 12:40 UTC | 2h 5m |
| 2026-04-21 | UZB279 | UGC → IST | Apr 21, 05:55 UTC | Apr 21, 07:05 UTC | 1h 10m |
| 2026-04-18 | UZB9684 | - | Apr 18, 07:25 UTC | Apr 18, 08:45 UTC | 1h 20m |
| 2026-04-18 | UZB9683 | - | Apr 18, 04:45 UTC | Apr 18, 04:55 UTC | 10m |
| 2026-04-18 | UZB9684 | - | Apr 18, 04:20 UTC | Apr 18, 08:45 UTC | 4h 25m |
| 2026-04-17 | UZB282 | IST → TAS | Apr 17, 03:25 UTC | Apr 17, 05:15 UTC | 1h 51m |
| 2026-04-16 | UZB281 | TAS → IST | Apr 16, 23:20 UTC | Apr 17, 00:30 UTC | 1h 10m |
| 2026-04-16 | UZB281 | TAS → IST | Apr 16, 22:45 UTC | Apr 16, 23:10 UTC | 25m |
| 2026-04-16 | UZB288 | - | Apr 16, 11:09 UTC | Apr 16, 13:05 UTC | 1h 55m |
| 2026-04-16 | UZB287 | AZN → IST | Apr 16, 07:09 UTC | Apr 16, 08:19 UTC | 1h 10m |
| 2026-04-16 | UZB287 | AZN → IST | Apr 16, 06:34 UTC | Apr 16, 07:05 UTC | 30m |
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-32022 page for operator, model, and routing details .