sensors Mode-S transponder
3C64F7
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIGW · AIRBUS A-340-300
- Hex
- 3C64F7
- Octal
- 17062367
- Decimal
- 3,958,007
- Country
- DE
- Tail
- D-AIGW
- Type
- A343
- Flights observed
- 129
- Distinct callsigns
- 20
- Country
- DE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 3C64F7 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 |
|---|---|---|---|
| DLH432 | - | 15 | 2026-06-15 |
| DLH438 | - | 14 | 2026-07-14 |
| DLH433 | Lufthansa | 14 | 2026-06-16 |
| DLH439 | - | 13 | 2026-07-12 |
| DLH491 | - | 11 | 2026-07-10 |
| DLH490 | - | 10 | 2026-07-10 |
| DLH3V | Lufthansa | 8 | 2026-06-29 |
| DLH443 | - | 7 | 2026-06-29 |
| DLH595 | - | 5 | 2026-07-07 |
| DLH561 | Lufthansa | 5 | 2026-06-03 |
| DLH560 | Lufthansa | 5 | 2026-06-02 |
| DLH648 | - | 4 | 2026-07-09 |
| DLH405 | Lufthansa | 3 | 2026-04-30 |
| DLH404 | Lufthansa | 3 | 2026-04-29 |
| DLH651 | Lufthansa | 2 | 2026-05-29 |
| DLH646 | Lufthansa | 2 | 2026-06-01 |
| DLH420 | Lufthansa | 2 | 2026-07-05 |
| DLH9912 | Lufthansa | 1 | 2026-05-04 |
| DLH9911 | Lufthansa | 1 | 2026-05-06 |
| DLH9899 | Lufthansa | 1 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | DLH438 | - | Jul 14, 08:45 UTC | Jul 14, 09:45 UTC | 1h 0m |
| 2026-07-12 | DLH439 | - | Jul 12, 21:50 UTC | Jul 13, 07:50 UTC | 10h 0m |
| 2026-07-12 | DLH438 | FRA → DFW | Jul 12, 08:45 UTC | Jul 12, 19:10 UTC | 10h 25m |
| 2026-07-10 | DLH491 | SEA → FRA | Jul 10, 21:50 UTC | Jul 11, 07:10 UTC | 9h 20m |
| 2026-07-10 | DLH490 | FRA → SEA | Jul 10, 09:05 UTC | Jul 10, 19:10 UTC | 10h 5m |
| 2026-07-09 | DLH648 | - | Jul 9, 11:50 UTC | Jul 10, 06:30 UTC | 18h 40m |
| 2026-07-09 | DLH648 | - | Jul 9, 11:35 UTC | Jul 10, 06:30 UTC | 18h 55m |
| 2026-07-07 | DLH595 | - | Jul 7, 09:55 UTC | Jul 8, 03:15 UTC | 17h 20m |
| 2026-07-06 | DLH9899 | SKG → FRA | Jul 6, 21:35 UTC | Jul 7, 04:05 UTC | 6h 30m |
| 2026-07-05 | DLH420 | FRA → BOS | Jul 5, 16:00 UTC | Jul 6, 00:00 UTC | 8h 0m |
| 2026-07-04 | DLH439 | - | Jul 4, 21:50 UTC | Jul 5, 07:05 UTC | 9h 15m |
| 2026-07-04 | DLH438 | FRA → DFW | Jul 4, 08:50 UTC | Jul 4, 19:35 UTC | 10h 45m |
| 2026-07-03 | DLH595 | FRA → FRA | Jul 3, 10:50 UTC | Jul 4, 03:30 UTC | 16h 40m |
| 2026-07-02 | DLH439 | DFW → FRA | Jul 2, 22:10 UTC | Jul 3, 07:00 UTC | 8h 50m |
| 2026-07-02 | DLH438 | - | Jul 2, 08:50 UTC | Jul 2, 19:35 UTC | 10h 45m |
| 2026-07-01 | DLH595 | FRA → FRA | Jul 1, 10:05 UTC | Jul 2, 03:25 UTC | 17h 20m |
| 2026-06-30 | DLH439 | - | Jun 30, 21:25 UTC | Jul 1, 06:50 UTC | 9h 25m |
| 2026-06-30 | DLH438 | FRA → DFW | Jun 30, 08:35 UTC | Jun 30, 18:55 UTC | 10h 20m |
| 2026-06-29 | DLH443 | - | Jun 29, 20:19 UTC | Jun 30, 03:55 UTC | 7h 36m |
| 2026-06-29 | DLH3V | FRA → DTW | Jun 29, 09:34 UTC | Jun 29, 17:59 UTC | 8h 25m |
| 2026-06-28 | DLH439 | DFW → FRA | Jun 28, 21:24 UTC | Jun 29, 06:34 UTC | 9h 10m |
| 2026-06-28 | DLH438 | FRA → DFW | Jun 28, 08:55 UTC | Jun 28, 18:55 UTC | 10h 0m |
| 2026-06-27 | DLH443 | - | Jun 27, 21:04 UTC | Jun 28, 04:44 UTC | 7h 40m |
| 2026-06-27 | DLH3V | FRA → DTW | Jun 27, 10:34 UTC | Jun 27, 19:00 UTC | 8h 25m |
| 2026-06-26 | DLH443 | - | Jun 26, 20:55 UTC | Jun 27, 04:34 UTC | 7h 40m |
| 2026-06-26 | DLH3V | FRA → DTW | Jun 26, 09:59 UTC | Jun 26, 18:34 UTC | 8h 35m |
| 2026-06-25 | DLH648 | - | Jun 25, 11:50 UTC | Jun 26, 06:25 UTC | 18h 35m |
| 2026-06-25 | DLH648 | - | Jun 25, 11:39 UTC | Jun 26, 06:25 UTC | 18h 45m |
| 2026-06-24 | DLH491 | - | Jun 24, 22:14 UTC | Jun 25, 07:54 UTC | 9h 40m |
| 2026-06-24 | DLH490 | FRA → SEA | Jun 24, 10:25 UTC | Jun 24, 20:05 UTC | 9h 40m |
| 2026-06-23 | DLH439 | DFW → FRA | Jun 23, 21:29 UTC | Jun 24, 06:50 UTC | 9h 20m |
| 2026-06-23 | DLH438 | FRA → DFW | Jun 23, 08:54 UTC | Jun 23, 19:15 UTC | 10h 20m |
| 2026-06-18 | DLH443 | - | Jun 18, 20:15 UTC | Jun 19, 03:55 UTC | 7h 39m |
| 2026-06-18 | DLH3V | FRA → DTW | Jun 18, 10:40 UTC | Jun 18, 18:05 UTC | 7h 25m |
| 2026-06-18 | DLH3V | FRA → DTW | Jun 18, 09:35 UTC | Jun 18, 10:35 UTC | 1h 0m |
| 2026-06-17 | DLH421 | BOS → FRA | Jun 17, 02:35 UTC | Jun 17, 09:00 UTC | 6h 25m |
| 2026-06-16 | DLH420 | FRA → BOS | Jun 16, 16:05 UTC | Jun 16, 23:35 UTC | 7h 31m |
| 2026-06-16 | DLH433 | ORD → FRA | Jun 16, 04:00 UTC | Jun 16, 12:10 UTC | 8h 10m |
| 2026-06-15 | DLH432 | FRA → ORD | Jun 15, 15:55 UTC | Jun 16, 00:40 UTC | 8h 45m |
| 2026-06-15 | DLH433 | ORD → FRA | Jun 15, 04:00 UTC | Jun 15, 11:54 UTC | 7h 55m |
| 2026-06-14 | DLH432 | FRA → ORD | Jun 14, 15:55 UTC | Jun 15, 00:49 UTC | 8h 54m |
| 2026-06-12 | DLH433 | ORD → FRA | Jun 12, 09:00 UTC | Jun 12, 16:35 UTC | 7h 35m |
| 2026-06-12 | DLH432 | MSP → ORD | Jun 12, 05:05 UTC | Jun 12, 06:05 UTC | 1h 0m |
| 2026-06-11 | DLH432 | FRA → MSP | Jun 11, 15:50 UTC | Jun 12, 01:50 UTC | 10h 1m |
| 2026-06-10 | DLH443 | DTW → FRA | Jun 10, 20:30 UTC | Jun 11, 03:50 UTC | 7h 20m |
| 2026-06-10 | DLH3V | FRA → DTW | Jun 10, 09:55 UTC | Jun 10, 18:20 UTC | 8h 25m |
| 2026-06-09 | DLH439 | DFW → FRA | Jun 9, 21:45 UTC | Jun 10, 07:00 UTC | 9h 15m |
| 2026-06-09 | DLH438 | FRA → DFW | Jun 9, 09:00 UTC | Jun 9, 19:05 UTC | 10h 5m |
| 2026-06-08 | DLH443 | DTW → FRA | Jun 8, 20:15 UTC | Jun 9, 03:50 UTC | 7h 35m |
| 2026-06-08 | DLH3V | FRA → DTW | Jun 8, 09:40 UTC | Jun 8, 17:45 UTC | 8h 5m |
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-AIGW page for operator, model, and routing details .