sensors Mode-S transponder
507C56
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32021 · AIRBUS A-320neo
- Hex
- 507C56
- Octal
- 24076126
- Decimal
- 5,274,710
- Country
- UZ
- Tail
- UK-32021
- Type
- A20N
- Flights observed
- 73
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 507C56 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 | 11 | 2026-05-26 |
| UZB282 | Uzbekistan Airways | 9 | 2026-05-26 |
| UZB279 | Uzbekistan Airways | 6 | 2026-05-19 |
| UZB236 | Uzbekistan Airways | 5 | 2026-05-10 |
| UZB232 | Uzbekistan Airways | 5 | 2026-05-16 |
| UZB231 | Uzbekistan Airways | 5 | 2026-05-16 |
| UZB536 | Uzbekistan Airways | 3 | 2026-04-18 |
| UZB341 | - | 3 | 2026-04-15 |
| UZB241 | Uzbekistan Airways | 3 | 2026-04-13 |
| UZB235 | Uzbekistan Airways | 3 | 2026-05-02 |
| UZB342 | - | 2 | 2026-04-15 |
| UZB3223 | - | 2 | 2026-05-01 |
| UZB280 | Uzbekistan Airways | 2 | 2026-05-19 |
| UZB258 | Uzbekistan Airways | 2 | 2026-04-19 |
| UZB242 | - | 2 | 2026-04-13 |
| UZB685 | Uzbekistan Airways | 1 | 2026-04-21 |
| UZB631 | Uzbekistan Airways | 1 | 2026-05-13 |
| UZB576 | - | 1 | 2026-05-11 |
| UZB575 | - | 1 | 2026-05-24 |
| UZB535 | - | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | UZB333 | TAS → DXB | May 28, 04:05 UTC | May 28, 11:05 UTC | 7h 0m |
| 2026-05-26 | UZB282 | IST → TAS | May 26, 03:25 UTC | May 27, 00:10 UTC | 20h 45m |
| 2026-05-26 | UZB281 | TAS → IST | May 26, 01:00 UTC | May 26, 01:10 UTC | 10m |
| 2026-05-25 | UZB281 | TAS → IST | May 25, 22:44 UTC | May 26, 00:09 UTC | 1h 25m |
| 2026-05-24 | UZB575 | - | May 24, 23:35 UTC | May 24, 23:46 UTC | 11m |
| 2026-05-22 | UZB282 | IST → TAS | May 22, 03:45 UTC | May 22, 05:55 UTC | 2h 10m |
| 2026-05-22 | UZB281 | TAS → IST | May 22, 01:00 UTC | May 22, 01:10 UTC | 10m |
| 2026-05-21 | UZB281 | TAS → IST | May 21, 22:55 UTC | May 22, 00:10 UTC | 1h 15m |
| 2026-05-20 | UZB282 | IST → TAS | May 20, 03:30 UTC | May 20, 05:30 UTC | 2h 1m |
| 2026-05-20 | UZB281 | TAS → IST | May 20, 01:10 UTC | May 20, 01:20 UTC | 10m |
| 2026-05-19 | UZB280 | IST → UGC | May 19, 10:30 UTC | May 20, 00:20 UTC | 13h 50m |
| 2026-05-19 | UZB279 | UGC → IST | May 19, 08:10 UTC | May 19, 08:20 UTC | 10m |
| 2026-05-18 | UZB279 | UGC → IST | May 18, 16:50 UTC | May 19, 07:05 UTC | 14h 14m |
| 2026-05-16 | UZB232 | FRA → TAS | May 16, 10:16 UTC | May 16, 12:25 UTC | 2h 10m |
| 2026-05-16 | UZB231 | TAS → FRA | May 16, 06:45 UTC | May 16, 07:45 UTC | 1h 0m |
| 2026-05-13 | UZB631 | TAS → LED | May 13, 16:40 UTC | May 14, 10:05 UTC | 17h 25m |
| 2026-05-13 | UZB282 | IST → TAS | May 13, 04:15 UTC | May 13, 22:50 UTC | 18h 35m |
| 2026-05-12 | UZB282 | IST → TAS | May 12, 23:35 UTC | May 13, 22:50 UTC | 23h 15m |
| 2026-05-12 | UZB281 | TAS → IST | May 12, 22:55 UTC | May 13, 17:30 UTC | 18h 35m |
| 2026-05-12 | UZB281 | TAS → IST | May 12, 11:35 UTC | May 13, 05:20 UTC | 17h 45m |
| 2026-05-12 | UZB281 | TAS → IST | May 12, 07:35 UTC | May 13, 05:20 UTC | 21h 45m |
| 2026-05-12 | UZB279 | UGC → IST | May 12, 06:05 UTC | May 13, 05:20 UTC | 23h 15m |
| 2026-05-11 | UZB279 | UGC → IST | May 11, 16:55 UTC | May 12, 12:40 UTC | 19h 46m |
| 2026-05-11 | UZB576 | - | May 11, 02:15 UTC | May 11, 02:30 UTC | 15m |
| 2026-05-10 | UZB236 | MUC → TAS | May 10, 09:30 UTC | May 10, 13:05 UTC | 3h 35m |
| 2026-05-09 | UZB232 | FRA → TAS | May 9, 11:35 UTC | May 10, 07:30 UTC | 19h 55m |
| 2026-05-09 | UZB232 | FRA → TAS | May 9, 11:20 UTC | May 10, 07:30 UTC | 20h 10m |
| 2026-05-08 | UZB231 | TAS → FRA | May 8, 14:10 UTC | May 9, 09:05 UTC | 18h 55m |
| 2026-05-08 | UZB231 | TAS → FRA | May 8, 12:10 UTC | May 9, 09:05 UTC | 20h 55m |
| 2026-05-06 | UZB281 | TAS → IST | May 6, 22:55 UTC | May 7, 00:15 UTC | 1h 20m |
| 2026-05-04 | UZB282 | IST → TAS | May 4, 03:19 UTC | May 4, 20:40 UTC | 17h 21m |
| 2026-05-03 | UZB236 | MUC → TAS | May 3, 09:10 UTC | May 4, 00:05 UTC | 14h 55m |
| 2026-05-02 | UZB235 | TAS → MUC | May 2, 11:35 UTC | May 3, 07:30 UTC | 19h 54m |
| 2026-05-02 | UZB232 | FRA → TAS | May 2, 09:50 UTC | May 3, 07:30 UTC | 21h 39m |
| 2026-05-01 | UZB231 | TAS → FRA | May 1, 12:00 UTC | May 2, 07:30 UTC | 19h 30m |
| 2026-05-01 | UZB3223 | - | May 1, 07:30 UTC | May 1, 10:00 UTC | 2h 30m |
| 2026-04-27 | UZB282 | IST → TAS | Apr 27, 03:10 UTC | Apr 27, 05:20 UTC | 2h 10m |
| 2026-04-26 | UZB236 | MUC → TAS | Apr 26, 09:25 UTC | Apr 27, 00:00 UTC | 14h 35m |
| 2026-04-25 | UZB235 | TAS → MUC | Apr 25, 11:35 UTC | Apr 26, 07:20 UTC | 19h 45m |
| 2026-04-25 | UZB232 | FRA → TAS | Apr 25, 10:05 UTC | Apr 26, 07:20 UTC | 21h 15m |
| 2026-04-25 | UZB231 | TAS → FRA | Apr 25, 06:10 UTC | Apr 25, 07:50 UTC | 1h 40m |
| 2026-04-24 | UZB428 | - | Apr 24, 01:00 UTC | Apr 24, 01:10 UTC | 10m |
| 2026-04-23 | UZB427 | - | Apr 23, 04:20 UTC | Apr 23, 23:00 UTC | 18h 40m |
| 2026-04-22 | UZB3224 | AYT → TAS | Apr 22, 12:10 UTC | Apr 23, 00:15 UTC | 12h 5m |
| 2026-04-21 | UZB3223 | - | Apr 21, 16:15 UTC | Apr 22, 10:15 UTC | 18h 0m |
| 2026-04-21 | UZB685 | TAS → AER | Apr 21, 04:15 UTC | Apr 21, 16:15 UTC | 12h 0m |
| 2026-04-19 | UZB258 | FCO → TAS | Apr 19, 18:30 UTC | Apr 19, 20:30 UTC | 2h 0m |
| 2026-04-19 | UZB257 | - | Apr 19, 12:20 UTC | Apr 19, 16:30 UTC | 4h 10m |
| 2026-04-18 | UZB536 | HKT → TAS | Apr 18, 07:25 UTC | Apr 18, 08:15 UTC | 50m |
| 2026-04-18 | UZB536 | HKT → TAS | Apr 18, 05:45 UTC | Apr 18, 07:20 UTC | 1h 35m |
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-32021 page for operator, model, and routing details .