sensors Mode-S transponder
507C42
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32019 · AIRBUS A-320
- Hex
- 507C42
- Octal
- 24076102
- Decimal
- 5,274,690
- Country
- UZ
- Tail
- UK-32019
- Type
- A320
- Flights observed
- 38
- Distinct callsigns
- 15
- Country
- UZ
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 507C42 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB710 | Uzbekistan Airways | 6 | 2026-05-21 |
| UZB275 | Uzbekistan Airways | 6 | 2026-05-28 |
| UZB709 | Uzbekistan Airways | 4 | 2026-05-09 |
| UZB276 | Uzbekistan Airways | 4 | 2026-05-29 |
| UZB746 | Uzbekistan Airways | 3 | 2026-05-24 |
| UZB745 | Uzbekistan Airways | 3 | 2026-05-24 |
| UZB605 | Uzbekistan Airways | 2 | 2026-05-27 |
| UZB304 | Uzbekistan Airways | 2 | 2026-05-12 |
| UZB303 | Uzbekistan Airways | 2 | 2026-05-12 |
| UZB640 | Uzbekistan Airways | 1 | 2026-05-26 |
| UZB428 | - | 1 | 2026-05-22 |
| UZB427 | - | 1 | 2026-05-21 |
| UZB424 | Uzbekistan Airways | 1 | 2026-04-22 |
| UZB291 | Uzbekistan Airways | 1 | 2026-04-27 |
| UZB281 | Uzbekistan Airways | 1 | 2026-05-13 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB276 | IST → SKD | May 29, 11:00 UTC | May 29, 23:50 UTC | 12h 50m |
| 2026-05-28 | UZB275 | SKD → IST | May 28, 18:55 UTC | May 29, 09:05 UTC | 14h 10m |
| 2026-05-27 | UZB605 | SKD → DME | May 27, 20:35 UTC | May 28, 19:25 UTC | 22h 50m |
| 2026-05-27 | UZB276 | IST → SKD | May 27, 12:15 UTC | May 27, 20:50 UTC | 8h 35m |
| 2026-05-27 | UZB275 | SKD → IST | May 27, 10:25 UTC | May 27, 10:35 UTC | 10m |
| 2026-05-26 | UZB275 | SKD → IST | May 26, 21:34 UTC | May 27, 09:35 UTC | 12h 1m |
| 2026-05-26 | UZB640 | LED → SKD | May 26, 10:25 UTC | May 26, 11:30 UTC | 1h 5m |
| 2026-05-25 | UZB605 | SKD → DME | May 25, 12:35 UTC | May 26, 06:49 UTC | 18h 15m |
| 2026-05-25 | UZB276 | IST → SKD | May 25, 12:00 UTC | May 26, 06:49 UTC | 18h 49m |
| 2026-05-25 | UZB276 | IST → SKD | May 25, 11:00 UTC | May 25, 11:10 UTC | 10m |
| 2026-05-25 | UZB275 | SKD → IST | May 25, 08:50 UTC | May 25, 09:00 UTC | 10m |
| 2026-05-25 | UZB275 | SKD → IST | May 25, 06:35 UTC | May 25, 07:55 UTC | 1h 20m |
| 2026-05-24 | UZB275 | SKD → IST | May 24, 08:35 UTC | May 25, 07:55 UTC | 23h 20m |
| 2026-05-24 | UZB746 | TBS → TAS | May 24, 08:05 UTC | May 24, 08:35 UTC | 30m |
| 2026-05-24 | UZB745 | TAS → TBS | May 24, 05:50 UTC | May 24, 06:25 UTC | 35m |
| 2026-05-22 | UZB428 | - | May 22, 00:30 UTC | May 22, 01:25 UTC | 55m |
| 2026-05-21 | UZB427 | - | May 21, 21:30 UTC | May 21, 22:55 UTC | 1h 25m |
| 2026-05-21 | UZB710 | MSQ → TAS | May 21, 11:20 UTC | May 21, 11:35 UTC | 15m |
| 2026-05-19 | UZB746 | TBS → TAS | May 19, 08:00 UTC | May 19, 08:35 UTC | 35m |
| 2026-05-19 | UZB745 | TAS → TBS | May 19, 06:05 UTC | May 19, 06:35 UTC | 30m |
| 2026-05-16 | UZB710 | MSQ → TAS | May 16, 18:40 UTC | May 16, 19:10 UTC | 30m |
| 2026-05-13 | UZB281 | TAS → IST | May 13, 23:00 UTC | May 14, 05:50 UTC | 6h 50m |
| 2026-05-12 | UZB304 | TLV → TAS | May 12, 17:30 UTC | May 12, 19:50 UTC | 2h 20m |
| 2026-05-12 | UZB303 | TAS → TLV | May 12, 12:45 UTC | May 12, 15:30 UTC | 2h 45m |
| 2026-05-09 | UZB709 | TAS → MSQ | May 9, 14:25 UTC | May 9, 15:05 UTC | 40m |
| 2026-05-05 | UZB746 | TBS → TAS | May 5, 08:25 UTC | May 5, 08:55 UTC | 30m |
| 2026-05-05 | UZB745 | TAS → TBS | May 5, 06:00 UTC | May 5, 06:30 UTC | 30m |
| 2026-04-27 | UZB291 | TAS → ESB | Apr 27, 04:50 UTC | Apr 27, 17:05 UTC | 12h 15m |
| 2026-04-25 | UZB710 | MSQ → TAS | Apr 25, 18:35 UTC | Apr 25, 19:05 UTC | 30m |
| 2026-04-25 | UZB709 | TAS → MSQ | Apr 25, 14:35 UTC | Apr 25, 14:50 UTC | 15m |
| 2026-04-23 | UZB710 | MSQ → TAS | Apr 23, 10:55 UTC | Apr 23, 12:50 UTC | 1h 55m |
| 2026-04-22 | UZB424 | DEL → TAS | Apr 22, 08:55 UTC | Apr 22, 20:30 UTC | 11h 35m |
| 2026-04-21 | UZB304 | TLV → TAS | Apr 21, 17:35 UTC | Apr 22, 06:25 UTC | 12h 50m |
| 2026-04-21 | UZB303 | - | Apr 21, 13:01 UTC | Apr 21, 15:51 UTC | 2h 50m |
| 2026-04-16 | UZB710 | - | Apr 16, 11:09 UTC | Apr 16, 11:29 UTC | 20m |
| 2026-04-13 | UZB710 | - | Apr 13, 11:00 UTC | Apr 13, 11:35 UTC | 35m |
| 2026-04-13 | UZB709 | TAS → MSQ | Apr 13, 08:50 UTC | Apr 13, 09:00 UTC | 10m |
| 2026-04-13 | UZB709 | TAS → MSQ | Apr 13, 06:55 UTC | Apr 13, 07:35 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-32019 page for operator, model, and routing details .