sensors Mode-S transponder
3C9C23
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-BGAC · BOMBARDIER BD-100 Challenger 350
- Hex
- 3C9C23
- Octal
- 17116043
- Decimal
- 3,972,131
- Country
- DE
- Tail
- D-BGAC
- Type
- CL35
- Flights observed
- 61
- Distinct callsigns
- 3
- Country
- DE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 3C9C23 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | ADN95Y | - | Jul 20, 07:35 UTC | Jul 20, 08:25 UTC | 50m |
| 2026-07-17 | ADN95Y | - | Jul 17, 16:49 UTC | Jul 17, 17:15 UTC | 25m |
| 2026-07-17 | ADN95Y | BCN → MUC | Jul 17, 13:25 UTC | Jul 17, 15:25 UTC | 2h 0m |
| 2026-07-17 | ADN95Y | - | Jul 17, 08:15 UTC | Jul 17, 10:05 UTC | 1h 50m |
| 2026-07-13 | ADN95Y | - | Jul 13, 15:55 UTC | Jul 13, 16:15 UTC | 20m |
| 2026-07-13 | ADN95Y | - | Jul 13, 14:45 UTC | Jul 13, 15:10 UTC | 25m |
| 2026-07-13 | ADN95Y | NUE → FRA | Jul 13, 05:05 UTC | Jul 13, 05:45 UTC | 40m |
| 2026-07-12 | ADN95Y | - | Jul 12, 12:01 UTC | Jul 12, 12:25 UTC | 25m |
| 2026-07-06 | ADN111 | - | Jul 6, 15:55 UTC | Jul 6, 17:05 UTC | 1h 10m |
| 2026-07-06 | ADN111 | - | Jul 6, 11:25 UTC | Jul 6, 13:25 UTC | 2h 0m |
| 2026-07-02 | ADN95Y | - | Jul 2, 11:20 UTC | Jul 2, 12:25 UTC | 1h 5m |
| 2026-06-30 | ADN95Y | NCE → SZG | Jun 30, 10:30 UTC | Jun 30, 11:35 UTC | 1h 5m |
| 2026-06-30 | ADN95Y | NUE → NCE | Jun 30, 07:30 UTC | Jun 30, 08:45 UTC | 1h 15m |
| 2026-06-26 | ADN95Y | HEL → NUE | Jun 26, 10:20 UTC | Jun 26, 12:19 UTC | 2h 0m |
| 2026-06-25 | ADN95Y | NUE → HEL | Jun 25, 09:45 UTC | Jun 25, 11:50 UTC | 2h 5m |
| 2026-06-24 | ADN95Y | - | Jun 24, 19:00 UTC | Jun 24, 19:39 UTC | 40m |
| 2026-06-22 | ADN95Y | BRU → BER | Jun 22, 18:44 UTC | Jun 22, 19:44 UTC | 1h 0m |
| 2026-06-22 | ADN95Y | - | Jun 22, 13:44 UTC | Jun 22, 14:55 UTC | 1h 10m |
| 2026-06-22 | ADN95Y | NUE → BER | Jun 22, 05:44 UTC | Jun 22, 06:19 UTC | 35m |
| 2026-06-21 | ADN95Y | - | Jun 21, 11:44 UTC | Jun 21, 12:10 UTC | 25m |
| 2026-06-19 | ADN111 | - | Jun 19, 17:34 UTC | Jun 19, 18:39 UTC | 1h 5m |
| 2026-06-19 | ADN111 | LIN → LBG | Jun 19, 14:49 UTC | Jun 19, 15:54 UTC | 1h 5m |
| 2026-06-19 | ADN111 | MUC → LIN | Jun 19, 12:25 UTC | Jun 19, 13:09 UTC | 45m |
| 2026-06-18 | ADN95Y | - | Jun 18, 16:25 UTC | Jun 18, 17:40 UTC | 1h 15m |
| 2026-06-17 | ADN95Y | - | Jun 17, 07:45 UTC | Jun 17, 09:15 UTC | 1h 30m |
| 2026-06-11 | ADN95Y | - | Jun 11, 16:15 UTC | Jun 11, 17:00 UTC | 45m |
| 2026-06-11 | ADN95Y | BRU → KSF | Jun 11, 14:10 UTC | Jun 11, 14:55 UTC | 45m |
| 2026-06-10 | ADN95Y | - | Jun 10, 11:25 UTC | Jun 10, 12:25 UTC | 1h 0m |
| 2026-06-09 | ADN95Y | - | Jun 9, 17:20 UTC | Jun 9, 18:05 UTC | 45m |
| 2026-06-08 | ADN95Y | - | Jun 8, 15:35 UTC | Jun 8, 16:15 UTC | 40m |
| 2026-06-08 | ADN95Y | NUE → FRA | Jun 8, 05:10 UTC | Jun 8, 05:40 UTC | 30m |
| 2026-06-07 | ADN95Y | - | Jun 7, 11:05 UTC | Jun 7, 11:25 UTC | 20m |
| 2026-06-07 | ADN111 | ZRH → MUC | Jun 7, 08:55 UTC | Jun 7, 09:30 UTC | 35m |
| 2026-06-05 | ADN111 | MUC → ZRH | Jun 5, 14:30 UTC | Jun 5, 15:10 UTC | 40m |
| 2026-05-19 | ADN95Y | - | May 19, 14:50 UTC | May 19, 15:55 UTC | 1h 5m |
| 2026-05-18 | ADN95Y | - | May 18, 15:35 UTC | May 18, 16:30 UTC | 55m |
| 2026-05-18 | ADN95Y | - | May 18, 12:35 UTC | May 18, 13:15 UTC | 40m |
| 2026-05-14 | ADN95Y | - | May 14, 09:05 UTC | May 14, 09:55 UTC | 50m |
| 2026-05-14 | ADN95Y | - | May 14, 06:10 UTC | May 14, 07:55 UTC | 1h 45m |
| 2026-05-13 | ADN95Y | - | May 13, 17:40 UTC | May 13, 17:55 UTC | 15m |
| 2026-05-11 | ADN95Y | - | May 11, 10:50 UTC | May 11, 11:05 UTC | 15m |
| 2026-05-11 | ADN95Y | - | May 11, 07:35 UTC | May 11, 09:25 UTC | 1h 50m |
| 2026-05-10 | ADN95Y | MUC → BER | May 10, 13:55 UTC | May 10, 14:40 UTC | 45m |
| 2026-05-08 | ADN95Y | NUE → MUC | May 8, 13:05 UTC | May 8, 13:30 UTC | 25m |
| 2026-05-07 | ADN111 | - | May 7, 16:45 UTC | May 7, 18:25 UTC | 1h 40m |
| 2026-05-07 | ADN111 | - | May 7, 05:15 UTC | May 7, 07:10 UTC | 1h 55m |
| 2026-05-04 | ADN95Y | - | May 4, 19:05 UTC | May 4, 19:50 UTC | 45m |
| 2026-05-04 | ADN95Y | NUE → BER | May 4, 04:44 UTC | May 4, 05:25 UTC | 40m |
| 2026-05-03 | ADN95Y | MUC → NUE | May 3, 10:25 UTC | May 3, 10:50 UTC | 25m |
| 2026-04-30 | ADN95Y | NUE → MUC | Apr 30, 13:55 UTC | Apr 30, 14:15 UTC | 20m |
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-BGAC page for operator, model, and routing details .