sensors Mode-S transponder

507CC1

ICAO 24-bit transponder address · allocated to Uzbekistan

Hex
507CC1
Octal
24076301
Decimal
5,274,817
Country
UZ
No current signal · last broadcast 11h ago
Flights observed
54
Distinct callsigns
20
Country
UZ
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S 507CC1.

Country allocation

The ICAO 24-bit address 507CC1 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
MFX445 - 7 2026-06-26
MFX446 - 5 2026-06-22
MFX449 - 4 2026-05-17
MFX417 My Freighter LLC 4 2026-06-18
MFX404 My Freighter LLC 4 2026-06-21
MFX430 My Freighter LLC 3 2026-07-04
MFX352 - 3 2026-06-23
MFX351 - 3 2026-06-23
MFX457 - 2 2026-06-08
MFX456 - 2 2026-06-11
MFX429 - 2 2026-07-04
MFX418 - 2 2026-06-30
MFX374 - 2 2026-06-10
MFX373 - 2 2026-06-10
MFX3361 - 2 2026-05-18
MFX315 - 2 2026-06-20
MFX422 - 1 2026-05-17
MFX410 My Freighter LLC 1 2026-06-10
MFX403 My Freighter LLC 1 2026-05-29
MFX3362 - 1 2026-05-19

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-04 MFX430 LED → UGC Jul 4, 13:00 UTCJul 4, 13:20 UTC20m
2026-07-04 MFX429 - Jul 4, 10:10 UTCJul 4, 10:20 UTC10m
2026-06-30 MFX418 - Jun 30, 13:30 UTCJun 30, 13:40 UTC10m
2026-06-26 MFX430 LED → UGC Jun 26, 20:20 UTCJun 27, 14:54 UTC18h 35m
2026-06-26 MFX445 - Jun 26, 16:35 UTCJun 27, 14:54 UTC22h 20m
2026-06-24 MFX430 LED → UGC Jun 24, 14:04 UTCJun 24, 14:15 UTC10m
2026-06-23 MFX352 - Jun 23, 09:20 UTCJun 23, 11:29 UTC2h 10m
2026-06-23 MFX351 - Jun 23, 06:59 UTCJun 23, 07:15 UTC15m
2026-06-22 MFX446 - Jun 22, 11:04 UTCJun 23, 04:55 UTC17h 50m
2026-06-22 MFX445 - Jun 22, 07:40 UTCJun 23, 04:55 UTC21h 15m
2026-06-21 MFX404 SVO → TAS Jun 21, 17:39 UTCJun 22, 11:24 UTC17h 45m
2026-06-21 MFX404 SVO → TAS Jun 21, 11:24 UTCJun 22, 08:00 UTC20h 35m
2026-06-21 MFX352 - Jun 21, 09:10 UTCJun 21, 09:35 UTC25m
2026-06-20 MFX316 IST → FEG Jun 20, 13:59 UTCJun 21, 04:39 UTC14h 40m
2026-06-20 MFX315 - Jun 20, 11:09 UTCJun 20, 11:40 UTC30m
2026-06-20 MFX315 - Jun 20, 09:05 UTCJun 20, 10:34 UTC1h 30m
2026-06-18 MFX417 UGC → DME Jun 18, 09:35 UTCJun 18, 10:15 UTC40m
2026-06-18 MFX417 UGC → DME Jun 18, 06:45 UTCJun 18, 07:45 UTC1h 0m
2026-06-16 MFX404 SVO → TAS Jun 16, 22:00 UTCJun 16, 22:10 UTC10m
2026-06-14 MFX418 DME → UGC Jun 14, 10:05 UTCJun 14, 10:35 UTC30m
2026-06-14 MFX417 UGC → DME Jun 14, 06:10 UTCJun 14, 06:30 UTC20m
2026-06-12 MFX446 - Jun 12, 18:30 UTCJun 12, 19:25 UTC55m
2026-06-12 MFX445 - Jun 12, 15:00 UTCJun 12, 15:25 UTC25m
2026-06-11 MFX456 - Jun 11, 07:55 UTCJun 11, 14:30 UTC6h 35m
2026-06-10 MFX456 - Jun 10, 19:20 UTCJun 11, 14:30 UTC19h 10m
2026-06-10 MFX410 DME → SKD Jun 10, 18:35 UTCJun 10, 18:45 UTC10m
2026-06-10 MFX374 - Jun 10, 06:15 UTCJun 10, 08:35 UTC2h 20m
2026-06-10 MFX373 - Jun 10, 01:25 UTCJun 10, 04:10 UTC2h 45m
2026-06-08 MFX457 - Jun 8, 07:30 UTCJun 8, 20:20 UTC12h 50m
2026-06-07 MFX374 - Jun 7, 09:55 UTCJun 7, 12:15 UTC2h 20m
2026-06-06 MFX373 - Jun 6, 14:54 UTCJun 7, 08:10 UTC17h 15m
2026-06-06 MFX429 UGC → LED Jun 6, 10:50 UTCJun 6, 11:05 UTC15m
2026-06-05 MFX446 - Jun 5, 15:05 UTCJun 6, 09:15 UTC18h 10m
2026-06-02 MFX351 TAS → DXB Jun 2, 04:35 UTCJun 2, 11:35 UTC7h 0m
2026-06-01 MFX446 - Jun 1, 10:55 UTCJun 2, 04:40 UTC17h 45m
2026-06-01 MFX445 - Jun 1, 07:30 UTCJun 2, 04:40 UTC21h 10m
2026-06-01 MFX445 - Jun 1, 01:40 UTCJun 1, 11:20 UTC9h 40m
2026-05-31 MFX445 - May 31, 10:25 UTCJun 1, 08:00 UTC21h 35m
2026-05-30 MFX352 DXB → TAS May 30, 09:35 UTCMay 30, 09:50 UTC15m
2026-05-29 MFX404 SVO → TAS May 29, 21:05 UTCMay 30, 04:40 UTC7h 35m
2026-05-29 MFX403 TAS → SVO May 29, 18:10 UTCMay 29, 18:40 UTC30m
2026-05-28 MFX351 TAS → DXB May 28, 04:30 UTCMay 28, 11:25 UTC6h 55m
2026-05-22 MFX446 - May 22, 18:35 UTCMay 22, 19:00 UTC25m
2026-05-21 MFX417 UGC → DME May 21, 06:15 UTCMay 21, 06:30 UTC15m
2026-05-19 MFX3362 - May 19, 20:00 UTCMay 19, 22:50 UTC2h 50m
2026-05-18 MFX3361 - May 18, 23:25 UTCMay 19, 17:50 UTC18h 25m
2026-05-18 MFX3361 - May 18, 20:20 UTCMay 19, 17:50 UTC21h 30m
2026-05-18 MFX457 - May 18, 17:45 UTCMay 18, 18:20 UTC35m
2026-05-17 MFX449 - May 17, 22:20 UTCMay 18, 17:05 UTC18h 45m
2026-05-17 MFX449 - May 17, 11:30 UTCMay 18, 07:50 UTC20h 20m

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.

Mode-S 507CC1 frequently asked

What is Mode-S code 507CC1?
507CC1 is an ICAO 24-bit transponder address. Allocated to Uzbekistan.
Where is Mode-S 507CC1 registered?
Mode-S code 507CC1 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CC1 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 507CC1, octal 24076301, decimal 5,274,817.
What flights does 507CC1 operate?
Mode-S 507CC1 has broadcast 20 distinct callsigns, including MFX445, MFX446, MFX449, MFX417, MFX404.