sensors Mode-S transponder

507C56

ICAO 24-bit transponder address · allocated to Uzbekistan

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

Hex
507C56
Octal
24076126
Decimal
5,274,710
Country
UZ
Tail
UK-32021
Type
A20N
No current signal · last broadcast Jul 25, 22:35 UTC
Flights observed
164
Distinct callsigns
20
Country
UZ
Last broadcast
Jul 25, 22:35 UTC

Last known position

Most recent position reported by Mode-S 507C56.

Country allocation

The ICAO 24-bit address 507C56 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 - 12 2026-06-23
UZB236 Uzbekistan Airways 12 2026-07-19
UZB282 - 11 2026-06-30
UZB235 Uzbekistan Airways 10 2026-07-19
UZB232 - 8 2026-06-29
UZB535 - 7 2026-07-24
UZB231 - 7 2026-06-29
UZB536 Uzbekistan Airways 6 2026-07-25
UZB533 - 6 2026-07-15
UZB279 Uzbekistan Airways 6 2026-05-19
UZB427 - 5 2026-07-16
UZB3229 - 5 2026-07-12
UZB211 Uzbekistan Airways 5 2026-07-24
UZB3230 - 4 2026-07-12
UZB3223 - 4 2026-07-14
UZB301 - 4 2026-06-22
UZB685 Uzbekistan Airways 3 2026-06-05
UZB428 - 3 2026-07-17
UZB341 - 3 2026-04-15
UZB3221 - 3 2026-06-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 UZB536 HKT → TAS Jul 25, 07:00 UTCJul 25, 22:35 UTC15h 35m
2026-07-24 UZB535 - Jul 24, 12:10 UTCJul 25, 06:15 UTC18h 5m
2026-07-24 UZB211 TAS → RIX Jul 24, 08:35 UTCJul 24, 08:50 UTC15m
2026-07-23 UZB212 RIX → TAS Jul 23, 12:10 UTCJul 23, 12:55 UTC45m
2026-07-23 UZB211 TAS → RIX Jul 23, 08:45 UTCJul 23, 09:05 UTC20m
2026-07-22 UZB212 RIX → TAS Jul 22, 12:15 UTCJul 23, 09:05 UTC20h 50m
2026-07-19 UZB236 MUC → TAS Jul 19, 09:40 UTCJul 19, 13:15 UTC3h 35m
2026-07-19 UZB235 TAS → MUC Jul 19, 05:25 UTCJul 19, 07:15 UTC1h 50m
2026-07-17 UZB428 - Jul 17, 00:25 UTCJul 17, 02:15 UTC1h 50m
2026-07-16 UZB427 - Jul 16, 20:25 UTCJul 16, 22:49 UTC2h 25m
2026-07-16 UZB634 LED → LED Jul 16, 10:20 UTCJul 16, 10:40 UTC20m
2026-07-15 UZB534 - Jul 15, 16:20 UTCJul 15, 20:25 UTC4h 5m
2026-07-15 UZB533 - Jul 15, 10:05 UTCJul 15, 14:30 UTC4h 25m
2026-07-14 UZB533 - Jul 14, 15:35 UTCJul 15, 14:30 UTC22h 54m
2026-07-14 UZB533 - Jul 14, 14:30 UTCJul 15, 13:30 UTC22h 59m
2026-07-14 UZB3223 - Jul 14, 00:10 UTCJul 14, 11:55 UTC11h 45m
2026-07-13 UZB427 - Jul 13, 20:15 UTCJul 13, 22:40 UTC2h 25m
2026-07-12 UZB3230 - Jul 12, 16:10 UTCJul 12, 18:20 UTC2h 10m
2026-07-12 UZB3229 - Jul 12, 11:20 UTCJul 12, 13:55 UTC2h 35m
2026-07-10 UZB535 - Jul 10, 21:15 UTCJul 11, 07:50 UTC10h 35m
2026-07-10 UZB535 - Jul 10, 02:15 UTCJul 10, 23:45 UTC21h 30m
2026-07-10 UZB535 - Jul 10, 00:20 UTCJul 10, 23:30 UTC23h 10m
2026-07-09 UZB427 - Jul 9, 20:10 UTCJul 9, 22:40 UTC2h 30m
2026-07-08 UZB534 - Jul 8, 16:55 UTCJul 8, 21:00 UTC4h 5m
2026-07-08 UZB533 - Jul 8, 10:10 UTCJul 8, 15:20 UTC5h 10m
2026-07-07 UZB533 - Jul 7, 15:35 UTCJul 8, 15:20 UTC23h 45m
2026-07-07 UZB533 - Jul 7, 14:25 UTCJul 8, 13:30 UTC23h 5m
2026-07-07 UZB3223 - Jul 7, 09:20 UTCJul 7, 12:00 UTC2h 40m
2026-07-05 UZB236 - Jul 5, 09:30 UTCJul 5, 13:05 UTC3h 35m
2026-07-01 UZB3230 - Jul 1, 10:05 UTCJul 1, 12:15 UTC2h 10m
2026-07-01 UZB3229 - Jul 1, 05:10 UTCJul 1, 07:55 UTC2h 45m
2026-06-30 UZB282 - Jun 30, 03:25 UTCJun 30, 05:25 UTC2h 0m
2026-06-29 UZB232 - Jun 29, 10:34 UTCJun 29, 23:44 UTC13h 10m
2026-06-29 UZB231 - Jun 29, 06:40 UTCJun 29, 07:44 UTC1h 5m
2026-06-26 UZB256 - Jun 26, 19:20 UTCJun 26, 23:15 UTC3h 55m
2026-06-26 UZB255 TAS → MXP Jun 26, 01:50 UTCJun 26, 17:25 UTC15h 35m
2026-06-25 UZB505 - Jun 25, 23:05 UTCJun 25, 23:14 UTC10m
2026-06-25 UZB334 - Jun 25, 08:50 UTCJun 25, 11:10 UTC2h 20m
2026-06-25 UZB333 - Jun 25, 04:20 UTCJun 25, 06:40 UTC2h 20m
2026-06-23 UZB282 - Jun 23, 04:29 UTCJun 23, 06:29 UTC2h 0m
2026-06-23 UZB281 - Jun 23, 02:09 UTCJun 23, 02:29 UTC20m
2026-06-22 UZB302 - Jun 22, 10:44 UTCJun 23, 01:35 UTC14h 50m
2026-06-22 UZB301 - Jun 22, 05:44 UTCJun 22, 08:44 UTC3h 0m
2026-06-21 UZB301 - Jun 21, 12:04 UTCJun 22, 08:44 UTC20h 40m
2026-06-21 UZB301 - Jun 21, 09:35 UTCJun 22, 08:44 UTC23h 10m
2026-06-21 UZB236 - Jun 21, 09:04 UTCJun 22, 07:10 UTC22h 5m
2026-06-21 UZB235 - Jun 21, 06:40 UTCJun 21, 07:20 UTC40m
2026-06-20 UZB235 - Jun 20, 07:34 UTCJun 21, 07:20 UTC23h 45m
2026-06-19 UZB535 - Jun 19, 21:09 UTCJun 20, 08:14 UTC11h 5m
2026-06-19 UZB535 - Jun 19, 12:09 UTCJun 20, 08:14 UTC20h 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-32021 page for operator, model, and routing details .

Mode-S 507C56 frequently asked

What is Mode-S code 507C56?
507C56 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK-32021.
Where is Mode-S 507C56 registered?
Mode-S code 507C56 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507C56 broadcasting right now?
No active broadcast right now. Last signal was Jul 25, 22:35 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507C56, octal 24076126, decimal 5,274,710.
What flights does 507C56 operate?
Mode-S 507C56 has broadcast 20 distinct callsigns, including UZB281, UZB236, UZB282, UZB235, UZB232.