sensors Mode-S transponder
507C40
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32017 · AIRBUS A-320
- Hex
- 507C40
- Octal
- 24076100
- Decimal
- 5,274,688
- Country
- UZ
- Tail
- UK32017
- Type
- A320
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 507C40 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 |
|---|---|---|---|
| UZB281 | Uzbekistan Airways | 4 | 2026-05-27 |
| UZB276 | Uzbekistan Airways | 4 | 2026-05-01 |
| UZB291 | Uzbekistan Airways | 3 | 2026-04-23 |
| UZB275 | Uzbekistan Airways | 3 | 2026-05-01 |
| UZB746 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB745 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB667 | - | 2 | 2026-04-20 |
| UZB282 | Uzbekistan Airways | 2 | 2026-05-28 |
| UZB9701 | - | 1 | 2026-04-25 |
| UZB747 | - | 1 | 2026-05-26 |
| UZB710 | Uzbekistan Airways | 1 | 2026-05-07 |
| UZB709 | Uzbekistan Airways | 1 | 2026-05-07 |
| UZB685 | Uzbekistan Airways | 1 | 2026-04-25 |
| UZB668 | Uzbekistan Airways | 1 | 2026-04-15 |
| UZB639 | Uzbekistan Airways | 1 | 2026-04-28 |
| UZB605 | Uzbekistan Airways | 1 | 2026-05-01 |
| UZB303 | Uzbekistan Airways | 1 | 2026-05-26 |
| UZB292 | Uzbekistan Airways | 1 | 2026-04-18 |
| UZB280 | Uzbekistan Airways | 1 | 2026-05-29 |
| UZB279 | Uzbekistan Airways | 1 | 2026-05-29 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB280 | IST → UGC | May 29, 10:20 UTC | May 29, 12:20 UTC | 2h 0m |
| 2026-05-29 | UZB279 | UGC → IST | May 29, 06:05 UTC | May 29, 08:40 UTC | 2h 35m |
| 2026-05-28 | UZB282 | IST → TAS | May 28, 03:05 UTC | May 28, 05:10 UTC | 2h 5m |
| 2026-05-27 | UZB281 | TAS → IST | May 27, 22:55 UTC | May 28, 01:25 UTC | 2h 30m |
| 2026-05-26 | UZB747 | - | May 26, 19:15 UTC | May 27, 09:15 UTC | 14h 0m |
| 2026-05-26 | UZB303 | TAS → TLV | May 26, 13:15 UTC | May 26, 16:00 UTC | 2h 45m |
| 2026-05-21 | UZB282 | IST → TAS | May 21, 03:25 UTC | May 21, 05:40 UTC | 2h 15m |
| 2026-05-21 | UZB281 | TAS → IST | May 21, 01:00 UTC | May 21, 01:10 UTC | 10m |
| 2026-05-20 | UZB281 | TAS → IST | May 20, 07:25 UTC | May 21, 00:10 UTC | 16h 45m |
| 2026-05-17 | UZB746 | TBS → TAS | May 17, 08:10 UTC | May 17, 08:40 UTC | 30m |
| 2026-05-17 | UZB745 | TAS → TBS | May 17, 05:50 UTC | May 17, 06:15 UTC | 25m |
| 2026-05-07 | UZB710 | MSQ → TAS | May 7, 11:10 UTC | May 7, 13:15 UTC | 2h 5m |
| 2026-05-07 | UZB709 | TAS → MSQ | May 7, 08:55 UTC | May 7, 09:20 UTC | 25m |
| 2026-05-01 | UZB605 | SKD → DME | May 1, 19:05 UTC | May 2, 12:15 UTC | 17h 10m |
| 2026-05-01 | UZB276 | IST → SKD | May 1, 12:05 UTC | May 2, 12:00 UTC | 23h 55m |
| 2026-05-01 | UZB276 | IST → SKD | May 1, 11:55 UTC | May 1, 23:35 UTC | 11h 40m |
| 2026-05-01 | UZB275 | SKD → IST | May 1, 06:05 UTC | May 1, 07:30 UTC | 1h 25m |
| 2026-04-29 | UZB276 | IST → SKD | Apr 29, 19:15 UTC | Apr 29, 20:20 UTC | 1h 5m |
| 2026-04-29 | UZB275 | SKD → IST | Apr 29, 07:55 UTC | Apr 29, 15:15 UTC | 7h 21m |
| 2026-04-28 | UZB639 | SKD → LED | Apr 28, 15:15 UTC | Apr 29, 14:00 UTC | 22h 46m |
| 2026-04-27 | UZB276 | IST → SKD | Apr 27, 21:55 UTC | Apr 28, 15:55 UTC | 18h 0m |
| 2026-04-27 | UZB275 | SKD → IST | Apr 27, 10:05 UTC | Apr 27, 18:15 UTC | 8h 10m |
| 2026-04-25 | UZB9701 | - | Apr 25, 15:45 UTC | Apr 26, 06:40 UTC | 14h 55m |
| 2026-04-25 | UZB685 | TAS → AER | Apr 25, 04:30 UTC | Apr 25, 15:55 UTC | 11h 25m |
| 2026-04-23 | UZB291 | TAS → ESB | Apr 23, 04:50 UTC | Apr 23, 10:15 UTC | 5h 25m |
| 2026-04-20 | UZB667 | - | Apr 20, 16:50 UTC | Apr 20, 20:30 UTC | 3h 40m |
| 2026-04-19 | UZB746 | TBS → TAS | Apr 19, 08:05 UTC | Apr 19, 08:35 UTC | 30m |
| 2026-04-19 | UZB745 | TAS → TBS | Apr 19, 06:10 UTC | Apr 19, 06:30 UTC | 20m |
| 2026-04-18 | UZB292 | ESB → TAS | Apr 18, 09:05 UTC | Apr 18, 09:20 UTC | 15m |
| 2026-04-18 | UZB291 | TAS → ESB | Apr 18, 05:25 UTC | Apr 18, 06:15 UTC | 50m |
| 2026-04-18 | UZB291 | TAS → ESB | Apr 18, 04:50 UTC | Apr 18, 10:10 UTC | 5h 20m |
| 2026-04-15 | UZB668 | OVB → TAS | Apr 15, 20:10 UTC | Apr 15, 20:50 UTC | 40m |
| 2026-04-15 | UZB667 | - | Apr 15, 17:10 UTC | Apr 15, 17:40 UTC | 30m |
| 2026-04-13 | UZB281 | TAS → IST | Apr 13, 22:50 UTC | Apr 13, 23:35 UTC | 45m |
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 UK32017 page for operator, model, and routing details .