sensors Mode-S transponder

507CA5

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK67019 · BOEING 767-300

Hex
507CA5
Octal
24076245
Decimal
5,274,789
Country
UZ
Tail
UK67019
Type
B763
Broadcasting now · callsign MFX7670 · 35,000 ft
Flights observed
104
Distinct callsigns
20
Country
UZ
Last broadcast
1h ago

Current position

507CA5 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 507CA5 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
MFX7561 - 6 2026-07-09
MFX7461 - 5 2026-07-07
MFX7618 - 4 2026-07-05
MFX7617 - 4 2026-07-05
MFX7462 - 4 2026-07-07
MFX7678 - 3 2026-06-27
MFX7670 My Freighter LLC 3 2026-07-18
MFX7663 - 3 2026-06-13
MFX7562 - 3 2026-07-09
MFX7507 - 3 2026-07-15
MFX7672 - 2 2026-07-03
MFX7671 - 2 2026-07-03
MFX7664 - 2 2026-06-13
MFX7632 - 2 2026-07-05
MFX7631 - 2 2026-05-24
MFX7626 - 2 2026-06-06
MFX7624 - 2 2026-06-19
MFX7564 - 2 2026-06-26
MFX7508 - 2 2026-07-16
MFX7486 - 2 2026-06-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 MFX7670 LGG → LGG Jul 18, 08:45 UTCJul 18, 09:15 UTC30m
2026-07-17 MFX7464 - Jul 17, 15:10 UTCJul 17, 17:05 UTC1h 55m
2026-07-17 MFX7463 - Jul 17, 08:54 UTCJul 17, 12:15 UTC3h 20m
2026-07-16 MFX7508 - Jul 16, 02:50 UTCJul 16, 05:45 UTC2h 55m
2026-07-15 MFX7507 - Jul 15, 20:50 UTCJul 15, 23:50 UTC3h 0m
2026-07-14 MFX678 - Jul 14, 01:15 UTCJul 14, 03:25 UTC2h 10m
2026-07-13 MFX677 - Jul 13, 19:40 UTCJul 13, 22:25 UTC2h 45m
2026-07-12 MFX7510 - Jul 12, 13:25 UTCJul 12, 16:15 UTC2h 50m
2026-07-12 MFX7509 - Jul 12, 07:40 UTCJul 12, 10:35 UTC2h 55m
2026-07-09 MFX7562 - Jul 9, 14:30 UTCJul 9, 15:05 UTC35m
2026-07-09 MFX7561 - Jul 9, 09:50 UTCJul 9, 09:55 UTC5m
2026-07-07 MFX7670 - Jul 7, 22:45 UTCJul 8, 00:50 UTC2h 5m
2026-07-07 MFX7462 - Jul 7, 17:20 UTCJul 7, 19:25 UTC2h 5m
2026-07-07 MFX7461 - Jul 7, 11:50 UTCJul 7, 15:10 UTC3h 20m
2026-07-05 MFX7618 - Jul 5, 20:55 UTCJul 5, 22:55 UTC2h 0m
2026-07-05 MFX7617 - Jul 5, 18:30 UTCJul 5, 19:15 UTC45m
2026-07-05 MFX7632 - Jul 5, 03:25 UTCJul 5, 03:40 UTC15m
2026-07-04 MFX7602 - Jul 4, 21:20 UTCJul 5, 00:30 UTC3h 10m
2026-07-03 MFX7672 - Jul 3, 19:25 UTCJul 3, 22:45 UTC3h 20m
2026-07-03 MFX7671 - Jul 3, 11:40 UTCJul 3, 15:20 UTC3h 40m
2026-07-01 MFX7508 - Jul 1, 15:55 UTCJul 1, 16:25 UTC30m
2026-07-01 MFX7507 - Jul 1, 12:25 UTCJul 1, 12:55 UTC30m
2026-07-01 MFX7507 - Jul 1, 10:30 UTCJul 1, 10:40 UTC10m
2026-06-30 MFX7680 - Jun 30, 07:40 UTCJun 30, 11:05 UTC3h 25m
2026-06-29 MFX7679 - Jun 29, 23:54 UTCJun 30, 03:30 UTC3h 36m
2026-06-27 MFX7678 - Jun 27, 17:20 UTCJun 27, 20:44 UTC3h 25m
2026-06-27 MFX7466 - Jun 27, 13:30 UTCJun 27, 14:25 UTC55m
2026-06-27 MFX7465 - Jun 27, 07:55 UTCJun 27, 11:09 UTC3h 15m
2026-06-26 MFX7564 - Jun 26, 07:20 UTCJun 26, 09:05 UTC1h 45m
2026-06-24 MFX674 - Jun 24, 21:44 UTCJun 24, 23:54 UTC2h 10m
2026-06-24 MFX673 - Jun 24, 16:09 UTCJun 24, 18:50 UTC2h 40m
2026-06-19 MFX7624 - Jun 19, 21:14 UTCJun 19, 22:45 UTC1h 30m
2026-06-19 MFX7462 DUB → DUB Jun 19, 14:29 UTCJun 19, 15:59 UTC1h 30m
2026-06-19 MFX7461 - Jun 19, 08:29 UTCJun 19, 11:49 UTC3h 20m
2026-06-18 MFX7461 - Jun 18, 10:30 UTCJun 19, 09:14 UTC22h 44m
2026-06-17 MFX7678 - Jun 17, 19:55 UTCJun 18, 08:00 UTC12h 5m
2026-06-17 MFX7446 - Jun 17, 15:00 UTCJun 17, 16:45 UTC1h 45m
2026-06-17 MFX7445 - Jun 17, 07:55 UTCJun 17, 12:45 UTC4h 50m
2026-06-16 MFX7434 MRA → LGG Jun 16, 01:04 UTCJun 16, 03:20 UTC2h 15m
2026-06-15 MFX7433 - Jun 15, 06:20 UTCJun 15, 10:55 UTC4h 35m
2026-06-14 MFX7532 - Jun 14, 10:20 UTCJun 15, 06:40 UTC20h 19m
2026-06-13 MFX7664 - Jun 13, 15:20 UTCJun 14, 08:05 UTC16h 45m
2026-06-13 MFX7663 - Jun 13, 08:40 UTCJun 13, 12:55 UTC4h 15m
2026-06-12 MFX7663 - Jun 12, 09:20 UTCJun 13, 09:15 UTC23h 54m
2026-06-12 MFX7536 - Jun 12, 09:05 UTCJun 12, 09:45 UTC40m
2026-06-11 MFX7535 TLL → DEL Jun 11, 15:05 UTCJun 12, 06:05 UTC15h 0m
2026-06-11 MFX7561 - Jun 11, 11:50 UTCJun 11, 11:55 UTC5m
2026-06-11 MFX7561 - Jun 11, 09:30 UTCJun 11, 10:15 UTC45m
2026-06-10 MFX7564 - Jun 10, 02:10 UTCJun 10, 03:25 UTC1h 15m
2026-06-06 MFX7626 - Jun 6, 16:39 UTCJun 6, 20:00 UTC3h 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.

Prefer a tail-number view? See the UK67019 page for operator, model, and routing details .

Mode-S 507CA5 frequently asked

What is Mode-S code 507CA5?
507CA5 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK67019.
Where is Mode-S 507CA5 registered?
Mode-S code 507CA5 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CA5 broadcasting right now?
Yes. Mode-S 507CA5 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507CA5, octal 24076245, decimal 5,274,789.
What flights does 507CA5 operate?
Mode-S 507CA5 has broadcast 20 distinct callsigns, including MFX7561, MFX7461, MFX7618, MFX7617, MFX7462.