sensors Mode-S transponder
507C3A
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32011 · AIRBUS A-320
- Hex
- 507C3A
- Octal
- 24076072
- Decimal
- 5,274,682
- Country
- UZ
- Tail
- UK-32011
- Type
- A320
- Flights observed
- 89
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 507C3A 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 |
|---|---|---|---|
| UZB9621 | Uzbekistan Airways | 13 | 2026-05-28 |
| UZB9622 | Uzbekistan Airways | 9 | 2026-05-29 |
| UZB9625 | Uzbekistan Airways | 7 | 2026-06-01 |
| UZB9609 | Uzbekistan Airways | 7 | 2026-05-31 |
| UZB9610 | Uzbekistan Airways | 6 | 2026-05-30 |
| UZB9616 | Uzbekistan Airways | 5 | 2026-05-31 |
| UZB9673 | Uzbekistan Airways | 4 | 2026-04-27 |
| UZB9623 | Uzbekistan Airways | 4 | 2026-05-28 |
| UZB9614 | Uzbekistan Airways | 4 | 2026-06-01 |
| UZB9613 | Uzbekistan Airways | 4 | 2026-05-26 |
| UZB9674 | Uzbekistan Airways | 3 | 2026-05-15 |
| UZB9618 | Uzbekistan Airways | 3 | 2026-05-05 |
| UZB9829 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB9801 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB9626 | Uzbekistan Airways | 2 | 2026-05-01 |
| UZB9617 | Uzbekistan Airways | 2 | 2026-05-26 |
| UZB9830 | Uzbekistan Airways | 1 | 2026-05-18 |
| UZB9826 | Uzbekistan Airways | 1 | 2026-05-23 |
| UZB9825 | Uzbekistan Airways | 1 | 2026-05-23 |
| UZB9821 | Uzbekistan Airways | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | UZB9614 | VKO → TAS | Jun 1, 18:35 UTC | Jun 2, 15:50 UTC | 21h 15m |
| 2026-06-01 | UZB9614 | VKO → TAS | Jun 1, 17:45 UTC | Jun 2, 15:50 UTC | 22h 5m |
| 2026-06-01 | UZB9625 | NCU → VKO | Jun 1, 06:50 UTC | Jun 1, 15:35 UTC | 8h 45m |
| 2026-05-31 | UZB9616 | VKO → UGC | May 31, 19:30 UTC | Jun 1, 04:20 UTC | 8h 50m |
| 2026-05-31 | UZB9609 | TMJ → VKO | May 31, 15:25 UTC | May 31, 16:45 UTC | 1h 20m |
| 2026-05-30 | UZB9609 | TMJ → VKO | May 30, 20:35 UTC | May 31, 16:45 UTC | 20h 10m |
| 2026-05-30 | UZB9616 | VKO → UGC | May 30, 19:40 UTC | May 31, 16:45 UTC | 21h 5m |
| 2026-05-30 | UZB9610 | VKO → TMJ | May 30, 06:40 UTC | May 30, 16:25 UTC | 9h 45m |
| 2026-05-29 | UZB9622 | VKO → AZN | May 29, 18:25 UTC | May 30, 04:25 UTC | 10h 0m |
| 2026-05-29 | UZB9625 | NCU → VKO | May 29, 06:35 UTC | May 29, 16:10 UTC | 9h 35m |
| 2026-05-28 | UZB9623 | KSQ → VKO | May 28, 19:45 UTC | May 29, 04:55 UTC | 9h 10m |
| 2026-05-28 | UZB9621 | AZN → VKO | May 28, 07:00 UTC | May 28, 16:40 UTC | 9h 40m |
| 2026-05-27 | UZB9610 | VKO → TMJ | May 27, 18:55 UTC | May 28, 04:50 UTC | 9h 55m |
| 2026-05-27 | UZB9621 | AZN → VKO | May 27, 06:49 UTC | May 27, 16:40 UTC | 9h 50m |
| 2026-05-26 | UZB9617 | NVI → VKO | May 26, 19:40 UTC | May 27, 04:49 UTC | 9h 10m |
| 2026-05-26 | UZB9621 | AZN → VKO | May 26, 06:39 UTC | May 26, 16:24 UTC | 9h 45m |
| 2026-05-26 | UZB9613 | TAS → VKO | May 26, 03:25 UTC | May 26, 04:50 UTC | 1h 25m |
| 2026-05-23 | UZB9826 | AER → NMA | May 23, 10:50 UTC | May 23, 11:45 UTC | 55m |
| 2026-05-23 | UZB9825 | NMA → AER | May 23, 08:00 UTC | May 23, 08:30 UTC | 30m |
| 2026-05-22 | UZB9432 | DEL → NMA | May 22, 08:35 UTC | May 23, 08:30 UTC | 23h 54m |
| 2026-05-22 | UZB9431 | - | May 22, 05:55 UTC | May 22, 06:40 UTC | 45m |
| 2026-05-20 | UZB9821 | NMA → IKT | May 20, 03:05 UTC | May 20, 10:30 UTC | 7h 26m |
| 2026-05-18 | UZB9830 | SVX → NMA | May 18, 07:15 UTC | May 18, 08:01 UTC | 45m |
| 2026-05-17 | UZB9829 | NMA → SVX | May 17, 10:50 UTC | May 18, 04:55 UTC | 18h 5m |
| 2026-05-17 | UZB9801 | NMA → PEE | May 17, 06:30 UTC | May 17, 07:00 UTC | 30m |
| 2026-05-15 | UZB9674 | IKT → TAS | May 15, 07:20 UTC | May 15, 14:30 UTC | 7h 10m |
| 2026-05-11 | UZB9614 | VKO → TAS | May 11, 17:55 UTC | May 11, 19:10 UTC | 1h 15m |
| 2026-05-11 | UZB9625 | NCU → VKO | May 11, 06:40 UTC | May 11, 15:55 UTC | 9h 15m |
| 2026-05-10 | UZB9616 | VKO → UGC | May 10, 20:35 UTC | May 11, 04:25 UTC | 7h 50m |
| 2026-05-10 | UZB9609 | TMJ → VKO | May 10, 09:20 UTC | May 10, 18:45 UTC | 9h 25m |
| 2026-05-09 | UZB9615 | UGC → VKO | May 9, 23:35 UTC | May 10, 07:34 UTC | 8h 0m |
| 2026-05-09 | UZB9609 | TMJ → VKO | May 9, 12:25 UTC | May 9, 22:15 UTC | 9h 50m |
| 2026-05-09 | UZB9621 | AZN → VKO | May 9, 01:10 UTC | May 9, 10:55 UTC | 9h 45m |
| 2026-05-08 | UZB9625 | NCU → VKO | May 8, 14:55 UTC | May 8, 22:40 UTC | 7h 45m |
| 2026-05-08 | UZB9623 | KSQ → VKO | May 8, 04:00 UTC | May 8, 12:49 UTC | 8h 50m |
| 2026-05-07 | UZB9621 | AZN → VKO | May 7, 16:35 UTC | May 8, 02:04 UTC | 9h 30m |
| 2026-05-06 | UZB9609 | TMJ → VKO | May 6, 19:10 UTC | May 7, 06:00 UTC | 10h 50m |
| 2026-05-06 | UZB9621 | AZN → VKO | May 6, 06:50 UTC | May 6, 16:35 UTC | 9h 45m |
| 2026-05-05 | UZB9618 | VKO → NVI | May 5, 19:40 UTC | May 6, 04:40 UTC | 9h 0m |
| 2026-05-05 | UZB9621 | AZN → VKO | May 5, 06:50 UTC | May 5, 17:50 UTC | 11h 0m |
| 2026-05-05 | UZB9613 | TAS → VKO | May 5, 03:25 UTC | May 5, 04:50 UTC | 1h 25m |
| 2026-05-04 | UZB9613 | TAS → VKO | May 4, 07:15 UTC | May 5, 04:50 UTC | 21h 36m |
| 2026-05-03 | UZB9829 | NMA → SVX | May 3, 10:45 UTC | May 4, 05:05 UTC | 18h 20m |
| 2026-05-03 | UZB9801 | NMA → PEE | May 3, 06:35 UTC | May 3, 07:05 UTC | 30m |
| 2026-05-01 | UZB9626 | VKO → NCU | May 1, 09:40 UTC | May 1, 10:50 UTC | 1h 10m |
| 2026-04-30 | UZB9623 | KSQ → VKO | Apr 30, 20:40 UTC | May 1, 05:40 UTC | 9h 0m |
| 2026-04-30 | UZB9622 | VKO → AZN | Apr 30, 07:15 UTC | Apr 30, 17:20 UTC | 10h 5m |
| 2026-04-29 | UZB9610 | VKO → TMJ | Apr 29, 19:05 UTC | Apr 30, 04:45 UTC | 9h 39m |
| 2026-04-29 | UZB9621 | AZN → VKO | Apr 29, 06:55 UTC | Apr 29, 16:55 UTC | 10h 1m |
| 2026-04-28 | UZB9618 | VKO → NVI | Apr 28, 19:45 UTC | Apr 29, 04:44 UTC | 9h 0m |
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-32011 page for operator, model, and routing details .