sensors Mode-S transponder

507CC3

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK32133 · AIRBUS A-321neo

Hex
507CC3
Octal
24076303
Decimal
5,274,819
Country
UZ
Tail
UK32133
Type
A21N
No current signal · last broadcast Jul 26, 11:45 UTC
Flights observed
171
Distinct callsigns
20
Country
UZ
Last broadcast
Jul 26, 11:45 UTC

Last known position

Most recent position reported by Mode-S 507CC3.

Country allocation

The ICAO 24-bit address 507CC3 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
MFX3307 - 21 2026-07-22
MFX530 - 17 2026-06-06
MFX531 - 12 2026-07-06
MFX3308 - 11 2026-07-23
MFX3362 - 10 2026-07-18
MFX221 - 10 2026-07-06
MFX3309 - 8 2026-07-24
MFX529 - 7 2026-07-16
MFX3361 - 7 2026-07-17
MFX525 - 6 2026-05-21
MFX223 - 6 2026-07-25
MFX222 - 6 2026-06-13
MFX5536 - 5 2026-05-18
MFX526 - 5 2026-05-22
MFX224 - 4 2026-07-25
MFX4403 - 3 2026-06-22
MFX352 My Freighter LLC 3 2026-05-23
MFX351 My Freighter LLC 3 2026-05-07
MFX3363 - 3 2026-04-14
MFX315 My Freighter LLC 3 2026-05-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 MFX224 - Jul 25, 19:05 UTCJul 26, 11:45 UTC16h 41m
2026-07-25 MFX223 - Jul 25, 16:05 UTCJul 25, 17:05 UTC1h 0m
2026-07-24 MFX223 - Jul 24, 16:50 UTCJul 25, 16:45 UTC23h 55m
2026-07-24 MFX3310 - Jul 24, 16:20 UTCJul 24, 17:15 UTC55m
2026-07-24 MFX3309 - Jul 24, 13:55 UTCJul 24, 15:10 UTC1h 15m
2026-07-23 MFX3308 - Jul 23, 12:20 UTCJul 23, 14:10 UTC1h 50m
2026-07-22 MFX3307 - Jul 22, 17:50 UTCJul 23, 10:10 UTC16h 20m
2026-07-22 MFX3309 - Jul 22, 14:55 UTCJul 22, 16:15 UTC1h 20m
2026-07-21 MFX3309 BUS → TZX Jul 21, 19:35 UTCJul 22, 16:15 UTC20h 40m
2026-07-21 MFX532 - Jul 21, 00:15 UTCJul 21, 17:50 UTC17h 35m
2026-07-18 MFX3362 - Jul 18, 14:50 UTCJul 19, 10:15 UTC19h 25m
2026-07-18 MFX3362 - Jul 18, 14:40 UTCJul 19, 10:15 UTC19h 35m
2026-07-18 MFX3362 - Jul 18, 10:55 UTCJul 19, 10:15 UTC23h 20m
2026-07-18 MFX3362 - Jul 18, 09:20 UTCJul 19, 08:30 UTC23h 10m
2026-07-17 MFX3361 - Jul 17, 16:49 UTCJul 18, 12:15 UTC19h 26m
2026-07-16 MFX529 - Jul 16, 21:10 UTCJul 17, 15:40 UTC18h 30m
2026-07-16 MFX529 - Jul 16, 12:49 UTCJul 17, 08:04 UTC19h 15m
2026-07-16 MFX529 - Jul 16, 12:34 UTCJul 17, 08:04 UTC19h 30m
2026-07-15 MFX3307 - Jul 15, 17:30 UTCJul 16, 10:04 UTC16h 35m
2026-07-15 MFX3309 - Jul 15, 14:45 UTCJul 15, 16:05 UTC1h 20m
2026-07-14 MFX3309 BUS → TZX Jul 14, 19:35 UTCJul 15, 16:05 UTC20h 29m
2026-07-13 MFX223 - Jul 13, 23:15 UTCJul 14, 18:15 UTC19h 0m
2026-07-11 MFX3362 - Jul 11, 16:15 UTCJul 12, 09:40 UTC17h 25m
2026-07-11 MFX3361 - Jul 11, 09:00 UTCJul 11, 15:45 UTC6h 45m
2026-07-10 MFX3361 - Jul 10, 10:50 UTCJul 11, 10:45 UTC23h 55m
2026-07-10 MFX3308 - Jul 10, 09:25 UTCJul 10, 11:10 UTC1h 45m
2026-07-09 MFX3307 - Jul 9, 12:50 UTCJul 10, 07:30 UTC18h 40m
2026-07-09 MFX3307 - Jul 9, 12:40 UTCJul 10, 07:30 UTC18h 50m
2026-07-08 MFX3307 - Jul 8, 16:15 UTCJul 9, 10:45 UTC18h 30m
2026-07-08 MFX3309 - Jul 8, 13:35 UTCJul 8, 14:50 UTC1h 15m
2026-07-07 MFX3309 - Jul 7, 18:50 UTCJul 8, 14:50 UTC20h 0m
2026-07-06 MFX531 - Jul 6, 23:25 UTCJul 7, 17:15 UTC17h 50m
2026-07-06 MFX531 - Jul 6, 11:40 UTCJul 7, 09:50 UTC22h 10m
2026-07-06 MFX221 - Jul 6, 09:15 UTCJul 6, 10:00 UTC45m
2026-07-04 MFX3362 - Jul 4, 14:50 UTCJul 5, 09:45 UTC18h 55m
2026-07-04 MFX3362 - Jul 4, 14:20 UTCJul 5, 09:45 UTC19h 25m
2026-07-04 MFX3361 - Jul 4, 09:00 UTCJul 4, 12:00 UTC3h 0m
2026-07-03 MFX3361 - Jul 3, 10:50 UTCJul 4, 10:45 UTC23h 55m
2026-07-03 MFX3308 - Jul 3, 09:20 UTCJul 3, 11:10 UTC1h 50m
2026-07-02 MFX3307 - Jul 2, 12:50 UTCJul 3, 07:20 UTC18h 30m
2026-07-02 MFX3307 - Jul 2, 12:25 UTCJul 3, 07:20 UTC18h 55m
2026-07-02 MFX3307 - Jul 2, 07:45 UTCJul 2, 10:15 UTC2h 30m
2026-07-01 MFX3307 - Jul 1, 11:35 UTCJul 2, 10:15 UTC22h 40m
2026-07-01 MFX3307 - Jul 1, 09:25 UTCJul 2, 08:45 UTC23h 20m
2026-06-30 MFX224 - Jun 30, 19:35 UTCJul 1, 07:25 UTC11h 50m
2026-06-29 MFX223 - Jun 29, 23:14 UTCJun 30, 17:50 UTC18h 36m
2026-06-29 MFX531 - Jun 29, 12:09 UTCJun 30, 10:15 UTC22h 5m
2026-06-29 MFX221 - Jun 29, 09:44 UTCJun 29, 10:20 UTC35m
2026-06-28 MFX3308 - Jun 28, 13:14 UTCJun 29, 10:20 UTC21h 5m
2026-06-28 MFX3308 - Jun 28, 12:25 UTCJun 28, 14:19 UTC1h 55m

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

Mode-S 507CC3 frequently asked

What is Mode-S code 507CC3?
507CC3 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK32133.
Where is Mode-S 507CC3 registered?
Mode-S code 507CC3 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CC3 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 11:45 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507CC3, octal 24076303, decimal 5,274,819.
What flights does 507CC3 operate?
Mode-S 507CC3 has broadcast 20 distinct callsigns, including MFX3307, MFX530, MFX531, MFX3308, MFX3362.