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