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
- 131
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- Jul 25, 05:25 UTC
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 |
|---|---|---|---|
| UZB279 | Uzbekistan Airways | 16 | 2026-07-21 |
| UZB281 | Uzbekistan Airways | 12 | 2026-07-24 |
| UZB280 | Uzbekistan Airways | 11 | 2026-07-21 |
| UZB282 | Uzbekistan Airways | 9 | 2026-07-25 |
| UZB287 | Uzbekistan Airways | 7 | 2026-06-15 |
| UZB236 | - | 7 | 2026-07-12 |
| UZB645 | Uzbekistan Airways | 5 | 2026-06-02 |
| UZB535 | - | 5 | 2026-07-03 |
| UZB536 | Uzbekistan Airways | 4 | 2026-06-16 |
| UZB288 | Uzbekistan Airways | 4 | 2026-06-04 |
| UZB212 | Uzbekistan Airways | 4 | 2026-06-24 |
| UZB235 | - | 3 | 2026-07-12 |
| UZB211 | - | 3 | 2026-06-24 |
| UZB9684 | - | 2 | 2026-04-18 |
| UZB9652 | Uzbekistan Airways | 2 | 2026-05-08 |
| UZB8673 | - | 2 | 2026-05-27 |
| UZB747 | - | 2 | 2026-07-14 |
| UZB631 | Uzbekistan Airways | 2 | 2026-05-06 |
| UZB603 | Uzbekistan Airways | 2 | 2026-05-13 |
| UZB533 | - | 2 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UZB282 | IST → TAS | Jul 25, 03:25 UTC | Jul 25, 05:25 UTC | 2h 0m |
| 2026-07-24 | UZB281 | TAS → IST | Jul 24, 22:40 UTC | Jul 25, 01:20 UTC | 2h 40m |
| 2026-07-24 | UZB281 | TAS → IST | Jul 24, 02:35 UTC | Jul 25, 01:20 UTC | 22h 45m |
| 2026-07-24 | UZB281 | TAS → IST | Jul 24, 00:40 UTC | Jul 24, 23:45 UTC | 23h 5m |
| 2026-07-23 | UZB427 | - | Jul 23, 20:20 UTC | Jul 23, 23:00 UTC | 2h 40m |
| 2026-07-21 | UZB280 | IST → UGC | Jul 21, 10:50 UTC | Jul 21, 12:45 UTC | 1h 55m |
| 2026-07-21 | UZB279 | UGC → IST | Jul 21, 06:00 UTC | Jul 21, 08:35 UTC | 2h 35m |
| 2026-07-19 | UZB282 | IST → TAS | Jul 19, 03:10 UTC | Jul 19, 05:10 UTC | 2h 0m |
| 2026-07-18 | UZB232 | - | Jul 18, 10:30 UTC | Jul 19, 01:10 UTC | 14h 40m |
| 2026-07-18 | UZB231 | - | Jul 18, 03:45 UTC | Jul 18, 07:55 UTC | 4h 10m |
| 2026-07-16 | UZB334 | - | Jul 16, 08:55 UTC | Jul 16, 11:05 UTC | 2h 10m |
| 2026-07-16 | UZB333 | - | Jul 16, 06:15 UTC | Jul 16, 06:45 UTC | 30m |
| 2026-07-15 | UZB667 | TAS → OVB | Jul 15, 16:40 UTC | Jul 16, 04:25 UTC | 11h 45m |
| 2026-07-14 | UZB747 | - | Jul 14, 11:50 UTC | Jul 15, 08:35 UTC | 20h 44m |
| 2026-07-14 | UZB280 | IST → UGC | Jul 14, 10:25 UTC | Jul 15, 08:35 UTC | 22h 9m |
| 2026-07-14 | UZB279 | - | Jul 14, 05:50 UTC | Jul 14, 08:25 UTC | 2h 35m |
| 2026-07-13 | UZB282 | - | Jul 13, 03:05 UTC | Jul 13, 05:05 UTC | 2h 0m |
| 2026-07-12 | UZB236 | - | Jul 12, 09:25 UTC | Jul 13, 01:01 UTC | 15h 35m |
| 2026-07-12 | UZB235 | - | Jul 12, 05:30 UTC | Jul 12, 07:15 UTC | 1h 45m |
| 2026-07-07 | UZB280 | IST → UGC | Jul 7, 10:40 UTC | Jul 7, 12:40 UTC | 2h 0m |
| 2026-07-07 | UZB279 | - | Jul 7, 05:55 UTC | Jul 7, 08:35 UTC | 2h 40m |
| 2026-07-05 | UZB3230 | - | Jul 5, 16:10 UTC | Jul 5, 18:20 UTC | 2h 10m |
| 2026-07-05 | UZB3229 | - | Jul 5, 11:00 UTC | Jul 5, 13:55 UTC | 2h 55m |
| 2026-07-03 | UZB535 | - | Jul 3, 21:25 UTC | Jul 4, 08:05 UTC | 10h 40m |
| 2026-07-03 | UZB535 | - | Jul 3, 02:30 UTC | Jul 4, 01:45 UTC | 23h 15m |
| 2026-07-03 | UZB535 | - | Jul 3, 00:40 UTC | Jul 3, 23:45 UTC | 23h 5m |
| 2026-07-02 | UZB427 | - | Jul 2, 22:05 UTC | Jul 2, 22:50 UTC | 45m |
| 2026-07-02 | UZB634 | LED → TAS | Jul 2, 10:15 UTC | Jul 2, 11:25 UTC | 1h 10m |
| 2026-07-01 | UZB534 | - | Jul 1, 16:30 UTC | Jul 1, 20:25 UTC | 3h 55m |
| 2026-07-01 | UZB533 | - | Jul 1, 10:25 UTC | Jul 1, 14:40 UTC | 4h 15m |
| 2026-06-30 | UZB533 | - | Jun 30, 11:50 UTC | Jul 1, 11:25 UTC | 23h 35m |
| 2026-06-30 | UZB280 | IST → UGC | Jun 30, 10:30 UTC | Jun 30, 12:25 UTC | 1h 55m |
| 2026-06-30 | UZB279 | - | Jun 30, 06:05 UTC | Jun 30, 08:40 UTC | 2h 35m |
| 2026-06-28 | UZB236 | - | Jun 28, 09:10 UTC | Jun 28, 11:09 UTC | 2h 0m |
| 2026-06-27 | UZB235 | - | Jun 27, 11:50 UTC | Jun 28, 06:55 UTC | 19h 5m |
| 2026-06-27 | UZB232 | FRA → MUC | Jun 27, 10:10 UTC | Jun 28, 06:55 UTC | 20h 45m |
| 2026-06-24 | UZB212 | RIX → TAS | Jun 24, 12:09 UTC | Jun 24, 12:40 UTC | 30m |
| 2026-06-24 | UZB211 | - | Jun 24, 08:45 UTC | Jun 24, 09:09 UTC | 25m |
| 2026-06-23 | UZB686 | AER → TAS | Jun 23, 15:30 UTC | Jun 23, 15:40 UTC | 10m |
| 2026-06-20 | UZB748 | SIP → TAS | Jun 20, 10:25 UTC | Jun 20, 11:05 UTC | 40m |
| 2026-06-20 | UZB747 | - | Jun 20, 07:54 UTC | Jun 20, 08:49 UTC | 55m |
| 2026-06-18 | UZB282 | - | Jun 18, 03:50 UTC | Jun 18, 05:55 UTC | 2h 5m |
| 2026-06-17 | UZB281 | - | Jun 17, 06:20 UTC | Jun 18, 01:50 UTC | 19h 30m |
| 2026-06-16 | UZB536 | HKT → TAS | Jun 16, 21:45 UTC | Jun 17, 08:40 UTC | 10h 55m |
| 2026-06-16 | UZB536 | HKT → TAS | Jun 16, 11:49 UTC | Jun 17, 08:40 UTC | 20h 51m |
| 2026-06-16 | UZB280 | IST → UGC | Jun 16, 10:25 UTC | Jun 17, 08:40 UTC | 22h 16m |
| 2026-06-16 | UZB279 | UGC → IST | Jun 16, 05:55 UTC | Jun 16, 08:39 UTC | 2h 45m |
| 2026-06-15 | UZB279 | UGC → IST | Jun 15, 11:49 UTC | Jun 16, 08:39 UTC | 20h 50m |
| 2026-06-15 | UZB279 | UGC → IST | Jun 15, 11:34 UTC | Jun 16, 08:39 UTC | 21h 5m |
| 2026-06-15 | UZB287 | AZN → IST | Jun 15, 06:55 UTC | Jun 15, 09:25 UTC | 2h 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 .