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