Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

507CAA

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK32075 · AIRBUS A-320neo

Hex
507CAA
Octal
24076252
Decimal
5,274,794
Country
UZ
Tail
UK32075
Type
A20N
No current signal · last broadcast 2d ago
Flights observed
110
Distinct callsigns
20
Country
UZ
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 507CAA.

Country allocation

The ICAO 24-bit address 507CAA 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
MFX152 - 13 2026-07-06
MFX151 - 12 2026-07-03
MFX3362 - 11 2026-06-24
MFX453 - 9 2026-07-13
MFX558 - 8 2026-07-16
MFX3361 - 8 2026-06-24
MFX456 - 6 2026-07-05
MFX525 - 5 2026-05-18
MFX315 - 5 2026-07-11
MFX3140 - 5 2026-05-16
MFX557 - 3 2026-07-16
MFX531 - 3 2026-06-13
MFX526 - 3 2026-05-19
MFX374 - 3 2026-05-31
MFX3141 - 3 2026-05-16
MFX461 - 2 2026-06-03
MFX550 - 1 2026-05-08
MFX549 - 1 2026-05-08
MFX529 - 1 2026-06-18
MFX457 - 1 2026-06-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-16 MFX558 - Jul 16, 07:20 UTCJul 16, 08:00 UTC40m
2026-07-16 MFX557 - Jul 16, 03:30 UTCJul 16, 04:20 UTC50m
2026-07-13 MFX453 - Jul 13, 21:55 UTCJul 13, 22:40 UTC45m
2026-07-13 MFX453 - Jul 13, 20:40 UTCJul 13, 20:55 UTC15m
2026-07-12 MFX226 - Jul 12, 04:30 UTCJul 12, 05:20 UTC50m
2026-07-11 MFX225 - Jul 11, 14:00 UTCJul 12, 02:45 UTC12h 45m
2026-07-11 MFX315 - Jul 11, 11:15 UTCJul 11, 11:40 UTC25m
2026-07-11 MFX315 - Jul 11, 09:10 UTCJul 11, 10:35 UTC1h 25m
2026-07-10 MFX315 - Jul 10, 11:30 UTCJul 11, 10:30 UTC23h 0m
2026-07-10 MFX352 - Jul 10, 09:25 UTCJul 10, 11:35 UTC2h 10m
2026-07-09 MFX558 - Jul 9, 07:05 UTCJul 10, 04:35 UTC21h 30m
2026-07-09 MFX557 - Jul 9, 03:40 UTCJul 9, 04:25 UTC45m
2026-07-06 MFX152 - Jul 6, 06:55 UTCJul 6, 08:50 UTC1h 55m
2026-07-05 MFX456 - Jul 5, 08:40 UTCJul 6, 04:20 UTC19h 40m
2026-07-05 MFX456 - Jul 5, 08:00 UTCJul 6, 04:20 UTC20h 20m
2026-07-03 MFX152 - Jul 3, 17:40 UTCJul 3, 19:35 UTC1h 55m
2026-07-03 MFX151 - Jul 3, 14:00 UTCJul 3, 15:15 UTC1h 15m
2026-06-30 MFX558 - Jun 30, 07:05 UTCJun 30, 07:45 UTC40m
2026-06-29 MFX152 - Jun 29, 08:35 UTCJun 30, 04:25 UTC19h 51m
2026-06-29 MFX152 FRA → DEL Jun 29, 07:20 UTCJun 30, 04:25 UTC21h 6m
2026-06-28 MFX456 - Jun 28, 11:09 UTCJun 29, 04:55 UTC17h 45m
2026-06-28 MFX456 - Jun 28, 08:34 UTCJun 29, 04:55 UTC20h 20m
2026-06-28 MFX456 - Jun 28, 07:25 UTCJun 29, 04:55 UTC21h 30m
2026-06-27 MFX558 - Jun 27, 07:10 UTCJun 27, 07:49 UTC40m
2026-06-26 MFX152 FRA → DEL Jun 26, 18:15 UTCJun 27, 04:44 UTC10h 30m
2026-06-26 MFX151 - Jun 26, 13:45 UTCJun 26, 14:55 UTC1h 10m
2026-06-25 MFX558 - Jun 25, 07:15 UTCJun 25, 07:54 UTC40m
2026-06-24 MFX3362 - Jun 24, 15:35 UTCJun 25, 04:45 UTC13h 10m
2026-06-24 MFX3361 - Jun 24, 03:24 UTCJun 24, 13:34 UTC10h 10m
2026-06-23 MFX3362 - Jun 23, 09:59 UTCJun 24, 02:05 UTC16h 5m
2026-06-22 MFX152 - Jun 22, 06:49 UTCJun 22, 08:50 UTC2h 0m
2026-06-22 MFX151 - Jun 22, 03:45 UTCJun 22, 04:34 UTC50m
2026-06-20 MFX453 - Jun 20, 00:14 UTCJun 20, 01:05 UTC50m
2026-06-19 MFX453 - Jun 19, 20:29 UTCJun 19, 20:44 UTC15m
2026-06-18 MFX529 - Jun 18, 21:40 UTCJun 19, 08:09 UTC10h 29m
2026-06-17 MFX3361 - Jun 17, 10:35 UTCJun 17, 18:30 UTC7h 55m
2026-06-16 MFX558 - Jun 16, 06:59 UTCJun 16, 07:34 UTC35m
2026-06-15 MFX152 FRA → DEL Jun 15, 09:49 UTCJun 16, 04:30 UTC18h 40m
2026-06-15 MFX151 BER → FRA Jun 15, 07:05 UTCJun 15, 07:50 UTC45m
2026-06-15 MFX151 - Jun 15, 04:20 UTCJun 15, 04:45 UTC25m
2026-06-13 MFX531 - Jun 13, 22:50 UTCJun 14, 09:50 UTC11h 0m
2026-06-12 MFX453 - Jun 12, 18:30 UTCJun 12, 19:10 UTC40m
2026-06-11 MFX453 - Jun 11, 20:35 UTCJun 12, 19:10 UTC22h 35m
2026-06-11 MFX457 - Jun 11, 16:50 UTCJun 11, 20:40 UTC3h 50m
2026-06-08 MFX3361 - Jun 8, 23:35 UTCJun 9, 17:50 UTC18h 15m
2026-06-08 MFX3361 - Jun 8, 18:40 UTCJun 9, 17:50 UTC23h 10m
2026-06-06 MFX3362 - Jun 6, 14:34 UTCJun 7, 10:20 UTC19h 45m
2026-06-06 MFX3362 - Jun 6, 13:54 UTCJun 7, 10:20 UTC20h 25m
2026-06-06 MFX3362 - Jun 6, 10:45 UTCJun 7, 10:20 UTC23h 35m
2026-06-06 MFX3361 - Jun 6, 08:50 UTCJun 7, 08:25 UTC23h 35m

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

Mode-S 507CAA frequently asked

What is Mode-S code 507CAA?
507CAA is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK32075.
Where is Mode-S 507CAA registered?
Mode-S code 507CAA is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CAA 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 507CAA, octal 24076252, decimal 5,274,794.
What flights does 507CAA operate?
Mode-S 507CAA has broadcast 20 distinct callsigns, including MFX152, MFX151, MFX3362, MFX453, MFX558.