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