sensors Mode-S transponder
4D0117
ICAO 24-bit transponder address · allocated to Luxembourg
Currently assigned to LX-VCM · BOEING 747-8
- Hex
- 4D0117
- Octal
- 23200427
- Decimal
- 5,046,551
- Country
- LU
- Tail
- LX-VCM
- Type
- B748
- Flights observed
- 134
- Distinct callsigns
- 20
- Country
- LU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 4D0117 falls within the block assigned to Luxembourg (LU) by ICAO Annex 10, Volume III. Every aircraft registered in Luxembourg 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 |
|---|---|---|---|
| CLX9521 | - | 8 | 2026-04-13 |
| CLX7625 | Cargolux | 5 | 2026-04-17 |
| CLX56R | Cargolux | 4 | 2026-04-17 |
| CLX4162 | - | 4 | 2026-04-15 |
| CLX3 | - | 4 | 2026-05-24 |
| CLX287 | Cargolux | 4 | 2026-05-15 |
| CLX245 | - | 4 | 2026-04-15 |
| CLX244 | Cargolux | 4 | 2026-05-04 |
| CLX9425 | Cargolux | 3 | 2026-05-09 |
| CLX7355 | Cargolux | 3 | 2026-05-16 |
| CLX7332 | Cargolux | 3 | 2026-05-27 |
| CLX54 | - | 3 | 2026-05-18 |
| CLX519 | - | 3 | 2026-04-14 |
| CLX5163 | Cargolux | 3 | 2026-04-16 |
| CLX5001 | Cargolux | 3 | 2026-05-06 |
| CLX4P | - | 3 | 2026-04-13 |
| CLX278 | Cargolux | 3 | 2026-05-26 |
| CLX226 | Cargolux | 3 | 2026-04-20 |
| CLX976 | - | 2 | 2026-05-21 |
| CLX9725 | Cargolux | 2 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | CLX83E | ANC → ORD | May 30, 01:05 UTC | May 30, 03:30 UTC | 2h 25m |
| 2026-05-29 | CLX83E | ANC → ORD | May 29, 16:45 UTC | May 29, 22:15 UTC | 5h 30m |
| 2026-05-29 | CLX5485 | ANC → ORD | May 29, 08:55 UTC | May 29, 15:05 UTC | 6h 10m |
| 2026-05-28 | CLX4484 | LUX → CGO | May 28, 14:55 UTC | May 29, 06:35 UTC | 15h 40m |
| 2026-05-28 | CLX531 | - | May 28, 06:30 UTC | May 28, 10:55 UTC | 4h 25m |
| 2026-05-27 | CLX531 | - | May 27, 16:35 UTC | May 27, 16:55 UTC | 20m |
| 2026-05-27 | CLX7332 | LUX → HKG | May 27, 13:45 UTC | May 27, 14:00 UTC | 15m |
| 2026-05-27 | CLX7332 | LUX → HKG | May 27, 11:45 UTC | May 27, 12:15 UTC | 30m |
| 2026-05-26 | CLX7332 | LUX → HKG | May 26, 21:25 UTC | May 27, 08:00 UTC | 10h 35m |
| 2026-05-26 | CLX278 | HKG → ANC | May 26, 11:30 UTC | May 26, 19:05 UTC | 7h 35m |
| 2026-05-26 | CLX278 | HKG → ANC | May 26, 03:00 UTC | May 26, 08:15 UTC | 5h 15m |
| 2026-05-25 | CLX278 | HKG → ANC | May 25, 15:35 UTC | May 26, 01:24 UTC | 9h 50m |
| 2026-05-25 | CLX4327 | LUX → HKG | May 25, 07:45 UTC | May 25, 08:20 UTC | 35m |
| 2026-05-24 | CLX4327 | LUX → HKG | May 24, 20:50 UTC | May 24, 23:15 UTC | 2h 25m |
| 2026-05-24 | CLX17G | SEA → PIK | May 24, 16:00 UTC | May 24, 17:25 UTC | 1h 25m |
| 2026-05-24 | CLX17G | SEA → PIK | May 24, 06:30 UTC | May 24, 14:35 UTC | 8h 5m |
| 2026-05-24 | CLX3 | - | May 24, 01:15 UTC | May 24, 03:25 UTC | 2h 10m |
| 2026-05-23 | CLX3 | - | May 23, 11:20 UTC | May 23, 22:25 UTC | 11h 6m |
| 2026-05-23 | CLX79 | - | May 23, 04:15 UTC | May 23, 08:20 UTC | 4h 5m |
| 2026-05-22 | CLX79 | - | May 22, 07:50 UTC | May 23, 07:45 UTC | 23h 54m |
| 2026-05-22 | CLX9725 | LUX → CGO | May 22, 05:50 UTC | May 23, 05:20 UTC | 23h 29m |
| 2026-05-22 | CLX9725 | LUX → CGO | May 22, 04:35 UTC | May 22, 08:35 UTC | 4h 0m |
| 2026-05-21 | CLX976 | - | May 21, 14:30 UTC | May 21, 18:30 UTC | 4h 0m |
| 2026-05-21 | CLX976 | - | May 21, 04:05 UTC | May 21, 04:20 UTC | 15m |
| 2026-05-21 | CLX7623 | HAN → HKG | May 21, 00:30 UTC | May 21, 01:00 UTC | 30m |
| 2026-05-20 | CLX7623 | HAN → HKG | May 20, 10:10 UTC | May 20, 20:25 UTC | 10h 15m |
| 2026-05-19 | CLX85 | - | May 19, 18:05 UTC | May 20, 07:15 UTC | 13h 11m |
| 2026-05-19 | CLX85 | - | May 19, 10:50 UTC | May 20, 07:15 UTC | 20h 26m |
| 2026-05-18 | CLX54 | - | May 18, 23:50 UTC | May 19, 18:30 UTC | 18h 40m |
| 2026-05-18 | CLX54 | - | May 18, 21:50 UTC | May 19, 18:30 UTC | 20h 40m |
| 2026-05-18 | CLX54 | - | May 18, 21:35 UTC | May 19, 18:30 UTC | 20h 55m |
| 2026-05-18 | CLX57R | IAH → PIK | May 18, 17:45 UTC | May 18, 19:05 UTC | 1h 19m |
| 2026-05-18 | CLX57R | IAH → PIK | May 18, 07:45 UTC | May 18, 16:00 UTC | 8h 15m |
| 2026-05-17 | CLX8 | - | May 17, 17:35 UTC | May 18, 03:55 UTC | 10h 20m |
| 2026-05-17 | CLX597 | - | May 17, 09:40 UTC | May 17, 13:50 UTC | 4h 10m |
| 2026-05-16 | CLX597 | - | May 16, 22:50 UTC | May 16, 23:10 UTC | 20m |
| 2026-05-16 | CLX7355 | NRT → HKG | May 16, 19:50 UTC | May 16, 20:00 UTC | 10m |
| 2026-05-16 | CLX7355 | NRT → HKG | May 16, 17:50 UTC | May 16, 18:15 UTC | 25m |
| 2026-05-16 | CLX7355 | NRT → HKG | May 16, 04:20 UTC | May 16, 15:05 UTC | 10h 46m |
| 2026-05-15 | CLX287 | HKG → ANC | May 15, 12:15 UTC | May 15, 20:05 UTC | 7h 49m |
| 2026-05-15 | CLX287 | HKG → ANC | May 15, 07:40 UTC | May 15, 09:50 UTC | 2h 10m |
| 2026-05-14 | CLX287 | HKG → ANC | May 14, 23:40 UTC | May 15, 05:20 UTC | 5h 40m |
| 2026-05-14 | CLX287 | HKG → ANC | May 14, 12:15 UTC | May 14, 22:10 UTC | 9h 55m |
| 2026-05-13 | CLX4793 | AMM → HKG | May 13, 21:35 UTC | May 14, 09:10 UTC | 11h 35m |
| 2026-05-11 | CLX753 | HKG → LUX | May 11, 15:50 UTC | May 11, 20:00 UTC | 4h 11m |
| 2026-05-11 | CLX753 | HKG → LUX | May 11, 05:15 UTC | May 11, 05:30 UTC | 15m |
| 2026-05-10 | CLX9937 | LUX → HKG | May 10, 14:04 UTC | May 11, 01:20 UTC | 11h 15m |
| 2026-05-09 | CLX892 | LUX → HKG | May 9, 17:10 UTC | May 10, 08:25 UTC | 15h 15m |
| 2026-05-09 | CLX9425 | LUX → ICN | May 9, 12:55 UTC | May 9, 15:00 UTC | 2h 5m |
| 2026-05-09 | CLX9425 | LUX → ICN | May 9, 08:25 UTC | May 9, 08:45 UTC | 20m |
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 LX-VCM page for operator, model, and routing details .