sensors Mode-S transponder

507CB1

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK67020 · BOEING 767-300

Hex
507CB1
Octal
24076261
Decimal
5,274,801
Country
UZ
Tail
UK67020
Type
B763
No current signal · last broadcast 7h ago
Flights observed
145
Distinct callsigns
20
Country
UZ
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S 507CB1.

Country allocation

The ICAO 24-bit address 507CB1 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
MFX675 - 10 2026-07-17
MFX676 My Freighter LLC 9 2026-07-17
MFX7486 - 6 2026-06-22
MFX7485 - 5 2026-06-22
MFX7463 - 5 2026-07-10
MFX7619 - 4 2026-06-07
MFX7563 - 4 2026-05-31
MFX678 - 4 2026-06-30
MFX677 - 4 2026-06-29
MFX672 - 4 2026-07-04
MFX671 - 4 2026-07-04
MFX7686 - 3 2026-06-23
MFX7678 - 3 2026-07-11
MFX7622 - 3 2026-06-16
MFX7620 - 3 2026-06-08
MFX7564 - 3 2026-05-31
MFX7482 - 3 2026-06-16
MFX7481 - 3 2026-06-16
MFX7464 - 3 2026-07-11
MFX7461 - 3 2026-06-03

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 MFX676 TLV → DWC Jul 17, 15:44 UTCJul 17, 19:05 UTC3h 20m
2026-07-17 MFX675 - Jul 17, 09:25 UTCJul 17, 12:10 UTC2h 45m
2026-07-15 MFX7506 - Jul 15, 12:40 UTCJul 15, 15:25 UTC2h 45m
2026-07-15 MFX7505 - Jul 15, 06:45 UTCJul 15, 09:35 UTC2h 50m
2026-07-13 MFX7502 - Jul 13, 14:55 UTCJul 13, 16:05 UTC1h 10m
2026-07-13 MFX7501 - Jul 13, 09:10 UTCJul 13, 12:00 UTC2h 50m
2026-07-11 MFX7678 - Jul 11, 07:35 UTCJul 11, 10:50 UTC3h 15m
2026-07-11 MFX7464 - Jul 11, 03:25 UTCJul 11, 04:30 UTC1h 5m
2026-07-10 MFX7463 - Jul 10, 22:05 UTCJul 11, 01:25 UTC3h 20m
2026-07-06 MFX676 - Jul 6, 18:30 UTCJul 6, 20:40 UTC2h 10m
2026-07-06 MFX675 - Jul 6, 13:05 UTCJul 6, 15:50 UTC2h 45m
2026-07-04 MFX7502 - Jul 4, 21:45 UTCJul 4, 22:15 UTC30m
2026-07-04 MFX672 - Jul 4, 15:30 UTCJul 4, 18:20 UTC2h 50m
2026-07-04 MFX671 - Jul 4, 10:25 UTCJul 4, 13:10 UTC2h 45m
2026-07-03 MFX7668 - Jul 3, 05:20 UTCJul 3, 07:20 UTC2h 0m
2026-07-02 MFX7464 - Jul 2, 22:00 UTCJul 3, 00:05 UTC2h 5m
2026-07-02 MFX7463 - Jul 2, 16:05 UTCJul 2, 19:20 UTC3h 15m
2026-07-01 MFX7562 - Jul 1, 12:20 UTCJul 1, 12:55 UTC35m
2026-07-01 MFX7561 - Jul 1, 06:50 UTCJul 1, 07:00 UTC10m
2026-06-30 MFX678 - Jun 30, 00:55 UTCJun 30, 03:10 UTC2h 16m
2026-06-29 MFX677 - Jun 29, 19:09 UTCJun 29, 21:54 UTC2h 45m
2026-06-28 MFX7566 - Jun 28, 06:15 UTCJun 28, 06:55 UTC40m
2026-06-28 MFX7565 - Jun 28, 03:29 UTCJun 28, 03:50 UTC20m
2026-06-28 MFX7565 - Jun 28, 01:55 UTCJun 28, 02:44 UTC50m
2026-06-26 MFX7530 - Jun 26, 11:09 UTCJun 26, 11:45 UTC35m
2026-06-25 MFX676 TLV → DEL Jun 25, 18:55 UTCJun 26, 08:40 UTC13h 45m
2026-06-25 MFX675 - Jun 25, 13:40 UTCJun 25, 16:29 UTC2h 50m
2026-06-24 MFX7526 - Jun 24, 13:34 UTCJun 24, 14:09 UTC35m
2026-06-23 MFX7686 BUD → DEL Jun 23, 20:19 UTCJun 24, 10:19 UTC14h 0m
2026-06-23 MFX7685 - Jun 23, 14:35 UTCJun 23, 17:59 UTC3h 25m
2026-06-22 MFX7685 - Jun 22, 18:19 UTCJun 23, 17:59 UTC23h 40m
2026-06-22 MFX7486 - Jun 22, 16:20 UTCJun 23, 15:55 UTC23h 35m
2026-06-22 MFX7486 - Jun 22, 14:59 UTCJun 22, 19:19 UTC4h 20m
2026-06-22 MFX7485 - Jun 22, 08:44 UTCJun 22, 13:19 UTC4h 35m
2026-06-20 MFX7682 - Jun 20, 23:29 UTCJun 21, 02:35 UTC3h 5m
2026-06-20 MFX7681 - Jun 20, 15:34 UTCJun 20, 19:04 UTC3h 30m
2026-06-19 MFX7484 - Jun 19, 18:20 UTCJun 20, 18:14 UTC23h 55m
2026-06-19 MFX7484 - Jun 19, 17:29 UTCJun 19, 21:54 UTC4h 25m
2026-06-19 MFX7483 - Jun 19, 09:14 UTCJun 19, 13:44 UTC4h 30m
2026-06-18 MFX676 TLV → DWC Jun 18, 03:25 UTCJun 18, 05:40 UTC2h 15m
2026-06-17 MFX675 - Jun 17, 22:05 UTCJun 18, 00:45 UTC2h 40m
2026-06-16 MFX7622 - Jun 16, 13:19 UTCJun 16, 14:55 UTC1h 35m
2026-06-16 MFX7482 - Jun 16, 09:25 UTCJun 16, 10:20 UTC55m
2026-06-16 MFX7481 - Jun 16, 02:15 UTCJun 16, 06:59 UTC4h 45m
2026-06-14 MFX676 TLV → DWC Jun 14, 18:45 UTCJun 14, 21:10 UTC2h 25m
2026-06-14 MFX675 - Jun 14, 13:15 UTCJun 14, 15:55 UTC2h 40m
2026-06-13 MFX7530 - Jun 13, 06:45 UTCJun 13, 07:30 UTC45m
2026-06-12 MFX672 TLV → DEL Jun 12, 15:10 UTCJun 13, 04:15 UTC13h 4m
2026-06-12 MFX671 - Jun 12, 09:55 UTCJun 12, 12:35 UTC2h 40m
2026-06-11 MFX7528 - Jun 11, 08:50 UTCJun 11, 09:35 UTC45m

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

Mode-S 507CB1 frequently asked

What is Mode-S code 507CB1?
507CB1 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK67020.
Where is Mode-S 507CB1 registered?
Mode-S code 507CB1 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507CB1 broadcasting right now?
No active broadcast right now. Last signal was 7h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507CB1, octal 24076261, decimal 5,274,801.
What flights does 507CB1 operate?
Mode-S 507CB1 has broadcast 20 distinct callsigns, including MFX675, MFX676, MFX7486, MFX7485, MFX7463.