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