sensors Mode-S transponder
507C8E
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK67009 · BOEING 767-300
- Hex
- 507C8E
- Octal
- 24076216
- Decimal
- 5,274,766
- Country
- UZ
- Tail
- UK67009
- Type
- B763
- Flights observed
- 57
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 507C8E 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 |
|---|---|---|---|
| MFX7484 | - | 4 | 2026-05-23 |
| MFX7594 | - | 3 | 2026-04-23 |
| MFX7507 | - | 3 | 2026-04-19 |
| MFX7483 | - | 3 | 2026-05-23 |
| MFX7462 | My Freighter LLC | 3 | 2026-05-13 |
| MFX7461 | - | 3 | 2026-05-13 |
| MFX674 | My Freighter LLC | 3 | 2026-05-28 |
| MFX7668 | My Freighter LLC | 2 | 2026-05-21 |
| MFX7662 | My Freighter LLC | 2 | 2026-05-26 |
| MFX7530 | - | 2 | 2026-05-26 |
| MFX7508 | - | 2 | 2026-04-19 |
| MFX7463 | - | 2 | 2026-05-11 |
| MFX7431 | - | 2 | 2026-05-21 |
| MFX673 | - | 2 | 2026-05-27 |
| MFX672 | - | 2 | 2026-05-29 |
| MFX671 | - | 2 | 2026-05-29 |
| MFX7672 | - | 1 | 2026-05-11 |
| MFX7670 | My Freighter LLC | 1 | 2026-05-13 |
| MFX7667 | - | 1 | 2026-05-21 |
| MFX7664 | - | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MFX672 | - | May 29, 23:20 UTC | May 30, 01:35 UTC | 2h 15m |
| 2026-05-29 | MFX671 | - | May 29, 08:30 UTC | May 29, 11:20 UTC | 2h 50m |
| 2026-05-28 | MFX674 | TLV → DWC | May 28, 08:25 UTC | May 28, 08:55 UTC | 30m |
| 2026-05-28 | MFX674 | TLV → DWC | May 28, 06:10 UTC | May 28, 06:30 UTC | 20m |
| 2026-05-27 | MFX673 | - | May 27, 23:45 UTC | May 28, 02:35 UTC | 2h 50m |
| 2026-05-26 | MFX7530 | - | May 26, 20:29 UTC | May 26, 21:09 UTC | 40m |
| 2026-05-26 | MFX7662 | LCA → TAS | May 26, 03:40 UTC | May 26, 16:35 UTC | 12h 55m |
| 2026-05-25 | MFX7482 | - | May 25, 18:00 UTC | May 25, 18:45 UTC | 45m |
| 2026-05-25 | MFX7481 | - | May 25, 10:50 UTC | May 25, 15:10 UTC | 4h 20m |
| 2026-05-23 | MFX7664 | - | May 23, 17:30 UTC | May 23, 19:35 UTC | 2h 5m |
| 2026-05-23 | MFX7484 | - | May 23, 11:20 UTC | May 23, 12:25 UTC | 1h 5m |
| 2026-05-23 | MFX7483 | - | May 23, 00:25 UTC | May 23, 04:40 UTC | 4h 14m |
| 2026-05-21 | MFX7668 | LGG → ALA | May 21, 15:40 UTC | May 21, 17:50 UTC | 2h 10m |
| 2026-05-21 | MFX7667 | - | May 21, 08:05 UTC | May 21, 08:35 UTC | 30m |
| 2026-05-21 | MFX7431 | - | May 21, 01:55 UTC | May 21, 06:00 UTC | 4h 5m |
| 2026-05-20 | MFX7431 | - | May 20, 05:35 UTC | May 21, 05:30 UTC | 23h 55m |
| 2026-05-20 | MFX672 | - | May 20, 03:35 UTC | May 21, 02:20 UTC | 22h 46m |
| 2026-05-19 | MFX671 | - | May 19, 22:15 UTC | May 20, 00:55 UTC | 2h 40m |
| 2026-05-18 | MFX674 | TLV → DWC | May 18, 04:25 UTC | May 18, 06:50 UTC | 2h 25m |
| 2026-05-17 | MFX673 | - | May 17, 22:55 UTC | May 18, 01:40 UTC | 2h 45m |
| 2026-05-16 | MFX7668 | LGG → ALA | May 16, 12:16 UTC | May 16, 14:41 UTC | 2h 25m |
| 2026-05-16 | MFX7486 | - | May 16, 07:16 UTC | May 16, 08:20 UTC | 1h 5m |
| 2026-05-15 | MFX7485 | - | May 15, 23:40 UTC | May 16, 04:10 UTC | 4h 30m |
| 2026-05-14 | MFX7530 | - | May 14, 12:35 UTC | May 14, 13:15 UTC | 40m |
| 2026-05-13 | MFX7670 | LGG → LGG | May 13, 19:30 UTC | May 14, 08:25 UTC | 12h 55m |
| 2026-05-13 | MFX7462 | DUB → DUB | May 13, 14:20 UTC | May 13, 16:30 UTC | 2h 10m |
| 2026-05-13 | MFX7461 | - | May 13, 08:25 UTC | May 13, 11:55 UTC | 3h 30m |
| 2026-05-11 | MFX7672 | - | May 11, 22:00 UTC | May 11, 22:35 UTC | 34m |
| 2026-05-11 | MFX7464 | BEG → OSR | May 11, 18:40 UTC | May 11, 19:35 UTC | 55m |
| 2026-05-11 | MFX7463 | - | May 11, 13:00 UTC | May 11, 16:15 UTC | 3h 15m |
| 2026-05-10 | MFX7463 | - | May 10, 15:35 UTC | May 11, 15:30 UTC | 23h 55m |
| 2026-05-10 | MFX7454 | - | May 10, 14:40 UTC | May 11, 13:30 UTC | 22h 50m |
| 2026-05-09 | MFX7453 | - | May 9, 06:15 UTC | May 9, 07:30 UTC | 1h 15m |
| 2026-05-05 | MFX7618 | - | May 5, 10:30 UTC | May 5, 12:20 UTC | 1h 50m |
| 2026-05-05 | MFX7617 | - | May 5, 03:10 UTC | May 5, 04:35 UTC | 1h 25m |
| 2026-05-04 | MFX7632 | - | May 4, 06:05 UTC | May 4, 06:25 UTC | 20m |
| 2026-05-03 | MFX7604 | - | May 3, 23:20 UTC | May 4, 02:15 UTC | 2h 55m |
| 2026-04-23 | MFX7594 | - | Apr 23, 09:35 UTC | Apr 23, 10:50 UTC | 1h 15m |
| 2026-04-22 | MFX7594 | - | Apr 22, 13:55 UTC | Apr 23, 10:50 UTC | 20h 55m |
| 2026-04-22 | MFX7594 | - | Apr 22, 13:05 UTC | Apr 23, 10:50 UTC | 21h 45m |
| 2026-04-21 | MFX7593 | - | Apr 21, 13:35 UTC | Apr 22, 13:20 UTC | 23h 45m |
| 2026-04-21 | MFX7662 | LCA → TAS | Apr 21, 10:55 UTC | Apr 21, 13:35 UTC | 2h 40m |
| 2026-04-21 | MFX7661 | - | Apr 21, 05:40 UTC | Apr 21, 07:50 UTC | 2h 10m |
| 2026-04-19 | MFX7508 | - | Apr 19, 21:30 UTC | Apr 19, 22:05 UTC | 35m |
| 2026-04-19 | MFX7507 | - | Apr 19, 17:55 UTC | Apr 19, 18:30 UTC | 35m |
| 2026-04-17 | MFX7508 | - | Apr 17, 04:45 UTC | Apr 17, 05:10 UTC | 25m |
| 2026-04-16 | MFX7507 | - | Apr 16, 23:20 UTC | Apr 16, 23:30 UTC | 10m |
| 2026-04-16 | MFX7507 | - | Apr 16, 22:54 UTC | Apr 16, 23:10 UTC | 15m |
| 2026-04-15 | MFX7462 | - | Apr 15, 13:05 UTC | Apr 15, 14:10 UTC | 1h 5m |
| 2026-04-15 | MFX7462 | - | Apr 15, 11:20 UTC | Apr 15, 12:25 UTC | 1h 5m |
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 UK67009 page for operator, model, and routing details .