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
- 124
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 2d 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 | 15 | 2026-06-10 |
| UZB9622 | Uzbekistan Airways | 12 | 2026-06-12 |
| UZB9673 | - | 9 | 2026-07-10 |
| UZB9609 | Uzbekistan Airways | 9 | 2026-06-13 |
| UZB9625 | Uzbekistan Airways | 8 | 2026-06-15 |
| UZB9610 | Uzbekistan Airways | 7 | 2026-06-14 |
| UZB9614 | Uzbekistan Airways | 6 | 2026-06-15 |
| UZB9674 | Uzbekistan Airways | 5 | 2026-07-06 |
| UZB9623 | Uzbekistan Airways | 5 | 2026-06-11 |
| UZB9616 | Uzbekistan Airways | 5 | 2026-05-31 |
| UZB9613 | Uzbekistan Airways | 5 | 2026-06-09 |
| UZB9618 | Uzbekistan Airways | 4 | 2026-06-09 |
| UZB9822 | - | 3 | 2026-07-14 |
| UZB9801 | Uzbekistan Airways | 3 | 2026-06-21 |
| UZB9626 | Uzbekistan Airways | 3 | 2026-06-12 |
| UZB9615 | Uzbekistan Airways | 3 | 2026-06-14 |
| UZB9829 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB9824 | - | 2 | 2026-06-23 |
| UZB9672 | - | 2 | 2026-07-04 |
| UZB9671 | - | 2 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UZB9822 | - | Jul 14, 16:35 UTC | Jul 15, 11:20 UTC | 18h 44m |
| 2026-07-14 | UZB9823 | NMA → KJA | Jul 14, 15:10 UTC | Jul 15, 11:20 UTC | 20h 9m |
| 2026-07-10 | UZB9673 | - | Jul 10, 06:35 UTC | Jul 10, 14:15 UTC | 7h 40m |
| 2026-07-06 | UZB9674 | IKT → TAS | Jul 6, 06:35 UTC | Jul 6, 14:10 UTC | 7h 35m |
| 2026-07-04 | UZB9672 | - | Jul 4, 07:55 UTC | Jul 4, 22:25 UTC | 14h 30m |
| 2026-07-02 | UZB9673 | - | Jul 2, 19:15 UTC | Jul 3, 14:10 UTC | 18h 55m |
| 2026-07-02 | UZB9673 | - | Jul 2, 15:55 UTC | Jul 3, 14:10 UTC | 22h 15m |
| 2026-06-30 | UZB9822 | IKT → NMA | Jun 30, 18:25 UTC | Jul 1, 11:20 UTC | 16h 55m |
| 2026-06-30 | UZB9822 | IKT → NMA | Jun 30, 14:35 UTC | Jul 1, 11:20 UTC | 20h 45m |
| 2026-06-23 | UZB9824 | - | Jun 23, 14:35 UTC | Jun 24, 10:59 UTC | 20h 25m |
| 2026-06-23 | UZB9824 | - | Jun 23, 14:29 UTC | Jun 24, 10:10 UTC | 19h 40m |
| 2026-06-21 | UZB9802 | PEE → NMA | Jun 21, 10:54 UTC | Jun 22, 04:44 UTC | 17h 50m |
| 2026-06-21 | UZB9801 | NMA → PEE | Jun 21, 07:34 UTC | Jun 21, 08:15 UTC | 40m |
| 2026-06-16 | UZB9671 | - | Jun 16, 15:55 UTC | Jun 16, 19:55 UTC | 4h 1m |
| 2026-06-15 | UZB9614 | VKO → TAS | Jun 15, 18:35 UTC | Jun 16, 16:20 UTC | 21h 45m |
| 2026-06-15 | UZB9614 | VKO → TAS | Jun 15, 17:45 UTC | Jun 16, 16:20 UTC | 22h 35m |
| 2026-06-15 | UZB9625 | NCU → VKO | Jun 15, 06:49 UTC | Jun 15, 15:45 UTC | 8h 55m |
| 2026-06-14 | UZB9615 | UGC → VKO | Jun 14, 19:30 UTC | Jun 15, 05:10 UTC | 9h 40m |
| 2026-06-14 | UZB9610 | VKO → TMJ | Jun 14, 06:45 UTC | Jun 14, 17:45 UTC | 11h 0m |
| 2026-06-13 | UZB9615 | UGC → VKO | Jun 13, 19:35 UTC | Jun 14, 04:35 UTC | 9h 0m |
| 2026-06-13 | UZB9609 | TMJ → VKO | Jun 13, 06:45 UTC | Jun 13, 16:45 UTC | 10h 0m |
| 2026-06-12 | UZB9622 | VKO → AZN | Jun 12, 18:20 UTC | Jun 13, 04:30 UTC | 10h 9m |
| 2026-06-12 | UZB9626 | VKO → NCU | Jun 12, 06:40 UTC | Jun 12, 15:40 UTC | 9h 0m |
| 2026-06-11 | UZB9623 | KSQ → VKO | Jun 11, 19:40 UTC | Jun 12, 05:00 UTC | 9h 20m |
| 2026-06-11 | UZB9622 | VKO → AZN | Jun 11, 06:45 UTC | Jun 11, 17:20 UTC | 10h 35m |
| 2026-06-10 | UZB9609 | TMJ → VKO | Jun 10, 19:05 UTC | Jun 11, 04:45 UTC | 9h 40m |
| 2026-06-10 | UZB9621 | AZN → VKO | Jun 10, 07:35 UTC | Jun 10, 17:15 UTC | 9h 40m |
| 2026-06-09 | UZB9618 | VKO → NVI | Jun 9, 20:05 UTC | Jun 10, 05:35 UTC | 9h 30m |
| 2026-06-09 | UZB9621 | AZN → VKO | Jun 9, 16:45 UTC | Jun 9, 17:25 UTC | 40m |
| 2026-06-09 | UZB9622 | VKO → AZN | Jun 9, 07:00 UTC | Jun 9, 15:50 UTC | 8h 50m |
| 2026-06-09 | UZB9613 | TAS → VKO | Jun 9, 03:30 UTC | Jun 9, 04:40 UTC | 1h 10m |
| 2026-06-07 | UZB9675 | - | Jun 7, 16:10 UTC | Jun 7, 19:45 UTC | 3h 35m |
| 2026-06-05 | UZB9674 | IKT → TAS | Jun 5, 06:35 UTC | Jun 5, 14:35 UTC | 8h 0m |
| 2026-06-04 | UZB9673 | TAS → IKT | Jun 4, 15:15 UTC | Jun 5, 14:30 UTC | 23h 15m |
| 2026-06-04 | UZB9673 | TAS → IKT | Jun 4, 11:40 UTC | Jun 5, 07:55 UTC | 20h 15m |
| 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 |
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 .