sensors Mode-S transponder
507C3F
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-32016 · AIRBUS A-320
- Hex
- 507C3F
- Octal
- 24076077
- Decimal
- 5,274,687
- Country
- UZ
- Tail
- UK-32016
- Type
- A320
- Flights observed
- 94
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 507C3F 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 | - | 22 | 2026-07-12 |
| UZB276 | - | 16 | 2026-07-13 |
| UZB605 | Uzbekistan Airways | 6 | 2026-05-13 |
| UZB279 | - | 6 | 2026-06-26 |
| UZB745 | - | 5 | 2026-06-15 |
| UZB3231 | - | 5 | 2026-07-08 |
| UZB709 | - | 4 | 2026-06-15 |
| UZB640 | Uzbekistan Airways | 4 | 2026-07-11 |
| UZB291 | Uzbekistan Airways | 4 | 2026-05-02 |
| UZB746 | - | 3 | 2026-06-16 |
| UZB639 | Uzbekistan Airways | 3 | 2026-06-20 |
| UZB292 | Uzbekistan Airways | 2 | 2026-05-02 |
| UZB282 | - | 2 | 2026-06-25 |
| UZB281 | - | 2 | 2026-06-24 |
| UZB9701 | - | 1 | 2026-06-07 |
| UZB710 | Uzbekistan Airways | 1 | 2026-05-30 |
| UZB633 | Uzbekistan Airways | 1 | 2026-05-06 |
| UZB632 | Uzbekistan Airways | 1 | 2026-04-19 |
| UZB428 | - | 1 | 2026-06-30 |
| UZB427 | - | 1 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UZB276 | - | Jul 13, 10:50 UTC | Jul 13, 19:20 UTC | 8h 30m |
| 2026-07-12 | UZB275 | - | Jul 12, 23:25 UTC | Jul 13, 08:55 UTC | 9h 30m |
| 2026-07-11 | UZB640 | LED → SKD | Jul 11, 10:35 UTC | Jul 11, 11:20 UTC | 45m |
| 2026-07-10 | UZB276 | - | Jul 10, 10:45 UTC | Jul 10, 12:40 UTC | 1h 55m |
| 2026-07-10 | UZB275 | - | Jul 10, 06:05 UTC | Jul 10, 08:50 UTC | 2h 45m |
| 2026-07-09 | UZB275 | - | Jul 9, 11:50 UTC | Jul 10, 08:50 UTC | 21h 0m |
| 2026-07-09 | UZB275 | - | Jul 9, 10:45 UTC | Jul 10, 08:50 UTC | 22h 5m |
| 2026-07-08 | UZB3231 | - | Jul 8, 10:55 UTC | Jul 9, 08:40 UTC | 21h 45m |
| 2026-07-08 | UZB275 | - | Jul 8, 06:00 UTC | Jul 8, 08:40 UTC | 2h 40m |
| 2026-07-06 | UZB276 | - | Jul 6, 10:50 UTC | Jul 6, 12:45 UTC | 1h 55m |
| 2026-07-06 | UZB275 | - | Jul 6, 06:05 UTC | Jul 6, 08:50 UTC | 2h 45m |
| 2026-06-30 | UZB3510 | - | Jun 30, 19:45 UTC | Jun 30, 20:10 UTC | 25m |
| 2026-06-30 | UZB428 | - | Jun 30, 00:55 UTC | Jun 30, 18:35 UTC | 17h 41m |
| 2026-06-29 | UZB427 | - | Jun 29, 20:40 UTC | Jun 29, 22:55 UTC | 2h 15m |
| 2026-06-26 | UZB280 | IST → UGC | Jun 26, 11:40 UTC | Jun 27, 08:44 UTC | 21h 5m |
| 2026-06-26 | UZB279 | - | Jun 26, 07:10 UTC | Jun 26, 09:39 UTC | 2h 30m |
| 2026-06-25 | UZB282 | - | Jun 25, 03:44 UTC | Jun 25, 05:44 UTC | 2h 0m |
| 2026-06-24 | UZB281 | - | Jun 24, 23:20 UTC | Jun 25, 01:50 UTC | 2h 30m |
| 2026-06-20 | UZB639 | SKD → LED | Jun 20, 09:14 UTC | Jun 20, 09:29 UTC | 15m |
| 2026-06-19 | UZB276 | IST → SKD | Jun 19, 12:49 UTC | Jun 19, 14:44 UTC | 1h 55m |
| 2026-06-19 | UZB275 | - | Jun 19, 08:29 UTC | Jun 19, 11:04 UTC | 2h 35m |
| 2026-06-18 | UZB275 | - | Jun 18, 12:05 UTC | Jun 19, 11:04 UTC | 22h 59m |
| 2026-06-18 | UZB3231 | - | Jun 18, 07:35 UTC | Jun 18, 13:45 UTC | 6h 10m |
| 2026-06-16 | UZB746 | - | Jun 16, 08:05 UTC | Jun 16, 08:39 UTC | 35m |
| 2026-06-15 | UZB745 | - | Jun 15, 16:15 UTC | Jun 16, 06:40 UTC | 14h 25m |
| 2026-06-15 | UZB709 | - | Jun 15, 11:54 UTC | Jun 15, 12:39 UTC | 45m |
| 2026-06-15 | UZB709 | - | Jun 15, 06:49 UTC | Jun 15, 07:10 UTC | 20m |
| 2026-06-13 | UZB640 | LED → SKD | Jun 13, 10:30 UTC | Jun 13, 10:45 UTC | 15m |
| 2026-06-12 | UZB276 | IST → SKD | Jun 12, 12:15 UTC | Jun 13, 07:10 UTC | 18h 54m |
| 2026-06-12 | UZB276 | IST → SKD | Jun 12, 11:20 UTC | Jun 13, 07:10 UTC | 19h 49m |
| 2026-06-11 | UZB275 | - | Jun 11, 13:50 UTC | Jun 12, 09:30 UTC | 19h 41m |
| 2026-06-11 | UZB275 | - | Jun 11, 12:20 UTC | Jun 12, 09:30 UTC | 21h 11m |
| 2026-06-11 | UZB3231 | - | Jun 11, 09:45 UTC | Jun 11, 10:10 UTC | 25m |
| 2026-06-10 | UZB3231 | - | Jun 10, 19:40 UTC | Jun 11, 09:00 UTC | 13h 20m |
| 2026-06-10 | UZB3231 | - | Jun 10, 11:50 UTC | Jun 11, 09:00 UTC | 21h 10m |
| 2026-06-10 | UZB276 | IST → SKD | Jun 10, 10:55 UTC | Jun 11, 09:00 UTC | 22h 5m |
| 2026-06-10 | UZB275 | SKD → IST | Jun 10, 06:15 UTC | Jun 10, 08:55 UTC | 2h 40m |
| 2026-06-09 | UZB640 | LED → SKD | Jun 9, 10:20 UTC | Jun 9, 10:45 UTC | 25m |
| 2026-06-08 | UZB276 | IST → SKD | Jun 8, 11:50 UTC | Jun 9, 06:35 UTC | 18h 45m |
| 2026-06-08 | UZB276 | IST → SKD | Jun 8, 10:40 UTC | Jun 9, 06:35 UTC | 19h 55m |
| 2026-06-08 | UZB275 | SKD → IST | Jun 8, 08:30 UTC | Jun 8, 08:50 UTC | 20m |
| 2026-06-08 | UZB275 | SKD → IST | Jun 8, 06:15 UTC | Jun 8, 07:35 UTC | 1h 20m |
| 2026-06-07 | UZB9701 | - | Jun 7, 06:10 UTC | Jun 7, 06:40 UTC | 30m |
| 2026-06-02 | UZB304 | TLV → TAS | Jun 2, 17:55 UTC | Jun 2, 20:15 UTC | 2h 20m |
| 2026-06-02 | UZB303 | TAS → TLV | Jun 2, 13:10 UTC | Jun 2, 15:55 UTC | 2h 45m |
| 2026-05-30 | UZB710 | MSQ → TAS | May 30, 18:25 UTC | May 30, 20:30 UTC | 2h 5m |
| 2026-05-30 | UZB709 | TAS → MSQ | May 30, 04:35 UTC | May 30, 14:55 UTC | 10h 20m |
| 2026-05-29 | UZB282 | IST → TAS | May 29, 03:10 UTC | May 29, 05:15 UTC | 2h 5m |
| 2026-05-28 | UZB281 | TAS → IST | May 28, 07:00 UTC | May 29, 01:20 UTC | 18h 20m |
| 2026-05-27 | UZB709 | TAS → MSQ | May 27, 16:35 UTC | May 28, 07:40 UTC | 15h 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 UK-32016 page for operator, model, and routing details .