sensors Mode-S transponder
507CA4
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK67018 · BOEING 767-300
- Hex
- 507CA4
- Octal
- 24076244
- Decimal
- 5,274,788
- Country
- UZ
- Tail
- UK67018
- Type
- B763
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 26d ago
Last known position
Country allocation
The ICAO 24-bit address 507CA4 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 |
|---|---|---|---|
| MFX7664 | - | 3 | 2026-05-02 |
| MFX7663 | - | 3 | 2026-05-02 |
| MFX7661 | - | 3 | 2026-04-13 |
| MFX7677 | My Freighter LLC | 2 | 2026-04-28 |
| MFX7674 | My Freighter LLC | 2 | 2026-04-15 |
| MFX7662 | - | 2 | 2026-04-13 |
| MFX7486 | - | 2 | 2026-04-20 |
| MFX7434 | My Freighter LLC | 2 | 2026-04-15 |
| MFX7433 | - | 2 | 2026-04-15 |
| MFX7684 | - | 1 | 2026-04-23 |
| MFX7682 | - | 1 | 2026-04-30 |
| MFX7678 | - | 1 | 2026-04-29 |
| MFX7670 | My Freighter LLC | 1 | 2026-04-19 |
| MFX7669 | - | 1 | 2026-04-18 |
| MFX7566 | - | 1 | 2026-05-04 |
| MFX7565 | - | 1 | 2026-05-03 |
| MFX7485 | - | 1 | 2026-04-20 |
| MFX7482 | - | 1 | 2026-04-27 |
| MFX7481 | - | 1 | 2026-04-27 |
| MFX7452 | - | 1 | 2026-04-22 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-04 | MFX7566 | - | May 4, 00:55 UTC | May 4, 01:40 UTC | 45m |
| 2026-05-03 | MFX7565 | - | May 3, 21:44 UTC | May 3, 21:54 UTC | 10m |
| 2026-05-02 | MFX7664 | - | May 2, 09:20 UTC | May 2, 11:40 UTC | 2h 20m |
| 2026-05-02 | MFX7663 | - | May 2, 01:55 UTC | May 2, 05:50 UTC | 3h 55m |
| 2026-04-30 | MFX7682 | - | Apr 30, 22:35 UTC | Apr 30, 23:05 UTC | 30m |
| 2026-04-30 | MFX674 | TLV → DWC | Apr 30, 18:20 UTC | Apr 30, 20:40 UTC | 2h 20m |
| 2026-04-30 | MFX673 | - | Apr 30, 13:25 UTC | Apr 30, 16:15 UTC | 2h 50m |
| 2026-04-29 | MFX7678 | - | Apr 29, 03:04 UTC | Apr 29, 06:25 UTC | 3h 20m |
| 2026-04-28 | MFX7677 | TAS → TAS | Apr 28, 20:05 UTC | Apr 29, 00:05 UTC | 4h 0m |
| 2026-04-27 | MFX7677 | TAS → TAS | Apr 27, 21:05 UTC | Apr 28, 21:00 UTC | 23h 55m |
| 2026-04-27 | MFX7482 | - | Apr 27, 17:15 UTC | Apr 27, 21:15 UTC | 4h 0m |
| 2026-04-27 | MFX7481 | - | Apr 27, 09:25 UTC | Apr 27, 14:00 UTC | 4h 35m |
| 2026-04-24 | MFX623 | - | Apr 24, 12:20 UTC | Apr 24, 18:30 UTC | 6h 10m |
| 2026-04-23 | MFX7684 | - | Apr 23, 22:00 UTC | Apr 24, 18:30 UTC | 20h 30m |
| 2026-04-23 | MFX676 | TLV → DWC | Apr 23, 17:40 UTC | Apr 23, 20:20 UTC | 2h 40m |
| 2026-04-23 | MFX675 | - | Apr 23, 12:15 UTC | Apr 23, 15:20 UTC | 3h 5m |
| 2026-04-22 | MFX7452 | - | Apr 22, 07:05 UTC | Apr 22, 09:35 UTC | 2h 30m |
| 2026-04-21 | MFX7451 | DEL → CGN | Apr 21, 17:55 UTC | Apr 22, 05:01 UTC | 11h 5m |
| 2026-04-20 | MFX7486 | - | Apr 20, 19:05 UTC | Apr 21, 14:31 UTC | 19h 25m |
| 2026-04-20 | MFX7486 | - | Apr 20, 17:50 UTC | Apr 21, 14:31 UTC | 20h 40m |
| 2026-04-20 | MFX7485 | - | Apr 20, 10:40 UTC | Apr 20, 15:40 UTC | 5h 0m |
| 2026-04-19 | MFX7670 | LGG → LGG | Apr 19, 01:50 UTC | Apr 19, 04:10 UTC | 2h 20m |
| 2026-04-18 | MFX7669 | - | Apr 18, 20:35 UTC | Apr 18, 23:15 UTC | 2h 40m |
| 2026-04-17 | MFX7664 | - | Apr 17, 11:20 UTC | Apr 17, 12:10 UTC | 50m |
| 2026-04-17 | MFX7664 | - | Apr 17, 09:35 UTC | Apr 17, 11:15 UTC | 1h 40m |
| 2026-04-17 | MFX7663 | - | Apr 17, 01:20 UTC | Apr 17, 02:15 UTC | 55m |
| 2026-04-16 | MFX7663 | - | Apr 16, 23:55 UTC | Apr 17, 01:15 UTC | 1h 20m |
| 2026-04-15 | MFX7674 | OSR → ALA | Apr 15, 13:01 UTC | Apr 15, 14:50 UTC | 1h 49m |
| 2026-04-15 | MFX7674 | OSR → ALA | Apr 15, 11:50 UTC | Apr 15, 12:55 UTC | 1h 5m |
| 2026-04-15 | MFX7434 | MRA → LGG | Apr 15, 09:00 UTC | Apr 15, 09:25 UTC | 25m |
| 2026-04-15 | MFX7434 | MRA → LGG | Apr 15, 07:55 UTC | Apr 15, 08:55 UTC | 1h 0m |
| 2026-04-15 | MFX7433 | - | Apr 15, 05:00 UTC | Apr 15, 05:25 UTC | 25m |
| 2026-04-15 | MFX7433 | - | Apr 15, 02:55 UTC | Apr 15, 04:50 UTC | 1h 55m |
| 2026-04-13 | MFX7662 | - | Apr 13, 19:50 UTC | Apr 13, 21:40 UTC | 1h 50m |
| 2026-04-13 | MFX7662 | - | Apr 13, 19:15 UTC | Apr 13, 20:10 UTC | 55m |
| 2026-04-13 | MFX7661 | - | Apr 13, 16:15 UTC | Apr 13, 16:30 UTC | 15m |
| 2026-04-13 | MFX7661 | - | Apr 13, 15:50 UTC | Apr 13, 16:30 UTC | 40m |
| 2026-04-13 | MFX7661 | - | Apr 13, 12:30 UTC | Apr 13, 16:15 UTC | 3h 45m |
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 UK67018 page for operator, model, and routing details .