sensors Mode-S transponder

507C5A

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK-32023 · AIRBUS A-320neo

Hex
507C5A
Octal
24076132
Decimal
5,274,714
Country
UZ
Tail
UK-32023
Type
A20N
No current signal · last broadcast 2h ago
Flights observed
144
Distinct callsigns
20
Country
UZ
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 507C5A.

Country allocation

The ICAO 24-bit address 507C5A 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
UZB535 - 17 2026-07-17
UZB281 - 14 2026-07-04
UZB211 - 12 2026-07-17
UZB536 - 11 2026-07-15
UZB282 - 11 2026-07-05
UZB232 - 10 2026-07-13
UZB235 - 8 2026-06-18
UZB231 - 7 2026-07-13
UZB212 Uzbekistan Airways 7 2026-07-16
UZB532 Uzbekistan Airways 4 2026-05-29
UZB236 - 4 2026-06-19
UZB645 Uzbekistan Airways 3 2026-05-13
UZB634 Uzbekistan Airways 3 2026-06-30
UZB633 - 3 2026-06-30
UZB632 Uzbekistan Airways 3 2026-05-30
UZB428 - 3 2026-06-05
UZB3229 - 3 2026-06-28
UZB531 Uzbekistan Airways 2 2026-05-28
UZB427 - 2 2026-05-25
UZB423 Uzbekistan Airways 2 2026-04-23

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 UZB535 - Jul 17, 12:25 UTCJul 18, 00:00 UTC11h 35m
2026-07-17 UZB211 - Jul 17, 08:40 UTCJul 17, 08:49 UTC10m
2026-07-16 UZB212 RIX → TAS Jul 16, 12:34 UTCJul 17, 06:45 UTC18h 10m
2026-07-16 UZB212 RIX → TAS Jul 16, 12:14 UTCJul 17, 06:45 UTC18h 30m
2026-07-16 UZB211 - Jul 16, 08:30 UTCJul 16, 08:50 UTC20m
2026-07-16 UZB211 - Jul 16, 06:30 UTCJul 16, 06:50 UTC20m
2026-07-15 UZB211 - Jul 15, 08:35 UTCJul 16, 06:50 UTC22h 15m
2026-07-15 UZB536 - Jul 15, 06:35 UTCJul 16, 06:30 UTC23h 55m
2026-07-14 UZB535 - Jul 14, 21:45 UTCJul 15, 08:40 UTC10h 54m
2026-07-14 UZB535 - Jul 14, 10:40 UTCJul 15, 08:40 UTC21h 59m
2026-07-14 UZB535 - Jul 14, 06:35 UTCJul 15, 06:30 UTC23h 54m
2026-07-13 UZB232 - Jul 13, 13:40 UTCJul 14, 10:55 UTC21h 15m
2026-07-13 UZB232 - Jul 13, 10:35 UTCJul 14, 06:50 UTC20h 15m
2026-07-13 UZB232 - Jul 13, 10:10 UTCJul 14, 06:50 UTC20h 40m
2026-07-13 UZB231 - Jul 13, 03:45 UTCJul 13, 07:40 UTC3h 55m
2026-07-10 UZB212 RIX → TAS Jul 10, 12:10 UTCJul 10, 12:50 UTC40m
2026-07-10 UZB211 - Jul 10, 08:25 UTCJul 10, 08:40 UTC15m
2026-07-09 UZB212 RIX → TAS Jul 9, 12:05 UTCJul 9, 12:45 UTC40m
2026-07-08 UZB211 - Jul 8, 22:35 UTCJul 9, 08:30 UTC9h 55m
2026-07-08 UZB211 - Jul 8, 08:35 UTCJul 9, 08:30 UTC23h 55m
2026-07-08 UZB536 - Jul 8, 05:55 UTCJul 8, 22:40 UTC16h 45m
2026-07-07 UZB536 - Jul 7, 21:50 UTCJul 8, 08:35 UTC10h 45m
2026-07-07 UZB536 - Jul 7, 12:35 UTCJul 8, 08:35 UTC20h 0m
2026-07-06 UZB232 - Jul 6, 14:00 UTCJul 7, 12:30 UTC22h 30m
2026-07-06 UZB232 - Jul 6, 10:20 UTCJul 6, 14:10 UTC3h 50m
2026-07-06 UZB231 - Jul 6, 07:00 UTCJul 6, 08:05 UTC1h 5m
2026-07-05 UZB282 - Jul 5, 03:10 UTCJul 5, 05:05 UTC1h 55m
2026-07-04 UZB281 - Jul 4, 10:30 UTCJul 5, 01:05 UTC14h 35m
2026-07-04 UZB747 - Jul 4, 07:55 UTCJul 4, 08:55 UTC1h 0m
2026-07-02 UZB212 RIX → TAS Jul 2, 12:05 UTCJul 2, 12:35 UTC30m
2026-07-02 UZB211 - Jul 2, 08:25 UTCJul 2, 08:45 UTC20m
2026-07-01 UZB536 - Jul 1, 06:25 UTCJul 1, 22:35 UTC16h 10m
2026-06-30 UZB535 - Jun 30, 21:55 UTCJul 1, 08:40 UTC10h 45m
2026-06-30 UZB634 LED → TAS Jun 30, 10:35 UTCJun 30, 11:25 UTC50m
2026-06-30 UZB633 - Jun 30, 08:15 UTCJun 30, 08:35 UTC20m
2026-06-28 UZB3230 - Jun 28, 15:14 UTCJun 28, 17:25 UTC2h 10m
2026-06-28 UZB3229 - Jun 28, 10:55 UTCJun 28, 13:29 UTC2h 35m
2026-06-27 UZB3229 - Jun 27, 16:35 UTCJun 28, 13:29 UTC20h 55m
2026-06-26 UZB536 - Jun 26, 22:34 UTCJun 27, 16:55 UTC18h 20m
2026-06-26 UZB535 - Jun 26, 21:10 UTCJun 27, 16:55 UTC19h 45m
2026-06-26 UZB535 - Jun 26, 12:34 UTCJun 27, 08:05 UTC19h 30m
2026-06-26 UZB535 - Jun 26, 12:10 UTCJun 27, 08:05 UTC19h 55m
2026-06-26 UZB211 - Jun 26, 08:34 UTCJun 26, 08:50 UTC15m
2026-06-25 UZB212 RIX → TAS Jun 25, 12:04 UTCJun 25, 14:09 UTC2h 5m
2026-06-25 UZB211 - Jun 25, 08:40 UTCJun 25, 08:55 UTC15m
2026-06-24 UZB631 TAS → LED Jun 24, 16:45 UTCJun 25, 07:54 UTC15h 10m
2026-06-24 UZB536 - Jun 24, 05:49 UTCJun 24, 22:25 UTC16h 35m
2026-06-24 UZB536 - Jun 24, 00:34 UTCJun 24, 22:25 UTC21h 50m
2026-06-23 UZB536 - Jun 23, 22:34 UTCJun 24, 22:25 UTC23h 50m
2026-06-23 UZB535 - Jun 23, 21:54 UTCJun 24, 16:59 UTC19h 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-32023 page for operator, model, and routing details .

Mode-S 507C5A frequently asked

What is Mode-S code 507C5A?
507C5A is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK-32023.
Where is Mode-S 507C5A registered?
Mode-S code 507C5A is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507C5A broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507C5A, octal 24076132, decimal 5,274,714.
What flights does 507C5A operate?
Mode-S 507C5A has broadcast 20 distinct callsigns, including UZB535, UZB281, UZB211, UZB536, UZB282.