sensors Mode-S transponder
507C9E
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32040 · AIRBUS A-320
- Hex
- 507C9E
- Octal
- 24076236
- Decimal
- 5,274,782
- Country
- UZ
- Tail
- UK32040
- Type
- A320
- Flights observed
- 77
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 507C9E 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 |
|---|---|---|---|
| UZB685 | Uzbekistan Airways | 7 | 2026-06-11 |
| UZB631 | Uzbekistan Airways | 7 | 2026-05-29 |
| UZB281 | - | 6 | 2026-07-05 |
| UZB634 | - | 5 | 2026-07-05 |
| UZB282 | - | 5 | 2026-07-06 |
| UZB271 | - | 5 | 2026-06-19 |
| UZB748 | Uzbekistan Airways | 4 | 2026-06-24 |
| UZB667 | Uzbekistan Airways | 4 | 2026-06-01 |
| UZB747 | - | 3 | 2026-06-05 |
| UZB633 | - | 3 | 2026-06-29 |
| UZB603 | Uzbekistan Airways | 3 | 2026-06-12 |
| UZB291 | - | 3 | 2026-06-22 |
| UZB9671 | - | 2 | 2026-05-16 |
| UZB668 | Uzbekistan Airways | 2 | 2026-06-01 |
| UZB632 | - | 2 | 2026-07-03 |
| UZB9701 | - | 1 | 2026-05-10 |
| UZB9663 | Uzbekistan Airways | 1 | 2026-05-01 |
| UZB746 | Uzbekistan Airways | 1 | 2026-04-24 |
| UZB745 | Uzbekistan Airways | 1 | 2026-04-24 |
| UZB686 | Uzbekistan Airways | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | UZB334 | - | Jul 11, 09:15 UTC | Jul 11, 11:30 UTC | 2h 15m |
| 2026-07-11 | UZB333 | - | Jul 11, 04:50 UTC | Jul 11, 07:10 UTC | 2h 20m |
| 2026-07-09 | UZB3224 | - | Jul 9, 14:20 UTC | Jul 9, 16:10 UTC | 1h 50m |
| 2026-07-09 | UZB3223 | - | Jul 9, 09:30 UTC | Jul 9, 12:10 UTC | 2h 40m |
| 2026-07-06 | UZB282 | - | Jul 6, 03:10 UTC | Jul 6, 05:05 UTC | 1h 55m |
| 2026-07-05 | UZB281 | - | Jul 5, 22:45 UTC | Jul 6, 01:20 UTC | 2h 35m |
| 2026-07-05 | UZB634 | - | Jul 5, 10:25 UTC | Jul 5, 10:40 UTC | 15m |
| 2026-07-03 | UZB632 | - | Jul 3, 21:25 UTC | Jul 3, 21:45 UTC | 20m |
| 2026-07-02 | UZB282 | - | Jul 2, 03:20 UTC | Jul 2, 05:15 UTC | 1h 55m |
| 2026-07-01 | UZB281 | - | Jul 1, 22:55 UTC | Jul 2, 01:30 UTC | 2h 35m |
| 2026-06-29 | UZB633 | - | Jun 29, 06:19 UTC | Jun 29, 06:34 UTC | 15m |
| 2026-06-27 | UZB282 | - | Jun 27, 03:20 UTC | Jun 27, 05:19 UTC | 2h 0m |
| 2026-06-26 | UZB236 | - | Jun 26, 09:05 UTC | Jun 27, 01:19 UTC | 16h 15m |
| 2026-06-26 | UZB235 | - | Jun 26, 04:10 UTC | Jun 26, 07:24 UTC | 3h 15m |
| 2026-06-24 | UZB748 | SIP → TAS | Jun 24, 10:49 UTC | Jun 24, 20:44 UTC | 9h 55m |
| 2026-06-24 | UZB748 | SIP → TAS | Jun 24, 07:50 UTC | Jun 24, 08:45 UTC | 55m |
| 2026-06-22 | UZB291 | - | Jun 22, 04:59 UTC | Jun 22, 10:44 UTC | 5h 45m |
| 2026-06-21 | UZB282 | - | Jun 21, 03:25 UTC | Jun 21, 05:20 UTC | 1h 55m |
| 2026-06-21 | UZB281 | - | Jun 21, 01:05 UTC | Jun 21, 01:35 UTC | 30m |
| 2026-06-20 | UZB281 | - | Jun 20, 22:50 UTC | Jun 21, 00:25 UTC | 1h 35m |
| 2026-06-19 | UZB272 | - | Jun 19, 09:55 UTC | Jun 19, 11:49 UTC | 1h 55m |
| 2026-06-19 | UZB271 | - | Jun 19, 05:14 UTC | Jun 19, 07:54 UTC | 2h 40m |
| 2026-06-18 | UZB271 | - | Jun 18, 11:35 UTC | Jun 19, 07:54 UTC | 20h 19m |
| 2026-06-18 | UZB271 | - | Jun 18, 09:55 UTC | Jun 19, 07:54 UTC | 21h 59m |
| 2026-06-18 | UZB271 | - | Jun 18, 05:20 UTC | Jun 18, 07:45 UTC | 2h 25m |
| 2026-06-17 | UZB271 | - | Jun 17, 07:35 UTC | Jun 18, 07:30 UTC | 23h 55m |
| 2026-06-17 | UZB282 | - | Jun 17, 05:45 UTC | Jun 18, 05:30 UTC | 23h 45m |
| 2026-06-17 | UZB281 | - | Jun 17, 03:30 UTC | Jun 17, 03:45 UTC | 15m |
| 2026-06-17 | UZB281 | - | Jun 17, 01:25 UTC | Jun 17, 02:50 UTC | 1h 25m |
| 2026-06-15 | UZB634 | LED → TAS | Jun 15, 10:20 UTC | Jun 15, 12:35 UTC | 2h 15m |
| 2026-06-15 | UZB633 | TAS → LED | Jun 15, 06:40 UTC | Jun 15, 07:00 UTC | 20m |
| 2026-06-12 | UZB604 | DME → TAS | Jun 12, 09:35 UTC | Jun 12, 22:45 UTC | 13h 10m |
| 2026-06-12 | UZB603 | TAS → DME | Jun 12, 07:10 UTC | Jun 12, 07:40 UTC | 30m |
| 2026-06-11 | UZB649 | TAS → KZN | Jun 11, 19:45 UTC | Jun 12, 06:20 UTC | 10h 35m |
| 2026-06-11 | UZB685 | TAS → AER | Jun 11, 09:45 UTC | Jun 11, 10:25 UTC | 40m |
| 2026-06-11 | UZB685 | TAS → AER | Jun 11, 07:20 UTC | Jun 11, 07:35 UTC | 15m |
| 2026-06-11 | UZB685 | TAS → AER | Jun 11, 05:15 UTC | Jun 11, 06:15 UTC | 1h 0m |
| 2026-06-09 | UZB685 | TAS → AER | Jun 9, 05:40 UTC | Jun 9, 19:50 UTC | 14h 10m |
| 2026-06-08 | UZB685 | TAS → AER | Jun 8, 16:45 UTC | Jun 9, 06:25 UTC | 13h 40m |
| 2026-06-06 | UZB748 | SIP → TAS | Jun 6, 11:30 UTC | Jun 6, 12:20 UTC | 50m |
| 2026-06-05 | UZB747 | - | Jun 5, 17:15 UTC | Jun 6, 10:00 UTC | 16h 45m |
| 2026-06-05 | UZB747 | - | Jun 5, 10:20 UTC | Jun 6, 09:30 UTC | 23h 10m |
| 2026-06-05 | UZB603 | TAS → DME | Jun 5, 07:10 UTC | Jun 5, 07:25 UTC | 15m |
| 2026-06-05 | UZB603 | TAS → DME | Jun 5, 06:00 UTC | Jun 5, 06:30 UTC | 30m |
| 2026-06-03 | UZB748 | SIP → TAS | Jun 3, 10:30 UTC | Jun 3, 20:55 UTC | 10h 25m |
| 2026-06-02 | UZB747 | - | Jun 2, 15:40 UTC | Jun 3, 08:50 UTC | 17h 10m |
| 2026-06-01 | UZB668 | OVB → TAS | Jun 1, 19:50 UTC | Jun 2, 18:40 UTC | 22h 50m |
| 2026-06-01 | UZB667 | TAS → OVB | Jun 1, 16:50 UTC | Jun 1, 17:25 UTC | 35m |
| 2026-05-29 | UZB631 | TAS → LED | May 29, 17:20 UTC | May 29, 18:00 UTC | 40m |
| 2026-05-28 | UZB631 | TAS → LED | May 28, 19:55 UTC | May 29, 18:00 UTC | 22h 5m |
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 UK32040 page for operator, model, and routing details .