sensors Mode-S transponder
507C8B
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32028 · AIRBUS A-320neo
- Hex
- 507C8B
- Octal
- 24076213
- Decimal
- 5,274,763
- Country
- UZ
- Tail
- UK32028
- Type
- A20N
- Flights observed
- 77
- Distinct callsigns
- 16
- Country
- UZ
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 507C8B 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB9669 | - | 22 | 2026-07-09 |
| UZB9670 | Uzbekistan Airways | 9 | 2026-06-25 |
| UZB9831 | Uzbekistan Airways | 7 | 2026-06-28 |
| UZB9832 | Uzbekistan Airways | 6 | 2026-06-28 |
| UZB9683 | - | 6 | 2026-05-30 |
| UZB9664 | Uzbekistan Airways | 6 | 2026-05-28 |
| UZB9684 | - | 5 | 2026-05-16 |
| UZB9607 | - | 4 | 2026-07-14 |
| UZB9675 | - | 3 | 2026-05-31 |
| UZB9698 | - | 2 | 2026-06-01 |
| UZB9676 | - | 2 | 2026-05-24 |
| UZB9813 | - | 1 | 2026-07-13 |
| UZB9663 | Uzbekistan Airways | 1 | 2026-06-05 |
| UZB9662 | - | 1 | 2026-05-09 |
| UZB9652 | Uzbekistan Airways | 1 | 2026-05-22 |
| UZB9627 | Uzbekistan Airways | 1 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | UZB9627 | FEG → VKO | Jul 17, 15:40 UTC | Jul 17, 16:15 UTC | 35m |
| 2026-07-14 | UZB9607 | - | Jul 14, 04:00 UTC | Jul 14, 04:15 UTC | 15m |
| 2026-07-13 | UZB9813 | - | Jul 13, 03:05 UTC | Jul 13, 03:20 UTC | 15m |
| 2026-07-09 | UZB9669 | - | Jul 9, 11:35 UTC | Jul 9, 15:45 UTC | 4h 10m |
| 2026-07-08 | UZB9669 | - | Jul 8, 15:50 UTC | Jul 9, 12:05 UTC | 20h 15m |
| 2026-07-07 | UZB9669 | - | Jul 7, 11:30 UTC | Jul 7, 15:30 UTC | 4h 0m |
| 2026-07-05 | UZB9607 | - | Jul 5, 02:50 UTC | Jul 5, 07:30 UTC | 4h 40m |
| 2026-07-03 | UZB9607 | - | Jul 3, 02:55 UTC | Jul 3, 04:10 UTC | 1h 15m |
| 2026-07-02 | UZB9607 | - | Jul 2, 07:35 UTC | Jul 3, 04:10 UTC | 20h 35m |
| 2026-06-28 | UZB9832 | OVB → AZN | Jun 28, 14:30 UTC | Jun 28, 15:29 UTC | 1h 0m |
| 2026-06-28 | UZB9831 | AZN → OVB | Jun 28, 11:29 UTC | Jun 28, 11:55 UTC | 25m |
| 2026-06-25 | UZB9670 | OVB → FEG | Jun 25, 14:59 UTC | Jun 25, 15:24 UTC | 25m |
| 2026-06-23 | UZB9669 | - | Jun 23, 11:40 UTC | Jun 23, 15:34 UTC | 3h 55m |
| 2026-06-21 | UZB9831 | AZN → OVB | Jun 21, 11:24 UTC | Jun 21, 15:25 UTC | 4h 0m |
| 2026-06-18 | UZB9669 | - | Jun 18, 11:30 UTC | Jun 18, 15:40 UTC | 4h 10m |
| 2026-06-17 | UZB9669 | - | Jun 17, 15:55 UTC | Jun 18, 12:00 UTC | 20h 5m |
| 2026-06-14 | UZB9832 | OVB → AZN | Jun 14, 15:10 UTC | Jun 15, 11:45 UTC | 20h 34m |
| 2026-06-14 | UZB9831 | AZN → OVB | Jun 14, 11:30 UTC | Jun 14, 15:35 UTC | 4h 5m |
| 2026-06-11 | UZB9670 | OVB → FEG | Jun 11, 11:20 UTC | Jun 11, 16:05 UTC | 4h 45m |
| 2026-06-09 | UZB9669 | FEG → OVB | Jun 9, 11:40 UTC | Jun 9, 15:35 UTC | 3h 55m |
| 2026-06-07 | UZB9832 | OVB → AZN | Jun 7, 15:10 UTC | Jun 8, 13:50 UTC | 22h 40m |
| 2026-06-07 | UZB9831 | AZN → OVB | Jun 7, 11:20 UTC | Jun 7, 15:35 UTC | 4h 15m |
| 2026-06-06 | UZB9831 | AZN → OVB | Jun 6, 16:34 UTC | Jun 7, 11:50 UTC | 19h 15m |
| 2026-06-05 | UZB9663 | BHK → OVB | Jun 5, 05:10 UTC | Jun 5, 09:00 UTC | 3h 50m |
| 2026-06-02 | UZB9670 | OVB → FEG | Jun 2, 14:40 UTC | Jun 2, 15:45 UTC | 1h 5m |
| 2026-06-02 | UZB9669 | FEG → OVB | Jun 2, 11:35 UTC | Jun 2, 12:05 UTC | 30m |
| 2026-06-01 | UZB9698 | - | Jun 1, 13:20 UTC | Jun 1, 13:35 UTC | 15m |
| 2026-05-31 | UZB9675 | - | May 31, 16:05 UTC | Jun 1, 10:35 UTC | 18h 30m |
| 2026-05-30 | UZB9675 | - | May 30, 17:40 UTC | May 31, 16:35 UTC | 22h 55m |
| 2026-05-30 | UZB9683 | - | May 30, 03:30 UTC | May 30, 17:45 UTC | 14h 15m |
| 2026-05-29 | UZB9683 | - | May 29, 08:50 UTC | May 30, 08:45 UTC | 23h 55m |
| 2026-05-29 | UZB9683 | - | May 29, 08:05 UTC | May 30, 04:55 UTC | 20h 50m |
| 2026-05-29 | UZB9683 | - | May 29, 05:00 UTC | May 30, 04:45 UTC | 23h 45m |
| 2026-05-28 | UZB9664 | OVB → BHK | May 28, 15:00 UTC | May 29, 09:00 UTC | 18h 0m |
| 2026-05-28 | UZB9664 | OVB → BHK | May 28, 11:25 UTC | May 29, 09:00 UTC | 21h 35m |
| 2026-05-26 | UZB9670 | OVB → FEG | May 26, 15:09 UTC | May 27, 10:30 UTC | 19h 21m |
| 2026-05-26 | UZB9669 | FEG → OVB | May 26, 11:34 UTC | May 27, 10:30 UTC | 22h 56m |
| 2026-05-25 | UZB9669 | FEG → OVB | May 25, 13:35 UTC | May 26, 12:05 UTC | 22h 30m |
| 2026-05-24 | UZB9676 | - | May 24, 19:40 UTC | May 25, 13:45 UTC | 18h 5m |
| 2026-05-24 | UZB9676 | - | May 24, 16:20 UTC | May 25, 13:45 UTC | 21h 25m |
| 2026-05-23 | UZB9683 | - | May 23, 03:40 UTC | May 23, 08:55 UTC | 5h 15m |
| 2026-05-22 | UZB9652 | KZN → FEG | May 22, 13:00 UTC | May 22, 13:10 UTC | 10m |
| 2026-05-21 | UZB9669 | FEG → OVB | May 21, 11:20 UTC | May 21, 11:50 UTC | 30m |
| 2026-05-19 | UZB9669 | FEG → OVB | May 19, 12:15 UTC | May 19, 15:55 UTC | 3h 40m |
| 2026-05-18 | UZB9669 | FEG → OVB | May 18, 13:30 UTC | May 19, 12:45 UTC | 23h 14m |
| 2026-05-17 | UZB9675 | - | May 17, 05:55 UTC | May 17, 16:40 UTC | 10h 45m |
| 2026-05-16 | UZB9684 | - | May 16, 08:51 UTC | May 17, 05:55 UTC | 21h 5m |
| 2026-05-16 | UZB9684 | - | May 16, 07:41 UTC | May 17, 05:55 UTC | 22h 15m |
| 2026-05-16 | UZB9684 | - | May 16, 04:35 UTC | May 16, 09:01 UTC | 4h 26m |
| 2026-05-15 | UZB9684 | - | May 15, 08:50 UTC | May 16, 08:46 UTC | 23h 55m |
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 UK32028 page for operator, model, and routing details .