sensors Mode-S transponder
3C4A0F
ICAO 24-bit transponder address · allocated to Germany
- Hex
- 3C4A0F
- Octal
- 17045017
- Decimal
- 3,951,119
- Country
- DE
- Flights observed
- 74
- Distinct callsigns
- 17
- Country
- DE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 3C4A0F 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DLH761 | Lufthansa | 12 | 2026-05-25 |
| DLH760 | Lufthansa | 12 | 2026-05-25 |
| DLH796 | Lufthansa | 11 | 2026-05-29 |
| DLH797 | Lufthansa | 10 | 2026-05-22 |
| DLH500 | Lufthansa | 8 | 2026-05-24 |
| DLH501 | Lufthansa | 6 | 2026-05-24 |
| DLH729 | Lufthansa | 3 | 2026-05-26 |
| DLH471 | Lufthansa | 2 | 2026-05-08 |
| DLH470 | Lufthansa | 2 | 2026-05-08 |
| DLH7JF | Lufthansa | 1 | 2026-04-20 |
| DLH753 | Lufthansa | 1 | 2026-04-25 |
| DLH728 | Lufthansa | 1 | 2026-05-26 |
| DLH6EE | Lufthansa | 1 | 2026-04-20 |
| DLH543 | Lufthansa | 1 | 2026-05-29 |
| DLH542 | Lufthansa | 1 | 2026-05-28 |
| DLH4MW | Lufthansa | 1 | 2026-04-20 |
| DLH107 | Lufthansa | 1 | 2026-04-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | DLH796 | FRA → HKG | May 29, 20:05 UTC | May 30, 07:15 UTC | 11h 10m |
| 2026-05-29 | DLH543 | BOG → FRA | May 29, 05:40 UTC | May 29, 15:40 UTC | 10h 0m |
| 2026-05-28 | DLH542 | FRA → BOG | May 28, 13:50 UTC | May 29, 00:50 UTC | 11h 0m |
| 2026-05-26 | DLH729 | PVG → FRA | May 26, 23:29 UTC | May 27, 17:05 UTC | 17h 36m |
| 2026-05-26 | DLH729 | PVG → FRA | May 26, 17:50 UTC | May 27, 17:05 UTC | 23h 16m |
| 2026-05-26 | DLH729 | PVG → FRA | May 26, 15:49 UTC | May 27, 15:45 UTC | 23h 55m |
| 2026-05-26 | DLH728 | FRA → PVG | May 26, 14:05 UTC | May 27, 13:45 UTC | 23h 40m |
| 2026-05-25 | DLH761 | DEL → FRA | May 25, 21:45 UTC | May 26, 05:49 UTC | 8h 5m |
| 2026-05-25 | DLH760 | FRA → DEL | May 25, 11:45 UTC | May 25, 18:50 UTC | 7h 5m |
| 2026-05-24 | DLH501 | GIG → MUC | May 24, 19:30 UTC | May 25, 06:20 UTC | 10h 50m |
| 2026-05-24 | DLH500 | MUC → GIG | May 24, 07:45 UTC | May 24, 08:00 UTC | 15m |
| 2026-05-23 | DLH500 | MUC → GIG | May 23, 20:50 UTC | May 24, 07:00 UTC | 10h 10m |
| 2026-05-22 | DLH797 | HKG → FRA | May 22, 21:10 UTC | May 23, 04:15 UTC | 7h 4m |
| 2026-05-22 | DLH797 | HKG → FRA | May 22, 15:50 UTC | May 22, 16:05 UTC | 15m |
| 2026-05-21 | DLH796 | FRA → HKG | May 21, 20:05 UTC | May 22, 07:30 UTC | 11h 25m |
| 2026-05-20 | DLH761 | DEL → FRA | May 20, 21:45 UTC | May 21, 05:30 UTC | 7h 45m |
| 2026-05-20 | DLH760 | FRA → DEL | May 20, 11:45 UTC | May 20, 19:20 UTC | 7h 35m |
| 2026-05-18 | DLH501 | GIG → MUC | May 18, 19:35 UTC | May 19, 06:15 UTC | 10h 40m |
| 2026-05-17 | DLH500 | MUC → GIG | May 17, 20:40 UTC | May 18, 07:50 UTC | 11h 10m |
| 2026-05-16 | DLH797 | HKG → FRA | May 16, 23:55 UTC | May 17, 04:35 UTC | 4h 40m |
| 2026-05-16 | DLH797 | HKG → FRA | May 16, 15:55 UTC | May 16, 16:15 UTC | 20m |
| 2026-05-16 | DLH796 | FRA → HKG | May 16, 07:01 UTC | May 16, 07:31 UTC | 30m |
| 2026-05-15 | DLH796 | FRA → HKG | May 15, 20:25 UTC | May 16, 00:10 UTC | 3h 45m |
| 2026-05-14 | DLH797 | HKG → FRA | May 14, 19:05 UTC | May 15, 04:35 UTC | 9h 30m |
| 2026-05-14 | DLH797 | HKG → FRA | May 14, 15:55 UTC | May 14, 16:10 UTC | 15m |
| 2026-05-14 | DLH796 | FRA → HKG | May 14, 06:55 UTC | May 14, 07:40 UTC | 45m |
| 2026-05-13 | DLH796 | FRA → HKG | May 13, 20:15 UTC | May 14, 04:45 UTC | 8h 30m |
| 2026-05-12 | DLH761 | DEL → FRA | May 12, 21:50 UTC | May 13, 05:55 UTC | 8h 5m |
| 2026-05-12 | DLH760 | FRA → DEL | May 12, 11:45 UTC | May 12, 18:45 UTC | 7h 0m |
| 2026-05-11 | DLH761 | DEL → FRA | May 11, 21:40 UTC | May 12, 06:00 UTC | 8h 20m |
| 2026-05-11 | DLH760 | FRA → DEL | May 11, 11:45 UTC | May 11, 18:45 UTC | 7h 0m |
| 2026-05-09 | DLH761 | DEL → FRA | May 9, 21:40 UTC | May 10, 05:55 UTC | 8h 15m |
| 2026-05-09 | DLH760 | FRA → DEL | May 9, 11:50 UTC | May 9, 19:10 UTC | 7h 20m |
| 2026-05-08 | DLH471 | YYZ → FRA | May 8, 22:50 UTC | May 9, 05:55 UTC | 7h 5m |
| 2026-05-08 | DLH470 | FRA → YYZ | May 8, 12:34 UTC | May 8, 20:30 UTC | 7h 55m |
| 2026-05-07 | DLH797 | HKG → FRA | May 7, 21:10 UTC | May 8, 04:34 UTC | 7h 24m |
| 2026-05-07 | DLH797 | HKG → FRA | May 7, 15:55 UTC | May 7, 16:15 UTC | 20m |
| 2026-05-07 | DLH796 | FRA → HKG | May 7, 06:40 UTC | May 7, 07:05 UTC | 25m |
| 2026-05-06 | DLH796 | FRA → HKG | May 6, 20:00 UTC | May 7, 04:30 UTC | 8h 30m |
| 2026-05-05 | DLH471 | YYZ → FRA | May 5, 23:25 UTC | May 6, 06:35 UTC | 7h 10m |
| 2026-05-05 | DLH470 | FRA → YYZ | May 5, 12:35 UTC | May 5, 20:20 UTC | 7h 45m |
| 2026-05-04 | DLH501 | GIG → MUC | May 4, 19:25 UTC | May 5, 05:50 UTC | 10h 25m |
| 2026-05-04 | DLH500 | MUC → GIG | May 4, 08:20 UTC | May 4, 08:35 UTC | 15m |
| 2026-05-03 | DLH500 | MUC → GIG | May 3, 20:49 UTC | May 4, 07:35 UTC | 10h 45m |
| 2026-05-02 | DLH761 | DEL → FRA | May 2, 21:50 UTC | May 3, 05:40 UTC | 7h 49m |
| 2026-05-02 | DLH760 | FRA → DEL | May 2, 11:50 UTC | May 2, 19:00 UTC | 7h 10m |
| 2026-05-01 | DLH501 | GIG → MUC | May 1, 19:25 UTC | May 2, 05:50 UTC | 10h 26m |
| 2026-04-30 | DLH500 | MUC → GIG | Apr 30, 20:40 UTC | May 1, 08:00 UTC | 11h 20m |
| 2026-04-29 | DLH761 | DEL → FRA | Apr 29, 21:40 UTC | Apr 30, 05:55 UTC | 8h 14m |
| 2026-04-29 | DLH760 | FRA → DEL | Apr 29, 11:55 UTC | Apr 29, 19:25 UTC | 7h 30m |
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.