sensors Mode-S transponder
507C8F
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK67010 · BOEING 767-300
- Hex
- 507C8F
- Octal
- 24076217
- Decimal
- 5,274,767
- Country
- UZ
- Tail
- UK67010
- Type
- B763
- Flights observed
- 28
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- Apr 30, 14:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 507C8F 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 |
|---|---|---|---|
| MFX7523 | - | 3 | 2026-04-22 |
| MFX7668 | My Freighter LLC | 2 | 2026-04-16 |
| MFX7662 | - | 2 | 2026-04-15 |
| MFX7592 | - | 2 | 2026-04-21 |
| MFX7524 | - | 2 | 2026-04-22 |
| MFX7414 | My Freighter LLC | 2 | 2026-04-27 |
| MFX7412 | - | 2 | 2026-04-27 |
| MFX7688 | - | 1 | 2026-04-30 |
| MFX7661 | - | 1 | 2026-04-15 |
| MFX7626 | - | 1 | 2026-04-18 |
| MFX7625 | - | 1 | 2026-04-18 |
| MFX7624 | - | 1 | 2026-04-28 |
| MFX7596 | - | 1 | 2026-04-23 |
| MFX7595 | - | 1 | 2026-04-22 |
| MFX7510 | - | 1 | 2026-04-24 |
| MFX7462 | My Freighter LLC | 1 | 2026-04-30 |
| MFX7461 | - | 1 | 2026-04-30 |
| MFX7411 | - | 1 | 2026-04-25 |
| MFX674 | My Freighter LLC | 1 | 2026-04-25 |
| MFX673 | - | 1 | 2026-04-25 |
Recent flights last 28
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-04-30 | MFX7688 | - | Apr 30, 12:50 UTC | Apr 30, 14:45 UTC | 1h 55m |
| 2026-04-30 | MFX7462 | DUB → DUB | Apr 30, 08:50 UTC | Apr 30, 09:50 UTC | 1h 0m |
| 2026-04-30 | MFX7461 | - | Apr 30, 02:40 UTC | Apr 30, 04:00 UTC | 1h 20m |
| 2026-04-28 | MFX7624 | - | Apr 28, 19:20 UTC | Apr 28, 22:00 UTC | 2h 40m |
| 2026-04-27 | MFX7414 | BHX → BHX | Apr 27, 12:45 UTC | Apr 28, 04:45 UTC | 16h 0m |
| 2026-04-27 | MFX7412 | - | Apr 27, 08:25 UTC | Apr 27, 08:55 UTC | 30m |
| 2026-04-26 | MFX7412 | - | Apr 26, 12:55 UTC | Apr 27, 08:55 UTC | 20h 0m |
| 2026-04-25 | MFX7411 | - | Apr 25, 22:30 UTC | Apr 26, 12:10 UTC | 13h 40m |
| 2026-04-25 | MFX674 | TLV → DWC | Apr 25, 19:05 UTC | Apr 25, 20:45 UTC | 1h 40m |
| 2026-04-25 | MFX673 | - | Apr 25, 13:10 UTC | Apr 25, 16:15 UTC | 3h 5m |
| 2026-04-24 | MFX7510 | - | Apr 24, 00:05 UTC | Apr 24, 00:30 UTC | 25m |
| 2026-04-23 | MFX7596 | - | Apr 23, 15:25 UTC | Apr 23, 21:50 UTC | 6h 24m |
| 2026-04-22 | MFX7595 | - | Apr 22, 19:50 UTC | Apr 23, 16:20 UTC | 20h 30m |
| 2026-04-22 | MFX7524 | - | Apr 22, 19:15 UTC | Apr 23, 16:20 UTC | 21h 5m |
| 2026-04-22 | MFX7523 | - | Apr 22, 01:10 UTC | Apr 22, 13:25 UTC | 12h 15m |
| 2026-04-21 | MFX7592 | - | Apr 21, 05:50 UTC | Apr 22, 02:05 UTC | 20h 15m |
| 2026-04-21 | MFX7592 | - | Apr 21, 05:00 UTC | Apr 22, 02:05 UTC | 21h 5m |
| 2026-04-18 | MFX7626 | - | Apr 18, 07:25 UTC | Apr 18, 09:20 UTC | 1h 55m |
| 2026-04-18 | MFX7625 | - | Apr 18, 03:55 UTC | Apr 18, 04:15 UTC | 20m |
| 2026-04-16 | MFX7668 | LGG → ALA | Apr 16, 03:09 UTC | Apr 16, 04:44 UTC | 1h 35m |
| 2026-04-16 | MFX7668 | LGG → ALA | Apr 16, 02:24 UTC | Apr 16, 03:04 UTC | 40m |
| 2026-04-15 | MFX7662 | - | Apr 15, 07:01 UTC | Apr 15, 07:25 UTC | 25m |
| 2026-04-15 | MFX7662 | - | Apr 15, 05:00 UTC | Apr 15, 06:55 UTC | 1h 55m |
| 2026-04-15 | MFX7661 | - | Apr 15, 00:00 UTC | Apr 15, 00:40 UTC | 40m |
| 2026-04-13 | MFX7524 | - | Apr 13, 13:25 UTC | Apr 13, 15:40 UTC | 2h 15m |
| 2026-04-13 | MFX7523 | - | Apr 13, 07:55 UTC | Apr 13, 08:00 UTC | 5m |
| 2026-04-13 | MFX7523 | - | Apr 13, 07:05 UTC | Apr 13, 08:00 UTC | 55m |
| 2026-04-12 | MFX7414 | - | Apr 12, 17:15 UTC | Apr 12, 19:50 UTC | 2h 35m |
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 UK67010 page for operator, model, and routing details .