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