sensors Mode-S transponder

507CA9

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK32074 · AIRBUS A-320neo

Hex
507CA9
Octal
24076251
Decimal
5,274,793
Country
UZ
Tail
UK32074
Type
A20N
No current signal · last broadcast 2d ago
Flights observed
65
Distinct callsigns
19
Country
UZ
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 507CA9.

Country allocation

The ICAO 24-bit address 507CA9 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 19 distinct

Callsign Airline Flights Last seen
MFX152 - 11 2026-05-25
MFX456 - 8 2026-05-24
MFX151 - 7 2026-05-08
MFX461 - 6 2026-05-27
MFX462 - 4 2026-05-13
MFX3362 - 4 2026-04-28
MFX3361 - 4 2026-04-28
MFX373 - 3 2026-05-20
MFX315 My Freighter LLC 3 2026-04-21
MFX526 - 2 2026-05-12
MFX525 - 2 2026-05-11
MFX455 - 2 2026-05-24
MFX374 - 2 2026-05-20
MFX221 - 2 2026-05-04
MFX531 - 1 2026-04-26
MFX512 - 1 2026-05-23
MFX453 - 1 2026-05-18
MFX402 My Freighter LLC 1 2026-05-14
MFX316 My Freighter LLC 1 2026-04-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-27 MFX461 - May 27, 08:25 UTCMay 27, 16:25 UTC8h 0m
2026-05-25 MFX152 - May 25, 06:40 UTCMay 25, 08:40 UTC2h 0m
2026-05-24 MFX456 - May 24, 11:10 UTCMay 25, 04:30 UTC17h 20m
2026-05-24 MFX456 - May 24, 08:20 UTCMay 25, 04:30 UTC20h 10m
2026-05-24 MFX455 - May 24, 07:25 UTCMay 25, 04:30 UTC21h 5m
2026-05-23 MFX512 - May 23, 21:10 UTCMay 23, 21:25 UTC15m
2026-05-20 MFX374 - May 20, 06:15 UTCMay 20, 08:35 UTC2h 20m
2026-05-20 MFX373 - May 20, 01:05 UTCMay 20, 03:55 UTC2h 50m
2026-05-19 MFX373 - May 19, 05:45 UTCMay 20, 03:55 UTC22h 10m
2026-05-18 MFX453 - May 18, 18:25 UTCMay 19, 05:50 UTC11h 24m
2026-05-14 MFX402 SVO → TAS May 14, 06:10 UTCMay 14, 06:55 UTC45m
2026-05-13 MFX462 - May 13, 13:10 UTCMay 13, 16:10 UTC3h 0m
2026-05-13 MFX461 - May 13, 08:35 UTCMay 13, 11:00 UTC2h 25m
2026-05-12 MFX526 - May 12, 03:05 UTCMay 12, 07:35 UTC4h 30m
2026-05-11 MFX525 - May 11, 20:10 UTCMay 11, 22:35 UTC2h 24m
2026-05-08 MFX152 - May 8, 17:35 UTCMay 8, 19:50 UTC2h 15m
2026-05-08 MFX151 - May 8, 13:35 UTCMay 8, 15:25 UTC1h 50m
2026-05-06 MFX462 - May 6, 13:30 UTCMay 6, 16:35 UTC3h 5m
2026-05-06 MFX461 - May 6, 08:55 UTCMay 6, 10:10 UTC1h 15m
2026-05-05 MFX526 - May 5, 02:50 UTCMay 5, 07:30 UTC4h 40m
2026-05-04 MFX525 - May 4, 12:30 UTCMay 5, 00:30 UTC12h 1m
2026-05-04 MFX221 - May 4, 09:15 UTCMay 4, 09:45 UTC30m
2026-05-03 MFX221 - May 3, 10:20 UTCMay 4, 09:45 UTC23h 25m
2026-05-03 MFX374 - May 3, 08:15 UTCMay 3, 10:35 UTC2h 20m
2026-05-03 MFX373 - May 3, 04:05 UTCMay 3, 07:00 UTC2h 55m
2026-05-01 MFX152 - May 1, 17:15 UTCMay 1, 19:35 UTC2h 20m
2026-05-01 MFX151 - May 1, 14:35 UTCMay 1, 15:05 UTC30m
2026-04-29 MFX462 - Apr 29, 13:10 UTCApr 29, 16:00 UTC2h 50m
2026-04-28 MFX461 - Apr 28, 16:20 UTCApr 29, 11:20 UTC19h 0m
2026-04-28 MFX461 - Apr 28, 14:20 UTCApr 29, 11:20 UTC21h 0m
2026-04-28 MFX3362 - Apr 28, 13:40 UTCApr 29, 11:20 UTC21h 40m
2026-04-28 MFX3362 - Apr 28, 10:55 UTCApr 29, 09:55 UTC23h 0m
2026-04-28 MFX3361 - Apr 28, 08:40 UTCApr 28, 16:30 UTC7h 50m
2026-04-26 MFX531 - Apr 26, 00:40 UTCApr 26, 07:40 UTC7h 0m
2026-04-24 MFX152 - Apr 24, 17:10 UTCApr 24, 19:30 UTC2h 20m
2026-04-24 MFX151 - Apr 24, 13:00 UTCApr 24, 14:45 UTC1h 45m
2026-04-22 MFX462 - Apr 22, 13:10 UTCApr 22, 16:25 UTC3h 15m
2026-04-22 MFX461 - Apr 22, 08:25 UTCApr 22, 10:55 UTC2h 30m
2026-04-21 MFX316 IST → FEG Apr 21, 07:30 UTCApr 21, 09:35 UTC2h 5m
2026-04-21 MFX315 FEG → IST Apr 21, 03:15 UTCApr 21, 04:35 UTC1h 20m
2026-04-20 MFX315 FEG → IST Apr 20, 08:20 UTCApr 21, 04:35 UTC20h 15m
2026-04-20 MFX152 - Apr 20, 06:25 UTCApr 21, 04:35 UTC22h 11m
2026-04-19 MFX456 - Apr 19, 11:05 UTCApr 20, 04:20 UTC17h 15m
2026-04-19 MFX456 - Apr 19, 08:20 UTCApr 20, 04:20 UTC20h 0m
2026-04-19 MFX456 - Apr 19, 07:10 UTCApr 20, 04:20 UTC21h 10m
2026-04-18 MFX456 - Apr 18, 15:05 UTCApr 19, 12:45 UTC21h 40m
2026-04-18 MFX315 FEG → IST Apr 18, 09:05 UTCApr 18, 09:20 UTC15m
2026-04-17 MFX152 - Apr 17, 19:25 UTCApr 17, 20:20 UTC55m
2026-04-17 MFX152 - Apr 17, 17:25 UTCApr 17, 19:20 UTC1h 55m
2026-04-17 MFX152 - Apr 17, 17:10 UTCApr 18, 10:20 UTC17h 11m

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

Mode-S 507CA9 frequently asked

What is Mode-S code 507CA9?
507CA9 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK32074.
Where is Mode-S 507CA9 registered?
Mode-S code 507CA9 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CA9 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507CA9, octal 24076251, decimal 5,274,793.
What flights does 507CA9 operate?
Mode-S 507CA9 has broadcast 19 distinct callsigns, including MFX152, MFX456, MFX151, MFX461, MFX462.