sensors Mode-S transponder

507C96

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK67015 · BOEING 767-300

Hex
507C96
Octal
24076226
Decimal
5,274,774
Country
UZ
Tail
UK67015
Type
B763
No current signal · last broadcast 14h ago
Flights observed
111
Distinct callsigns
20
Country
UZ
Last broadcast
14h ago

Last known position

Most recent position reported by Mode-S 507C96.

Country allocation

The ICAO 24-bit address 507C96 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
MFX7463 - 5 2026-06-25
MFX7672 - 4 2026-07-13
MFX7668 My Freighter LLC 4 2026-06-25
MFX7461 - 4 2026-07-02
MFX7431 - 4 2026-06-06
MFX7618 - 3 2026-07-11
MFX7563 - 3 2026-06-21
MFX7524 - 3 2026-06-20
MFX7464 - 3 2026-06-25
MFX7462 - 3 2026-07-03
MFX7432 My Freighter LLC 3 2026-06-06
MFX7412 - 3 2026-04-19
MFX7678 - 2 2026-07-04
MFX7676 - 2 2026-06-13
MFX7674 My Freighter LLC 2 2026-05-09
MFX7671 - 2 2026-07-13
MFX7662 - 2 2026-07-03
MFX7633 - 2 2026-07-10
MFX7617 - 2 2026-07-10
MFX7566 - 2 2026-04-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 MFX7672 - Jul 13, 14:45 UTCJul 13, 18:00 UTC3h 15m
2026-07-13 MFX7671 - Jul 13, 07:55 UTCJul 13, 11:35 UTC3h 40m
2026-07-11 MFX7618 - Jul 11, 10:45 UTCJul 11, 12:55 UTC2h 10m
2026-07-10 MFX7617 HKG → MST Jul 10, 15:20 UTCJul 11, 07:40 UTC16h 20m
2026-07-10 MFX7633 - Jul 10, 12:00 UTCJul 10, 12:25 UTC25m
2026-07-09 MFX7504 ALA → TAS Jul 9, 12:40 UTCJul 9, 15:25 UTC2h 45m
2026-07-09 MFX7503 - Jul 9, 07:00 UTCJul 9, 09:45 UTC2h 45m
2026-07-04 MFX7678 - Jul 4, 14:25 UTCJul 4, 17:45 UTC3h 20m
2026-07-04 MFX7677 - Jul 4, 07:30 UTCJul 4, 11:15 UTC3h 45m
2026-07-03 MFX7662 - Jul 3, 07:35 UTCJul 4, 07:30 UTC23h 55m
2026-07-03 MFX7662 - Jul 3, 06:45 UTCJul 3, 08:50 UTC2h 5m
2026-07-03 MFX7462 - Jul 3, 02:10 UTCJul 3, 04:15 UTC2h 5m
2026-07-02 MFX7461 - Jul 2, 01:35 UTCJul 2, 04:45 UTC3h 10m
2026-06-30 MFX7543 - Jun 30, 14:45 UTCJun 30, 21:55 UTC7h 10m
2026-06-30 MFX7543 - Jun 30, 02:15 UTCJun 30, 21:55 UTC19h 40m
2026-06-30 MFX7442 - Jun 30, 01:00 UTCJun 30, 01:14 UTC15m
2026-06-29 MFX7441 - Jun 29, 22:00 UTCJun 29, 22:24 UTC25m
2026-06-29 MFX7542 - Jun 29, 03:14 UTCJun 29, 21:05 UTC17h 50m
2026-06-27 MFX7618 - Jun 27, 20:19 UTCJun 28, 00:00 UTC3h 40m
2026-06-26 MFX7617 HKG → MST Jun 26, 16:30 UTCJun 27, 08:29 UTC16h 0m
2026-06-26 MFX7631 - Jun 26, 13:30 UTCJun 26, 14:05 UTC35m
2026-06-25 MFX7668 LGG → ALA Jun 25, 17:34 UTCJun 26, 14:05 UTC20h 30m
2026-06-25 MFX7668 LGG → ALA Jun 25, 17:05 UTCJun 26, 14:05 UTC21h 0m
2026-06-25 MFX7464 - Jun 25, 10:50 UTCJun 25, 12:40 UTC1h 50m
2026-06-25 MFX7463 - Jun 25, 05:25 UTCJun 25, 08:34 UTC3h 10m
2026-06-24 MFX7463 - Jun 24, 09:34 UTCJun 25, 08:34 UTC23h 0m
2026-06-24 MFX7463 - Jun 24, 09:24 UTCJun 25, 07:30 UTC22h 5m
2026-06-24 MFX7565 - Jun 24, 06:29 UTCJun 24, 06:35 UTC5m
2026-06-22 MFX676 TLV → DWC Jun 22, 22:15 UTCJun 23, 00:19 UTC2h 5m
2026-06-22 MFX675 - Jun 22, 17:10 UTCJun 22, 19:49 UTC2h 40m
2026-06-21 MFX7564 - Jun 21, 12:44 UTCJun 21, 13:24 UTC40m
2026-06-21 MFX7563 - Jun 21, 09:40 UTCJun 21, 09:49 UTC10m
2026-06-21 MFX7563 - Jun 21, 07:29 UTCJun 21, 07:49 UTC20m
2026-06-20 MFX7524 - Jun 20, 02:44 UTCJun 20, 03:19 UTC35m
2026-06-19 MFX7670 - Jun 19, 06:24 UTCJun 19, 23:14 UTC16h 50m
2026-06-18 MFX7669 - Jun 18, 22:35 UTCJun 18, 23:35 UTC1h 0m
2026-06-17 MFX7442 - Jun 17, 20:25 UTCJun 17, 22:55 UTC2h 30m
2026-06-17 MFX7441 - Jun 17, 04:40 UTCJun 17, 06:20 UTC1h 40m
2026-06-15 MFX678 - Jun 15, 16:24 UTCJun 15, 18:50 UTC2h 25m
2026-06-15 MFX677 - Jun 15, 11:00 UTCJun 15, 13:40 UTC2h 40m
2026-06-13 MFX7676 - Jun 13, 21:00 UTCJun 14, 00:05 UTC3h 5m
2026-06-13 MFX7466 - Jun 13, 14:50 UTCJun 13, 15:50 UTC1h 0m
2026-06-13 MFX7465 - Jun 13, 09:15 UTCJun 13, 12:30 UTC3h 15m
2026-06-12 MFX7564 - Jun 12, 09:35 UTCJun 13, 09:30 UTC23h 54m
2026-06-12 MFX7563 - Jun 12, 06:25 UTCJun 12, 06:40 UTC15m
2026-06-10 MFX7624 - Jun 10, 20:20 UTCJun 10, 21:50 UTC1h 30m
2026-06-10 MFX7484 - Jun 10, 17:10 UTCJun 10, 18:10 UTC1h 0m
2026-06-10 MFX7483 - Jun 10, 09:35 UTCJun 10, 14:10 UTC4h 35m
2026-06-09 MFX7522 - Jun 9, 02:15 UTCJun 9, 02:55 UTC40m
2026-06-08 MFX7521 - Jun 8, 07:10 UTCJun 8, 23:05 UTC15h 55m

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

Mode-S 507C96 frequently asked

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