sensors Mode-S transponder
4D020C
ICAO 24-bit transponder address · allocated to Luxembourg
Currently assigned to LX-ZIO · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4D020C
- Octal
- 23201014
- Decimal
- 5,046,796
- Country
- LU
- Tail
- LX-ZIO
- Type
- GLEX
- Flights observed
- 64
- Distinct callsigns
- 2
- Country
- LU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4D020C 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | SVW33IO | - | Jul 25, 11:10 UTC | Jul 25, 12:35 UTC | 1h 25m |
| 2026-07-24 | SVW33IO | - | Jul 24, 15:10 UTC | Jul 24, 15:40 UTC | 30m |
| 2026-07-24 | SVW33IO | - | Jul 24, 13:15 UTC | Jul 24, 13:50 UTC | 35m |
| 2026-07-24 | SVW33IO | - | Jul 24, 10:25 UTC | Jul 24, 11:25 UTC | 1h 0m |
| 2026-07-16 | SVW33IO | BRN → BSL | Jul 16, 07:10 UTC | Jul 16, 07:30 UTC | 20m |
| 2026-07-15 | SVW33IO | - | Jul 15, 15:55 UTC | Jul 15, 16:50 UTC | 55m |
| 2026-07-13 | SVW33IO | - | Jul 13, 07:30 UTC | Jul 13, 08:20 UTC | 50m |
| 2026-07-12 | SVW33IO | - | Jul 12, 09:15 UTC | Jul 12, 16:50 UTC | 7h 35m |
| 2026-07-10 | SVW33IO | - | Jul 10, 09:05 UTC | Jul 10, 16:40 UTC | 7h 35m |
| 2026-07-09 | SVW33I | OLB → LBG | Jul 9, 18:45 UTC | Jul 9, 20:20 UTC | 1h 35m |
| 2026-07-09 | SVW33IO | NCE → OLB | Jul 9, 17:05 UTC | Jul 9, 17:45 UTC | 40m |
| 2026-07-09 | SVW33IO | OLB → NCE | Jul 9, 14:30 UTC | Jul 9, 15:15 UTC | 45m |
| 2026-07-07 | SVW33IO | NCE → OLB | Jul 7, 07:35 UTC | Jul 7, 08:15 UTC | 40m |
| 2026-07-06 | SVW33IO | - | Jul 6, 07:20 UTC | Jul 6, 08:00 UTC | 40m |
| 2026-07-05 | SVW33IO | LBG → OLB | Jul 5, 11:05 UTC | Jul 5, 12:35 UTC | 1h 30m |
| 2026-07-05 | SVW33IO | - | Jul 5, 08:30 UTC | Jul 5, 09:55 UTC | 1h 25m |
| 2026-07-05 | SVW33IO | - | Jul 5, 05:50 UTC | Jul 5, 06:25 UTC | 35m |
| 2026-07-03 | SVW33IO | - | Jul 3, 15:25 UTC | Jul 3, 16:05 UTC | 40m |
| 2026-07-03 | SVW33IO | BRN → NCE | Jul 3, 10:00 UTC | Jul 3, 10:55 UTC | 55m |
| 2026-07-03 | SVW33IO | - | Jul 3, 07:15 UTC | Jul 3, 08:05 UTC | 50m |
| 2026-06-30 | SVW33IO | EDI → NCE | Jun 30, 19:35 UTC | Jun 30, 21:45 UTC | 2h 10m |
| 2026-06-30 | SVW33IO | - | Jun 30, 10:30 UTC | Jun 30, 12:55 UTC | 2h 25m |
| 2026-06-29 | SVW33IO | - | Jun 29, 08:14 UTC | Jun 29, 08:54 UTC | 40m |
| 2026-06-28 | SVW33IO | - | Jun 28, 23:20 UTC | Jun 29, 06:40 UTC | 7h 20m |
| 2026-06-27 | SVW33IO | - | Jun 27, 13:15 UTC | Jun 27, 19:24 UTC | 6h 10m |
| 2026-06-27 | SVW33IO | - | Jun 27, 10:19 UTC | Jun 27, 12:09 UTC | 1h 50m |
| 2026-06-26 | SVW33IO | NCE → BRN | Jun 26, 13:19 UTC | Jun 26, 14:09 UTC | 50m |
| 2026-06-18 | SVW33IO | - | Jun 18, 08:25 UTC | Jun 18, 10:50 UTC | 2h 25m |
| 2026-06-16 | SVW33IO | NCE → ISL | Jun 16, 09:25 UTC | Jun 16, 11:40 UTC | 2h 15m |
| 2026-06-15 | SVW33IO | - | Jun 15, 14:05 UTC | Jun 15, 14:34 UTC | 30m |
| 2026-06-15 | SVW33IO | - | Jun 15, 09:15 UTC | Jun 15, 09:45 UTC | 30m |
| 2026-06-10 | SVW33IO | - | Jun 10, 16:45 UTC | Jun 10, 18:20 UTC | 1h 35m |
| 2026-06-10 | SVW33IO | - | Jun 10, 07:35 UTC | Jun 10, 09:15 UTC | 1h 40m |
| 2026-06-09 | SVW33IO | TRN → NCE | Jun 9, 13:15 UTC | Jun 9, 13:50 UTC | 35m |
| 2026-06-07 | SVW33IO | - | Jun 7, 15:00 UTC | Jun 7, 15:30 UTC | 30m |
| 2026-06-05 | SVW33IO | ATH → NCE | Jun 5, 14:00 UTC | Jun 5, 16:10 UTC | 2h 10m |
| 2026-05-31 | SVW33IO | NCE → ATH | May 31, 08:30 UTC | May 31, 10:40 UTC | 2h 10m |
| 2026-05-28 | SVW33IO | - | May 28, 16:15 UTC | May 28, 17:15 UTC | 1h 0m |
| 2026-05-27 | SVW33IO | NCE → HPN | May 27, 13:20 UTC | May 27, 21:30 UTC | 8h 10m |
| 2026-05-25 | SVW33IO | - | May 25, 23:19 UTC | May 26, 06:44 UTC | 7h 25m |
| 2026-05-24 | SVW33IO | - | May 24, 14:25 UTC | May 24, 21:50 UTC | 7h 25m |
| 2026-05-24 | SVW33IO | MLA → NCE | May 24, 10:35 UTC | May 24, 12:10 UTC | 1h 35m |
| 2026-05-22 | SVW33IO | - | May 22, 15:35 UTC | May 22, 16:40 UTC | 1h 5m |
| 2026-05-22 | SVW33IO | NCE → CIA | May 22, 13:30 UTC | May 22, 14:25 UTC | 55m |
| 2026-05-19 | SVW33IO | - | May 19, 14:55 UTC | May 19, 16:35 UTC | 1h 40m |
| 2026-05-18 | SVW33IO | NCE → NHT | May 18, 08:20 UTC | May 18, 09:55 UTC | 1h 35m |
| 2026-05-09 | SVW33IO | - | May 9, 08:30 UTC | May 9, 09:35 UTC | 1h 5m |
| 2026-05-08 | SVW33IO | YYZ → LBG | May 8, 23:45 UTC | May 9, 06:55 UTC | 7h 10m |
| 2026-05-07 | SVW33IO | SJC → YYZ | May 7, 23:14 UTC | May 8, 03:30 UTC | 4h 15m |
| 2026-05-06 | SVW33IO | - | May 6, 21:15 UTC | May 7, 00:15 UTC | 3h 0m |
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-ZIO page for operator, model, and routing details .