sensors Mode-S transponder
4D021D
ICAO 24-bit transponder address · allocated to Luxembourg
Currently assigned to LX-ZED · BOMBARDIER CL-600 Challenger
- Hex
- 4D021D
- Octal
- 23201035
- Decimal
- 5,046,813
- Country
- LU
- Tail
- LX-ZED
- Type
- CL60
- Flights observed
- 36
- Distinct callsigns
- 1
- Country
- LU
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 4D021D 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVW74VI | - | 36 | 2026-06-02 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVW74VI | VLC → MAD | Jun 2, 13:35 UTC | Jun 2, 14:15 UTC | 40m |
| 2026-05-25 | SVW74VI | - | May 25, 18:10 UTC | May 25, 19:25 UTC | 1h 14m |
| 2026-05-25 | SVW74VI | - | May 25, 15:10 UTC | May 25, 16:05 UTC | 55m |
| 2026-05-25 | SVW74VI | - | May 25, 13:35 UTC | May 25, 13:55 UTC | 20m |
| 2026-05-23 | SVW74VI | - | May 23, 10:30 UTC | May 23, 10:45 UTC | 15m |
| 2026-05-23 | SVW74VI | - | May 23, 08:25 UTC | May 23, 09:15 UTC | 50m |
| 2026-05-22 | SVW74VI | - | May 22, 12:30 UTC | May 22, 13:40 UTC | 1h 10m |
| 2026-05-19 | SVW74VI | - | May 19, 14:40 UTC | May 19, 16:10 UTC | 1h 30m |
| 2026-05-18 | SVW74VI | - | May 18, 13:20 UTC | May 18, 15:25 UTC | 2h 5m |
| 2026-05-18 | SVW74VI | NCE → CIA | May 18, 09:15 UTC | May 18, 10:05 UTC | 50m |
| 2026-05-17 | SVW74VI | LBG → NCE | May 17, 12:30 UTC | May 17, 13:40 UTC | 1h 10m |
| 2026-05-16 | SVW74VI | - | May 16, 16:15 UTC | May 16, 17:30 UTC | 1h 15m |
| 2026-05-14 | SVW74VI | - | May 14, 07:55 UTC | May 14, 08:20 UTC | 25m |
| 2026-05-13 | SVW74VI | - | May 13, 14:05 UTC | May 13, 16:05 UTC | 2h 0m |
| 2026-05-13 | SVW74VI | - | May 13, 07:30 UTC | May 13, 09:15 UTC | 1h 45m |
| 2026-05-13 | SVW74VI | LBG → FAB | May 13, 05:05 UTC | May 13, 06:10 UTC | 1h 5m |
| 2026-05-11 | SVW74VI | FAB → LBG | May 11, 10:55 UTC | May 11, 11:45 UTC | 50m |
| 2026-05-10 | SVW74VI | - | May 10, 09:15 UTC | May 10, 10:49 UTC | 1h 35m |
| 2026-05-09 | SVW74VI | - | May 9, 14:00 UTC | May 9, 14:25 UTC | 25m |
| 2026-05-08 | SVW74VI | - | May 8, 13:50 UTC | May 8, 14:40 UTC | 50m |
| 2026-05-07 | SVW74VI | - | May 7, 16:40 UTC | May 7, 17:45 UTC | 1h 5m |
| 2026-05-07 | SVW74VI | TLL → LBG | May 7, 11:35 UTC | May 7, 14:25 UTC | 2h 50m |
| 2026-05-06 | SVW74VI | - | May 6, 13:15 UTC | May 6, 16:05 UTC | 2h 50m |
| 2026-05-04 | SVW74VI | - | May 4, 13:15 UTC | May 4, 14:30 UTC | 1h 15m |
| 2026-05-04 | SVW74VI | NCE → LBG | May 4, 05:45 UTC | May 4, 06:55 UTC | 1h 10m |
| 2026-04-29 | SVW74VI | - | Apr 29, 06:55 UTC | Apr 29, 08:15 UTC | 1h 20m |
| 2026-04-26 | SVW74VI | - | Apr 26, 06:10 UTC | Apr 26, 07:50 UTC | 1h 40m |
| 2026-04-20 | SVW74VI | MAD → NCE | Apr 20, 18:20 UTC | Apr 20, 19:45 UTC | 1h 25m |
| 2026-04-16 | SVW74VI | - | Apr 16, 19:15 UTC | Apr 16, 19:35 UTC | 20m |
| 2026-04-16 | SVW74VI | - | Apr 16, 18:40 UTC | Apr 16, 19:10 UTC | 30m |
| 2026-04-16 | SVW74VI | - | Apr 16, 15:30 UTC | Apr 16, 15:55 UTC | 25m |
| 2026-04-16 | SVW74VI | - | Apr 16, 13:25 UTC | Apr 16, 13:35 UTC | 10m |
| 2026-04-16 | SVW74VI | - | Apr 16, 11:09 UTC | Apr 16, 11:54 UTC | 45m |
| 2026-04-16 | SVW74VI | - | Apr 16, 10:59 UTC | Apr 16, 11:04 UTC | 5m |
| 2026-04-14 | SVW74VI | - | Apr 14, 07:10 UTC | Apr 14, 08:25 UTC | 1h 15m |
| 2026-04-14 | SVW74VI | - | Apr 14, 06:45 UTC | Apr 14, 07:10 UTC | 25m |
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-ZED page for operator, model, and routing details .