sensors Mode-S transponder
3C6718
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIXX · AIRBUS A-350-900
- Hex
- 3C6718
- Octal
- 17063430
- Decimal
- 3,958,552
- Country
- DE
- Tail
- D-AIXX
- Type
- A359
- Flights observed
- 98
- Distinct callsigns
- 18
- Country
- DE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 3C6718 falls within the block assigned to Germany (DE) by ICAO Annex 10, Volume III. Every aircraft registered in Germany 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DLH726 | Lufthansa | 12 | 2026-05-28 |
| DLH727 | Lufthansa | 11 | 2026-05-29 |
| DLH715 | Lufthansa | 10 | 2026-05-24 |
| DLH411 | Lufthansa | 8 | 2026-05-30 |
| DLH410 | Lufthansa | 8 | 2026-05-30 |
| DLH764 | Lufthansa | 7 | 2026-05-23 |
| DLH4C | Lufthansa | 7 | 2026-05-28 |
| DLH2C | Lufthansa | 7 | 2026-05-27 |
| DLH765 | Lufthansa | 6 | 2026-05-23 |
| DLH714 | Lufthansa | 6 | 2026-05-24 |
| DLH412 | Lufthansa | 4 | 2026-06-02 |
| DLH437 | Lufthansa | 3 | 2026-05-31 |
| DLH413 | Lufthansa | 3 | 2026-05-12 |
| DLH436 | Lufthansa | 2 | 2026-05-31 |
| DLH5Y | Lufthansa | 1 | 2026-06-01 |
| DLH495 | Lufthansa | 1 | 2026-04-25 |
| DLH494 | Lufthansa | 1 | 2026-04-24 |
| DLH2P | Lufthansa | 1 | 2026-06-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | DLH412 | MUC → EWR | Jun 2, 14:30 UTC | Jun 2, 22:00 UTC | 7h 30m |
| 2026-06-02 | DLH2P | SAN → MUC | Jun 2, 00:35 UTC | Jun 2, 11:30 UTC | 10h 55m |
| 2026-06-01 | DLH5Y | MUC → SAN | Jun 1, 11:30 UTC | Jun 1, 22:40 UTC | 11h 10m |
| 2026-05-31 | DLH437 | ORD → MUC | May 31, 21:05 UTC | Jun 1, 05:10 UTC | 8h 5m |
| 2026-05-31 | DLH436 | MUC → ORD | May 31, 08:25 UTC | May 31, 16:50 UTC | 8h 25m |
| 2026-05-30 | DLH411 | JFK → MUC | May 30, 22:00 UTC | May 30, 23:40 UTC | 1h 40m |
| 2026-05-30 | DLH410 | MUC → JFK | May 30, 11:15 UTC | May 30, 19:00 UTC | 7h 45m |
| 2026-05-29 | DLH727 | PVG → MUC | May 29, 16:50 UTC | May 30, 04:05 UTC | 11h 15m |
| 2026-05-29 | DLH727 | PVG → MUC | May 29, 05:30 UTC | May 30, 04:00 UTC | 22h 30m |
| 2026-05-28 | DLH726 | MUC → PVG | May 28, 22:05 UTC | May 29, 17:15 UTC | 19h 10m |
| 2026-05-28 | DLH726 | MUC → PVG | May 28, 20:40 UTC | May 29, 17:15 UTC | 20h 35m |
| 2026-05-28 | DLH4C | FRA → PMI | May 28, 03:15 UTC | May 28, 11:30 UTC | 8h 15m |
| 2026-05-27 | DLH2C | MUC → ORD | May 27, 14:30 UTC | May 27, 23:15 UTC | 8h 45m |
| 2026-05-26 | DLH727 | PVG → MUC | May 26, 16:50 UTC | May 27, 03:59 UTC | 11h 10m |
| 2026-05-26 | DLH727 | PVG → MUC | May 26, 06:04 UTC | May 27, 03:59 UTC | 21h 55m |
| 2026-05-26 | DLH727 | PVG → MUC | May 26, 05:49 UTC | May 27, 01:29 UTC | 19h 40m |
| 2026-05-26 | DLH726 | MUC → PVG | May 26, 00:04 UTC | May 26, 21:09 UTC | 21h 5m |
| 2026-05-25 | DLH726 | MUC → PVG | May 25, 22:05 UTC | May 26, 21:09 UTC | 23h 5m |
| 2026-05-25 | DLH726 | MUC → PVG | May 25, 20:40 UTC | May 26, 17:09 UTC | 20h 30m |
| 2026-05-24 | DLH715 | HND → MUC | May 24, 20:40 UTC | May 25, 14:50 UTC | 18h 10m |
| 2026-05-24 | DLH715 | HND → MUC | May 24, 14:05 UTC | May 25, 14:00 UTC | 23h 55m |
| 2026-05-24 | DLH714 | MUC → HND | May 24, 12:05 UTC | May 25, 12:00 UTC | 23h 55m |
| 2026-05-24 | DLH714 | MUC → HND | May 24, 10:40 UTC | May 25, 08:05 UTC | 21h 25m |
| 2026-05-23 | DLH765 | BOM → MUC | May 23, 20:45 UTC | May 24, 06:00 UTC | 9h 15m |
| 2026-05-23 | DLH764 | MUC → BOM | May 23, 18:25 UTC | May 23, 18:35 UTC | 10m |
| 2026-05-23 | DLH764 | MUC → BOM | May 23, 10:30 UTC | May 23, 16:55 UTC | 6h 25m |
| 2026-05-22 | DLH765 | BOM → MUC | May 22, 20:50 UTC | May 23, 06:05 UTC | 9h 14m |
| 2026-05-22 | DLH764 | MUC → BOM | May 22, 18:35 UTC | May 22, 18:50 UTC | 15m |
| 2026-05-22 | DLH764 | MUC → BOM | May 22, 10:30 UTC | May 22, 17:25 UTC | 6h 55m |
| 2026-05-21 | DLH715 | HND → MUC | May 21, 00:55 UTC | May 21, 14:30 UTC | 13h 35m |
| 2026-05-20 | DLH714 | MUC → HND | May 20, 10:50 UTC | May 20, 22:45 UTC | 11h 55m |
| 2026-05-19 | DLH727 | PVG → MUC | May 19, 17:00 UTC | May 20, 04:00 UTC | 11h 0m |
| 2026-05-19 | DLH727 | PVG → MUC | May 19, 06:05 UTC | May 20, 04:00 UTC | 21h 55m |
| 2026-05-19 | DLH727 | PVG → MUC | May 19, 05:55 UTC | May 20, 04:00 UTC | 22h 5m |
| 2026-05-18 | DLH726 | MUC → PVG | May 18, 22:05 UTC | May 19, 17:15 UTC | 19h 10m |
| 2026-05-18 | DLH726 | MUC → PVG | May 18, 20:40 UTC | May 19, 17:15 UTC | 20h 35m |
| 2026-05-18 | DLH715 | HND → MUC | May 18, 01:10 UTC | May 18, 14:55 UTC | 13h 45m |
| 2026-05-17 | DLH714 | MUC → HND | May 17, 10:40 UTC | May 17, 22:30 UTC | 11h 50m |
| 2026-05-17 | DLH437 | ORD → MUC | May 17, 04:40 UTC | May 17, 05:10 UTC | 30m |
| 2026-05-16 | DLH437 | ORD → MUC | May 16, 20:45 UTC | May 17, 04:35 UTC | 7h 50m |
| 2026-05-16 | DLH436 | MUC → ORD | May 16, 08:16 UTC | May 16, 17:10 UTC | 8h 55m |
| 2026-05-15 | DLH411 | JFK → MUC | May 15, 22:35 UTC | May 16, 05:35 UTC | 7h 0m |
| 2026-05-15 | DLH410 | MUC → JFK | May 15, 10:15 UTC | May 15, 18:20 UTC | 8h 4m |
| 2026-05-15 | DLH727 | PVG → MUC | May 15, 02:40 UTC | May 15, 04:00 UTC | 1h 20m |
| 2026-05-13 | DLH726 | MUC → PVG | May 13, 20:40 UTC | May 14, 00:35 UTC | 3h 55m |
| 2026-05-13 | DLH4C | FRA → PMI | May 13, 02:55 UTC | May 13, 10:50 UTC | 7h 55m |
| 2026-05-12 | DLH2C | MUC → ORD | May 12, 14:25 UTC | May 12, 23:40 UTC | 9h 15m |
| 2026-05-12 | DLH413 | EWR → MUC | May 12, 05:55 UTC | May 12, 08:15 UTC | 2h 20m |
| 2026-05-11 | DLH412 | MUC → EWR | May 11, 14:35 UTC | May 11, 22:35 UTC | 8h 0m |
| 2026-05-11 | DLH4C | FRA → PMI | May 11, 03:15 UTC | May 11, 11:05 UTC | 7h 50m |
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 D-AIXX page for operator, model, and routing details .