sensors Mode-S transponder

507C60

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK-32103 · AIRBUS A-321neo

Hex
507C60
Octal
24076140
Decimal
5,274,720
Country
UZ
Tail
UK-32103
Type
A21N
No current signal · last broadcast 55m ago
Flights observed
98
Distinct callsigns
20
Country
UZ
Last broadcast
55m ago

Last known position

Most recent position reported by Mode-S 507C60.

Country allocation

The ICAO 24-bit address 507C60 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-13 UZB561 TAS → CXR Jun 13, 12:35 UTCJun 14, 01:35 UTC13h 0m
2026-06-12 UZB256 - Jun 12, 19:30 UTCJun 13, 10:35 UTC15h 4m
2026-06-12 UZB255 TAS → MXP Jun 12, 01:30 UTCJun 12, 17:50 UTC16h 20m
2026-06-11 UZB531 TAS → BKK Jun 11, 11:00 UTCJun 11, 23:40 UTC12h 40m
2026-06-10 UZB531 TAS → BKK Jun 10, 21:15 UTCJun 11, 20:00 UTC22h 45m
2026-06-10 UZB613 TAS → VKO Jun 10, 16:05 UTCJun 11, 11:00 UTC18h 55m
2026-06-10 UZB613 TAS → VKO Jun 10, 15:55 UTCJun 11, 11:00 UTC19h 5m
2026-06-10 UZB562 CXR → TAS Jun 10, 05:00 UTCJun 10, 21:20 UTC16h 20m
2026-06-10 UZB562 CXR → TAS Jun 10, 00:15 UTCJun 10, 21:20 UTC21h 5m
2026-06-09 UZB562 CXR → TAS Jun 9, 22:05 UTCJun 10, 21:20 UTC23h 15m
2026-06-09 UZB562 CXR → TAS Jun 9, 21:00 UTCJun 10, 16:35 UTC19h 35m
2026-06-09 UZB561 TAS → CXR Jun 9, 04:05 UTCJun 10, 01:25 UTC21h 20m
2026-06-09 UZB532 BKK → TAS Jun 9, 02:05 UTCJun 10, 01:25 UTC23h 20m
2026-06-09 UZB532 BKK → TAS Jun 9, 01:45 UTCJun 9, 23:30 UTC21h 45m
2026-06-08 UZB531 TAS → BKK Jun 8, 19:45 UTCJun 8, 23:50 UTC4h 5m
2026-06-07 UZB531 TAS → BKK Jun 7, 20:05 UTCJun 8, 20:00 UTC23h 55m
2026-06-07 UZB204 LHR → TAS Jun 7, 17:35 UTCJun 7, 20:05 UTC2h 30m
2026-06-07 UZB203 TAS → LHR Jun 7, 10:40 UTCJun 7, 15:25 UTC4h 45m
2026-06-06 UZB203 TAS → LHR Jun 6, 14:30 UTCJun 7, 14:00 UTC23h 30m
2026-06-06 UZB342 SSH → TAS Jun 6, 12:30 UTCJun 7, 11:55 UTC23h 25m
2026-06-05 UZB341 - Jun 5, 20:05 UTCJun 6, 15:39 UTC19h 35m
2026-06-05 UZB252 CDG → TAS Jun 5, 18:25 UTCJun 6, 15:39 UTC21h 15m
2026-06-05 UZB251 TAS → CDG Jun 5, 03:35 UTCJun 5, 17:00 UTC13h 25m
2026-06-05 UZB281 TAS → IST Jun 5, 01:20 UTCJun 5, 01:45 UTC25m
2026-06-04 UZB281 TAS → IST Jun 4, 09:05 UTCJun 5, 00:35 UTC15h 30m
2026-06-04 UZB554 KUL → TAS Jun 4, 04:40 UTCJun 5, 00:35 UTC19h 55m
2026-06-03 UZB342 SSH → TAS Jun 3, 08:05 UTCJun 4, 02:20 UTC18h 15m
2026-06-03 UZB341 - Jun 3, 06:55 UTCJun 4, 02:20 UTC19h 25m
2026-06-02 UZB341 - Jun 2, 22:15 UTCJun 3, 21:40 UTC23h 25m
2026-06-02 UZB341 - Jun 2, 20:05 UTCJun 3, 15:05 UTC19h 0m
2026-06-02 UZB252 CDG → TAS Jun 2, 18:45 UTCJun 3, 15:05 UTC20h 20m
2026-06-02 UZB510 - Jun 2, 01:20 UTCJun 2, 16:15 UTC14h 55m
2026-06-01 UZB510 - Jun 1, 21:30 UTCJun 2, 16:15 UTC18h 45m
2026-05-31 UZB562 CXR → TAS May 31, 08:25 UTCMay 31, 21:35 UTC13h 10m
2026-05-31 UZB562 CXR → TAS May 31, 00:15 UTCMay 31, 21:35 UTC21h 20m
2026-05-30 UZB561 TAS → CXR May 30, 22:05 UTCMay 31, 21:35 UTC23h 30m
2026-05-30 UZB561 TAS → CXR May 30, 20:30 UTCMay 31, 09:50 UTC13h 20m
2026-05-30 UZB561 TAS → CXR May 30, 12:05 UTCMay 31, 09:50 UTC21h 45m
2026-05-30 UZB561 TAS → CXR May 30, 10:25 UTCMay 31, 09:50 UTC23h 25m
2026-05-30 UZB231 TAS → FRA May 30, 06:35 UTCMay 30, 07:15 UTC40m
2026-05-28 UZB554 KUL → TAS May 28, 08:45 UTCMay 28, 09:50 UTC1h 5m
2026-05-28 UZB554 KUL → TAS May 28, 04:30 UTCMay 28, 04:40 UTC10m
2026-05-28 UZB553 TAS → KUL May 28, 02:10 UTCMay 28, 02:30 UTC20m
2026-05-27 UZB342 SSH → TAS May 27, 07:15 UTCMay 27, 22:30 UTC15h 15m
2026-05-26 UZB342 SSH → TAS May 26, 22:29 UTCMay 27, 22:00 UTC23h 31m
2026-05-26 UZB342 SSH → TAS May 26, 20:05 UTCMay 27, 15:40 UTC19h 36m
2026-05-26 UZB342 SSH → TAS May 26, 18:45 UTCMay 27, 15:40 UTC20h 56m
2026-05-26 UZB510 - May 26, 02:00 UTCMay 26, 16:45 UTC14h 45m
2026-05-25 UZB510 - May 25, 04:15 UTCMay 26, 04:00 UTC23h 44m
2026-05-25 UZB282 IST → TAS May 25, 03:15 UTCMay 26, 02:00 UTC22h 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-32103 page for operator, model, and routing details .

Mode-S 507C60 frequently asked

What is Mode-S code 507C60?
507C60 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK-32103.
Where is Mode-S 507C60 registered?
Mode-S code 507C60 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507C60 broadcasting right now?
No active broadcast right now. Last signal was 55m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507C60, octal 24076140, decimal 5,274,720.
What flights does 507C60 operate?
Mode-S 507C60 has broadcast 20 distinct callsigns, including UZB342, UZB252, UZB510, UZB341, UZB562.