sensors Mode-S transponder

507CB9

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK32112 · AIRBUS A-321neo

Hex
507CB9
Octal
24076271
Decimal
5,274,809
Country
UZ
Tail
UK32112
Type
A21N
No current signal · last broadcast 11h ago
Flights observed
142
Distinct callsigns
15
Country
UZ
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S 507CB9.

Country allocation

The ICAO 24-bit address 507CB9 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 15 distinct

Callsign Airline Flights Last seen
QNT862 - 37 2026-07-12
QNT443 - 19 2026-07-13
QNT492 - 15 2026-07-10
QNT867 - 10 2026-07-12
QNT444 - 10 2026-07-13
QNT202 - 10 2026-06-10
QNT822 - 8 2026-07-11
QNT821 - 8 2026-07-11
QNT868 - 6 2026-05-29
QNT406 - 6 2026-07-08
QNT201 - 6 2026-06-24
QNT405 Qanot Sharq 3 2026-06-30
QNT2240 - 2 2026-06-12
QNT861 - 1 2026-06-01
QNT491 - 1 2026-06-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 QNT444 - Jul 13, 19:15 UTCJul 13, 23:45 UTC4h 30m
2026-07-13 QNT443 - Jul 13, 14:35 UTCJul 13, 16:50 UTC2h 15m
2026-07-12 QNT443 - Jul 12, 18:25 UTCJul 13, 16:50 UTC22h 25m
2026-07-12 QNT867 - Jul 12, 15:35 UTCJul 12, 15:45 UTC10m
2026-07-12 QNT862 - Jul 12, 02:35 UTCJul 12, 06:05 UTC3h 30m
2026-07-11 QNT822 - Jul 11, 07:25 UTCJul 11, 07:45 UTC20m
2026-07-11 QNT821 - Jul 11, 04:45 UTCJul 11, 05:10 UTC25m
2026-07-10 QNT492 - Jul 10, 15:10 UTCJul 11, 04:01 UTC12h 51m
2026-07-09 QNT444 LGW → FRA Jul 9, 22:25 UTCJul 10, 13:15 UTC14h 50m
2026-07-09 QNT443 - Jul 9, 18:10 UTCJul 9, 19:50 UTC1h 40m
2026-07-08 QNT406 - Jul 8, 12:25 UTCJul 8, 15:55 UTC3h 30m
2026-07-07 QNT492 - Jul 7, 13:35 UTCJul 7, 17:25 UTC3h 50m
2026-07-06 QNT444 LGW → FRA Jul 6, 18:35 UTCJul 7, 11:20 UTC16h 45m
2026-07-06 QNT443 - Jul 6, 14:10 UTCJul 6, 16:10 UTC2h 0m
2026-07-05 QNT443 - Jul 5, 18:25 UTCJul 6, 16:10 UTC21h 45m
2026-07-05 QNT867 - Jul 5, 15:25 UTCJul 5, 15:40 UTC15m
2026-07-05 QNT862 - Jul 5, 01:25 UTCJul 5, 05:35 UTC4h 10m
2026-07-04 QNT862 - Jul 4, 08:20 UTCJul 5, 05:35 UTC21h 15m
2026-07-04 QNT862 - Jul 4, 07:55 UTCJul 5, 05:35 UTC21h 40m
2026-07-04 QNT822 - Jul 4, 06:45 UTCJul 4, 07:00 UTC15m
2026-07-04 QNT821 - Jul 4, 04:15 UTCJul 4, 04:35 UTC20m
2026-07-03 QNT492 - Jul 3, 14:40 UTCJul 4, 03:20 UTC12h 40m
2026-07-02 QNT444 LGW → FRA Jul 2, 21:15 UTCJul 3, 12:35 UTC15h 20m
2026-07-02 QNT443 - Jul 2, 17:20 UTCJul 2, 19:30 UTC2h 10m
2026-07-01 QNT406 PRG → TAS Jul 1, 13:25 UTCJul 1, 17:15 UTC3h 50m
2026-06-30 QNT405 TAS → PRG Jun 30, 16:55 UTCJul 1, 11:10 UTC18h 15m
2026-06-30 QNT492 - Jun 30, 14:20 UTCJul 1, 11:10 UTC20h 50m
2026-06-30 QNT492 - Jun 30, 13:30 UTCJun 30, 17:30 UTC4h 0m
2026-06-29 QNT444 LGW → FRA Jun 29, 18:05 UTCJun 30, 11:30 UTC17h 25m
2026-06-28 QNT443 - Jun 28, 18:40 UTCJun 29, 16:15 UTC21h 35m
2026-06-28 QNT867 - Jun 28, 16:05 UTCJun 28, 16:19 UTC15m
2026-06-28 QNT862 - Jun 28, 01:25 UTCJun 28, 05:29 UTC4h 5m
2026-06-27 QNT822 - Jun 27, 06:59 UTCJun 27, 20:39 UTC13h 40m
2026-06-27 QNT822 - Jun 27, 05:44 UTCJun 27, 06:05 UTC20m
2026-06-27 QNT821 - Jun 27, 03:25 UTCJun 27, 03:49 UTC25m
2026-06-26 QNT492 - Jun 26, 13:59 UTCJun 27, 02:35 UTC12h 35m
2026-06-25 QNT444 LGW → FRA Jun 25, 21:10 UTCJun 26, 11:49 UTC14h 40m
2026-06-25 QNT443 - Jun 25, 00:19 UTCJun 25, 19:29 UTC19h 10m
2026-06-24 QNT443 - Jun 24, 22:19 UTCJun 25, 19:29 UTC21h 10m
2026-06-24 QNT443 - Jun 24, 22:04 UTCJun 25, 19:29 UTC21h 25m
2026-06-24 QNT201 - Jun 24, 14:20 UTCJun 25, 08:50 UTC18h 30m
2026-06-24 QNT406 PRG → TAS Jun 24, 12:54 UTCJun 25, 08:50 UTC19h 55m
2026-06-23 QNT492 - Jun 23, 14:19 UTCJun 24, 11:05 UTC20h 45m
2026-06-23 QNT492 FRA → PRG Jun 23, 13:15 UTCJun 24, 11:05 UTC21h 50m
2026-06-22 QNT444 LGW → FRA Jun 22, 18:04 UTCJun 23, 11:24 UTC17h 20m
2026-06-22 QNT443 - Jun 22, 13:39 UTCJun 22, 16:20 UTC2h 40m
2026-06-21 QNT443 - Jun 21, 20:45 UTCJun 22, 16:20 UTC19h 35m
2026-06-21 QNT867 - Jun 21, 18:35 UTCJun 21, 18:50 UTC15m
2026-06-21 QNT862 - Jun 21, 01:59 UTCJun 21, 10:19 UTC8h 20m
2026-06-20 QNT862 - Jun 20, 12:19 UTCJun 21, 10:19 UTC22h 0m

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 UK32112 page for operator, model, and routing details .

Mode-S 507CB9 frequently asked

What is Mode-S code 507CB9?
507CB9 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK32112.
Where is Mode-S 507CB9 registered?
Mode-S code 507CB9 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CB9 broadcasting right now?
No active broadcast right now. Last signal was 11h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507CB9, octal 24076271, decimal 5,274,809.
What flights does 507CB9 operate?
Mode-S 507CB9 has broadcast 15 distinct callsigns, including QNT862, QNT443, QNT492, QNT867, QNT444.