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
- 99
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 20h 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB275 | - | 17 | 2026-06-26 |
| UZB276 | - | 12 | 2026-06-26 |
| UZB746 | - | 7 | 2026-07-12 |
| UZB710 | - | 7 | 2026-07-13 |
| UZB745 | - | 6 | 2026-07-12 |
| UZB709 | Uzbekistan Airways | 4 | 2026-05-09 |
| UZB304 | Uzbekistan Airways | 4 | 2026-07-07 |
| UZB303 | Uzbekistan Airways | 4 | 2026-07-07 |
| UZB301 | Uzbekistan Airways | 4 | 2026-06-10 |
| UZB280 | Uzbekistan Airways | 4 | 2026-07-10 |
| UZB279 | - | 4 | 2026-07-10 |
| UZB640 | Uzbekistan Airways | 3 | 2026-06-15 |
| UZB428 | - | 3 | 2026-06-12 |
| UZB3231 | - | 3 | 2026-06-25 |
| UZB685 | Uzbekistan Airways | 2 | 2026-06-13 |
| UZB605 | Uzbekistan Airways | 2 | 2026-05-27 |
| UZB427 | - | 2 | 2026-07-06 |
| UZB302 | Uzbekistan Airways | 2 | 2026-06-11 |
| UZB282 | Uzbekistan Airways | 2 | 2026-06-04 |
| UZB281 | Uzbekistan Airways | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UZB710 | - | Jul 13, 11:00 UTC | Jul 13, 11:15 UTC | 15m |
| 2026-07-12 | UZB746 | - | Jul 12, 08:10 UTC | Jul 12, 08:40 UTC | 30m |
| 2026-07-12 | UZB745 | - | Jul 12, 05:35 UTC | Jul 12, 06:05 UTC | 30m |
| 2026-07-10 | UZB280 | IST → UGC | Jul 10, 10:40 UTC | Jul 10, 12:35 UTC | 1h 55m |
| 2026-07-10 | UZB279 | - | Jul 10, 05:55 UTC | Jul 10, 08:40 UTC | 2h 45m |
| 2026-07-07 | UZB304 | TLV → TAS | Jul 7, 17:35 UTC | Jul 7, 19:45 UTC | 2h 10m |
| 2026-07-07 | UZB303 | TAS → TLV | Jul 7, 00:45 UTC | Jul 7, 15:45 UTC | 15h 0m |
| 2026-07-06 | UZB427 | - | Jul 6, 20:20 UTC | Jul 6, 23:00 UTC | 2h 40m |
| 2026-07-05 | UZB746 | - | Jul 5, 08:00 UTC | Jul 5, 08:30 UTC | 30m |
| 2026-07-05 | UZB745 | - | Jul 5, 05:35 UTC | Jul 5, 06:05 UTC | 30m |
| 2026-07-03 | UZB280 | IST → UGC | Jul 3, 10:40 UTC | Jul 3, 12:40 UTC | 2h 0m |
| 2026-07-03 | UZB279 | - | Jul 3, 05:55 UTC | Jul 3, 08:30 UTC | 2h 35m |
| 2026-07-01 | UZB668 | - | Jul 1, 16:45 UTC | Jul 1, 21:20 UTC | 4h 35m |
| 2026-06-30 | UZB304 | TLV → TAS | Jun 30, 17:30 UTC | Jul 1, 09:20 UTC | 15h 50m |
| 2026-06-30 | UZB303 | TAS → TLV | Jun 30, 12:55 UTC | Jun 30, 15:45 UTC | 2h 50m |
| 2026-06-26 | UZB276 | - | Jun 26, 12:34 UTC | Jun 27, 12:09 UTC | 23h 35m |
| 2026-06-26 | UZB276 | - | Jun 26, 10:55 UTC | Jun 26, 12:50 UTC | 1h 55m |
| 2026-06-26 | UZB275 | - | Jun 26, 06:15 UTC | Jun 26, 08:54 UTC | 2h 40m |
| 2026-06-25 | UZB275 | - | Jun 25, 10:35 UTC | Jun 26, 08:54 UTC | 22h 20m |
| 2026-06-25 | UZB3231 | - | Jun 25, 06:05 UTC | Jun 25, 08:55 UTC | 2h 50m |
| 2026-06-24 | UZB3231 | - | Jun 24, 12:34 UTC | Jun 25, 08:55 UTC | 20h 20m |
| 2026-06-24 | UZB3231 | - | Jun 24, 10:59 UTC | Jun 25, 08:55 UTC | 21h 55m |
| 2026-06-24 | UZB275 | - | Jun 24, 06:20 UTC | Jun 24, 08:49 UTC | 2h 30m |
| 2026-06-23 | UZB275 | - | Jun 23, 10:35 UTC | Jun 24, 08:49 UTC | 22h 15m |
| 2026-06-23 | UZB275 | - | Jun 23, 10:29 UTC | Jun 24, 08:30 UTC | 22h 0m |
| 2026-06-22 | UZB276 | - | Jun 22, 10:55 UTC | Jun 22, 12:54 UTC | 2h 0m |
| 2026-06-22 | UZB275 | - | Jun 22, 06:15 UTC | Jun 22, 08:54 UTC | 2h 40m |
| 2026-06-21 | UZB275 | - | Jun 21, 08:35 UTC | Jun 22, 08:29 UTC | 23h 55m |
| 2026-06-21 | UZB746 | - | Jun 21, 08:04 UTC | Jun 22, 06:29 UTC | 22h 25m |
| 2026-06-21 | UZB745 | - | Jun 21, 05:44 UTC | Jun 21, 06:14 UTC | 30m |
| 2026-06-19 | UZB280 | IST → UGC | Jun 19, 10:29 UTC | Jun 19, 12:34 UTC | 2h 5m |
| 2026-06-19 | UZB279 | - | Jun 19, 05:59 UTC | Jun 19, 08:40 UTC | 2h 40m |
| 2026-06-17 | UZB276 | IST → SKD | Jun 17, 12:10 UTC | Jun 17, 13:00 UTC | 50m |
| 2026-06-17 | UZB276 | IST → SKD | Jun 17, 11:00 UTC | Jun 17, 11:25 UTC | 25m |
| 2026-06-17 | UZB275 | - | Jun 17, 06:15 UTC | Jun 17, 08:45 UTC | 2h 30m |
| 2026-06-16 | UZB275 | - | Jun 16, 12:39 UTC | Jun 17, 08:45 UTC | 20h 6m |
| 2026-06-16 | UZB275 | - | Jun 16, 10:35 UTC | Jun 17, 08:45 UTC | 22h 11m |
| 2026-06-15 | UZB640 | LED → SKD | Jun 15, 23:35 UTC | Jun 16, 12:45 UTC | 13h 10m |
| 2026-06-15 | UZB276 | IST → SKD | Jun 15, 12:35 UTC | Jun 16, 10:45 UTC | 22h 10m |
| 2026-06-15 | UZB276 | IST → SKD | Jun 15, 10:55 UTC | Jun 16, 10:30 UTC | 23h 35m |
| 2026-06-14 | UZB275 | - | Jun 14, 18:55 UTC | Jun 15, 08:45 UTC | 13h 50m |
| 2026-06-13 | UZB685 | TAS → AER | Jun 13, 06:30 UTC | Jun 13, 16:50 UTC | 10h 20m |
| 2026-06-12 | UZB685 | TAS → AER | Jun 12, 15:20 UTC | Jun 13, 07:10 UTC | 15h 49m |
| 2026-06-12 | UZB428 | - | Jun 12, 00:40 UTC | Jun 12, 15:20 UTC | 14h 40m |
| 2026-06-11 | UZB302 | TLV → TAS | Jun 11, 11:00 UTC | Jun 11, 23:00 UTC | 12h 0m |
| 2026-06-10 | UZB301 | TAS → TLV | Jun 10, 16:25 UTC | Jun 11, 08:40 UTC | 16h 15m |
| 2026-06-09 | UZB746 | TBS → TAS | Jun 9, 07:55 UTC | Jun 9, 08:25 UTC | 30m |
| 2026-06-08 | UZB288 | IST → AZN | Jun 8, 11:05 UTC | Jun 9, 06:20 UTC | 19h 15m |
| 2026-06-07 | UZB287 | AZN → IST | Jun 7, 16:00 UTC | Jun 8, 09:05 UTC | 17h 5m |
| 2026-06-07 | UZB301 | TAS → TLV | Jun 7, 11:55 UTC | Jun 7, 14:40 UTC | 2h 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 UK-32019 page for operator, model, and routing details .