sensors Mode-S transponder
3C6719
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIXY · AIRBUS A-350-900
- Hex
- 3C6719
- Octal
- 17063431
- Decimal
- 3,958,553
- Country
- DE
- Tail
- D-AIXY
- Type
- A359
- Flights observed
- 85
- Distinct callsigns
- 16
- Country
- DE
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 3C6719 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DLH726 | Lufthansa | 12 | 2026-05-23 |
| DLH727 | Lufthansa | 11 | 2026-05-24 |
| DLH765 | Lufthansa | 8 | 2026-04-24 |
| DLH715 | Lufthansa | 8 | 2026-05-23 |
| DLH714 | Lufthansa | 8 | 2026-05-22 |
| DLH5Y | Lufthansa | 7 | 2026-05-28 |
| DLH413 | Lufthansa | 6 | 2026-06-02 |
| DLH412 | Lufthansa | 5 | 2026-06-01 |
| DLH2P | Lufthansa | 5 | 2026-05-29 |
| DLH4C | Lufthansa | 4 | 2026-06-01 |
| DLH2C | Lufthansa | 4 | 2026-05-31 |
| DLH764 | Lufthansa | 3 | 2026-04-24 |
| DLH4J | Lufthansa | 1 | 2026-06-02 |
| DLH475 | Lufthansa | 1 | 2026-06-03 |
| DLH437 | Lufthansa | 1 | 2026-05-27 |
| DLH436 | Lufthansa | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | DLH475 | YUL → MUC | Jun 3, 01:10 UTC | Jun 3, 02:45 UTC | 1h 35m |
| 2026-06-02 | DLH4J | MUC → YUL | Jun 2, 15:25 UTC | Jun 2, 22:25 UTC | 7h 0m |
| 2026-06-02 | DLH413 | EWR → MUC | Jun 2, 01:05 UTC | Jun 2, 07:55 UTC | 6h 50m |
| 2026-06-01 | DLH412 | MUC → EWR | Jun 1, 14:35 UTC | Jun 1, 22:25 UTC | 7h 50m |
| 2026-06-01 | DLH4C | FRA → PMI | Jun 1, 03:30 UTC | Jun 1, 11:35 UTC | 8h 5m |
| 2026-05-31 | DLH2C | MUC → ORD | May 31, 15:35 UTC | Jun 1, 00:05 UTC | 8h 30m |
| 2026-05-31 | DLH4C | FRA → PMI | May 31, 09:15 UTC | May 31, 11:30 UTC | 2h 15m |
| 2026-05-30 | DLH2C | MUC → ORD | May 30, 14:25 UTC | May 30, 23:00 UTC | 8h 35m |
| 2026-05-30 | DLH413 | EWR → MUC | May 30, 10:20 UTC | May 30, 10:55 UTC | 35m |
| 2026-05-30 | DLH413 | EWR → MUC | May 30, 00:45 UTC | May 30, 08:25 UTC | 7h 40m |
| 2026-05-29 | DLH412 | MUC → EWR | May 29, 14:35 UTC | May 29, 22:25 UTC | 7h 50m |
| 2026-05-29 | DLH2P | SAN → MUC | May 29, 00:55 UTC | May 29, 11:50 UTC | 10h 55m |
| 2026-05-28 | DLH5Y | MUC → SAN | May 28, 18:30 UTC | May 28, 22:15 UTC | 3h 45m |
| 2026-05-28 | DLH5Y | MUC → SAN | May 28, 10:55 UTC | May 28, 13:00 UTC | 2h 5m |
| 2026-05-27 | DLH437 | ORD → MUC | May 27, 21:05 UTC | May 28, 05:20 UTC | 8h 15m |
| 2026-05-27 | DLH436 | MUC → ORD | May 27, 08:25 UTC | May 27, 17:15 UTC | 8h 50m |
| 2026-05-24 | DLH727 | PVG → MUC | May 24, 21:10 UTC | May 25, 03:55 UTC | 6h 45m |
| 2026-05-23 | DLH726 | MUC → PVG | May 23, 22:20 UTC | May 24, 21:15 UTC | 22h 55m |
| 2026-05-23 | DLH726 | MUC → PVG | May 23, 21:50 UTC | May 24, 00:00 UTC | 2h 10m |
| 2026-05-23 | DLH726 | MUC → PVG | May 23, 20:30 UTC | May 23, 21:45 UTC | 1h 15m |
| 2026-05-23 | DLH715 | HND → MUC | May 23, 01:00 UTC | May 23, 14:45 UTC | 13h 44m |
| 2026-05-22 | DLH714 | MUC → HND | May 22, 10:50 UTC | May 22, 22:30 UTC | 11h 40m |
| 2026-05-21 | DLH727 | PVG → MUC | May 21, 16:50 UTC | May 22, 04:00 UTC | 11h 10m |
| 2026-05-21 | DLH727 | PVG → MUC | May 21, 05:50 UTC | May 22, 04:00 UTC | 22h 10m |
| 2026-05-20 | DLH726 | MUC → PVG | May 20, 22:20 UTC | May 21, 17:10 UTC | 18h 50m |
| 2026-05-20 | DLH726 | MUC → PVG | May 20, 20:35 UTC | May 21, 17:10 UTC | 20h 35m |
| 2026-05-20 | DLH715 | HND → MUC | May 20, 01:00 UTC | May 20, 14:50 UTC | 13h 51m |
| 2026-05-19 | DLH714 | MUC → HND | May 19, 10:45 UTC | May 19, 22:45 UTC | 12h 0m |
| 2026-05-18 | DLH2P | SAN → MUC | May 18, 00:40 UTC | May 18, 11:10 UTC | 10h 30m |
| 2026-05-17 | DLH5Y | MUC → SAN | May 17, 11:20 UTC | May 17, 22:25 UTC | 11h 5m |
| 2026-05-17 | DLH727 | PVG → MUC | May 17, 00:10 UTC | May 17, 04:05 UTC | 3h 55m |
| 2026-05-16 | DLH726 | MUC → PVG | May 16, 00:25 UTC | May 17, 00:15 UTC | 23h 51m |
| 2026-05-15 | DLH726 | MUC → PVG | May 15, 21:15 UTC | May 16, 01:10 UTC | 3h 55m |
| 2026-05-15 | DLH715 | HND → MUC | May 15, 01:35 UTC | May 15, 15:10 UTC | 13h 34m |
| 2026-05-14 | DLH714 | MUC → HND | May 14, 11:15 UTC | May 14, 23:20 UTC | 12h 5m |
| 2026-05-13 | DLH715 | HND → MUC | May 13, 00:45 UTC | May 13, 14:25 UTC | 13h 40m |
| 2026-05-12 | DLH714 | MUC → HND | May 12, 10:50 UTC | May 12, 22:45 UTC | 11h 55m |
| 2026-05-12 | DLH727 | PVG → MUC | May 12, 02:45 UTC | May 12, 03:50 UTC | 1h 5m |
| 2026-05-10 | DLH726 | MUC → PVG | May 10, 20:54 UTC | May 11, 00:49 UTC | 3h 55m |
| 2026-05-10 | DLH2P | SAN → MUC | May 10, 00:24 UTC | May 10, 11:10 UTC | 10h 45m |
| 2026-05-09 | DLH5Y | MUC → SAN | May 9, 11:05 UTC | May 9, 22:25 UTC | 11h 20m |
| 2026-05-09 | DLH413 | EWR → MUC | May 9, 01:00 UTC | May 9, 08:15 UTC | 7h 15m |
| 2026-05-08 | DLH412 | MUC → EWR | May 8, 14:35 UTC | May 8, 22:45 UTC | 8h 10m |
| 2026-05-08 | DLH2P | SAN → MUC | May 8, 00:34 UTC | May 8, 11:30 UTC | 10h 55m |
| 2026-05-07 | DLH5Y | MUC → SAN | May 7, 11:00 UTC | May 7, 21:45 UTC | 10h 45m |
| 2026-05-07 | DLH5Y | MUC → SAN | May 7, 10:45 UTC | May 7, 10:55 UTC | 10m |
| 2026-05-07 | DLH413 | EWR → MUC | May 7, 00:50 UTC | May 7, 08:10 UTC | 7h 20m |
| 2026-05-06 | DLH412 | MUC → EWR | May 6, 14:30 UTC | May 6, 22:45 UTC | 8h 14m |
| 2026-05-06 | DLH4C | FRA → PMI | May 6, 03:00 UTC | May 6, 10:55 UTC | 7h 55m |
| 2026-05-05 | DLH2C | MUC → ORD | May 5, 13:55 UTC | May 5, 22:50 UTC | 8h 55m |
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-AIXY page for operator, model, and routing details .