sensors Mode-S transponder

507CB2

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK67021 · BOEING 767-300

Hex
507CB2
Octal
24076262
Decimal
5,274,802
Country
UZ
Tail
UK67021
Type
B763
No current signal · last broadcast 1d ago
Flights observed
115
Distinct callsigns
20
Country
UZ
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 507CB2.

Country allocation

The ICAO 24-bit address 507CB2 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
MFX672 - 7 2026-07-10
MFX671 - 6 2026-07-10
MFX7484 - 5 2026-05-26
MFX676 - 5 2026-07-13
MFX675 - 4 2026-07-12
MFX7622 - 3 2026-05-26
MFX7566 - 3 2026-06-14
MFX7483 - 3 2026-05-26
MFX7463 - 3 2026-06-11
MFX7680 - 2 2026-06-03
MFX7679 - 2 2026-06-03
MFX7678 - 2 2026-04-16
MFX7676 - 2 2026-05-24
MFX7674 - 2 2026-07-08
MFX7662 My Freighter LLC 2 2026-06-21
MFX7661 - 2 2026-06-21
MFX7634 - 2 2026-06-25
MFX7633 - 2 2026-06-25
MFX7631 - 2 2026-06-04
MFX7618 - 2 2026-06-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 MFX676 - Jul 13, 00:50 UTCJul 13, 03:01 UTC2h 10m
2026-07-12 MFX675 - Jul 12, 19:25 UTCJul 12, 22:00 UTC2h 35m
2026-07-10 MFX672 - Jul 10, 15:20 UTCJul 10, 17:25 UTC2h 5m
2026-07-10 MFX671 - Jul 10, 09:45 UTCJul 10, 12:40 UTC2h 55m
2026-07-08 MFX7674 - Jul 8, 22:20 UTCJul 8, 23:50 UTC1h 30m
2026-07-08 MFX674 - Jul 8, 14:15 UTCJul 8, 17:45 UTC3h 30m
2026-07-08 MFX673 - Jul 8, 08:10 UTCJul 8, 11:05 UTC2h 55m
2026-06-30 MFX7506 - Jun 30, 01:35 UTCJun 30, 02:05 UTC30m
2026-06-29 MFX7505 - Jun 29, 02:35 UTCJun 29, 22:15 UTC19h 40m
2026-06-29 MFX676 - Jun 29, 00:34 UTCJun 29, 22:15 UTC21h 40m
2026-06-29 MFX676 TLV → DWC Jun 29, 00:24 UTCJun 29, 22:15 UTC21h 50m
2026-06-28 MFX675 - Jun 28, 19:34 UTCJun 28, 22:20 UTC2h 45m
2026-06-27 MFX7446 - Jun 27, 02:35 UTCJun 27, 05:59 UTC3h 25m
2026-06-26 MFX672 - Jun 26, 23:15 UTCJun 26, 23:55 UTC40m
2026-06-26 MFX671 - Jun 26, 18:24 UTCJun 26, 21:04 UTC2h 40m
2026-06-25 MFX7634 - Jun 25, 19:54 UTCJun 26, 18:29 UTC22h 35m
2026-06-25 MFX7633 - Jun 25, 15:34 UTCJun 25, 15:59 UTC25m
2026-06-24 MFX7672 - Jun 24, 23:29 UTCJun 25, 02:49 UTC3h 20m
2026-06-24 MFX7462 DUB → DUB Jun 24, 10:04 UTCJun 24, 11:05 UTC1h 0m
2026-06-24 MFX7461 - Jun 24, 04:20 UTCJun 24, 07:34 UTC3h 15m
2026-06-22 MFX7684 - Jun 22, 17:50 UTCJun 22, 21:00 UTC3h 10m
2026-06-22 MFX7683 - Jun 22, 11:30 UTCJun 22, 14:45 UTC3h 15m
2026-06-21 MFX7662 LCA → TAS Jun 21, 06:50 UTCJun 21, 08:49 UTC2h 0m
2026-06-21 MFX7661 - Jun 21, 00:29 UTCJun 21, 02:50 UTC2h 20m
2026-06-20 MFX7661 - Jun 20, 02:35 UTCJun 21, 02:30 UTC23h 55m
2026-06-20 MFX672 - Jun 20, 01:55 UTCJun 20, 04:04 UTC2h 10m
2026-06-19 MFX671 - Jun 19, 20:14 UTCJun 19, 23:04 UTC2h 50m
2026-06-18 MFX7436 - Jun 18, 14:50 UTCJun 18, 17:05 UTC2h 15m
2026-06-17 MFX7435 - Jun 17, 19:55 UTCJun 18, 12:45 UTC16h 50m
2026-06-17 MFX7602 - Jun 17, 15:00 UTCJun 17, 15:40 UTC40m
2026-06-16 MFX672 - Jun 16, 16:35 UTCJun 17, 15:40 UTC23h 6m
2026-06-16 MFX672 - Jun 16, 15:24 UTCJun 16, 17:45 UTC2h 20m
2026-06-16 MFX671 - Jun 16, 09:15 UTCJun 16, 12:00 UTC2h 45m
2026-06-14 MFX7566 - Jun 14, 05:50 UTCJun 14, 08:25 UTC2h 35m
2026-06-12 MFX7674 OSR → ALA Jun 12, 03:50 UTCJun 12, 05:10 UTC1h 20m
2026-06-11 MFX7464 - Jun 11, 12:55 UTCJun 11, 13:50 UTC55m
2026-06-11 MFX7463 - Jun 11, 06:55 UTCJun 11, 10:10 UTC3h 15m
2026-06-10 MFX7467 MXP → BAH Jun 10, 02:50 UTCJun 10, 06:40 UTC3h 50m
2026-06-09 MFX7482 - Jun 9, 08:55 UTCJun 9, 09:35 UTC40m
2026-06-09 MFX7481 - Jun 9, 02:20 UTCJun 9, 06:55 UTC4h 35m
2026-06-07 MFX676 TLV → DWC Jun 7, 18:35 UTCJun 7, 21:05 UTC2h 30m
2026-06-07 MFX675 - Jun 7, 13:25 UTCJun 7, 16:05 UTC2h 40m
2026-06-06 MFX7530 - Jun 6, 10:25 UTCJun 6, 10:39 UTC15m
2026-06-06 MFX7529 - Jun 6, 07:30 UTCJun 6, 07:45 UTC15m
2026-06-05 MFX7618 - Jun 5, 15:05 UTCJun 5, 18:55 UTC3h 50m
2026-06-05 MFX7617 - Jun 5, 08:25 UTCJun 5, 12:25 UTC4h 0m
2026-06-04 MFX7632 - Jun 4, 19:25 UTCJun 4, 19:45 UTC20m
2026-06-04 MFX7631 - Jun 4, 15:55 UTCJun 4, 16:25 UTC30m
2026-06-04 MFX7522 - Jun 4, 04:30 UTCJun 4, 04:55 UTC25m
2026-06-03 MFX7680 - Jun 3, 09:05 UTCJun 3, 22:20 UTC13h 15m

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

Mode-S 507CB2 frequently asked

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