sensors Mode-S transponder
3C0BD2
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-ATMJ · BOMBARDIER CL-600 Challenger
- Hex
- 3C0BD2
- Octal
- 17005722
- Decimal
- 3,935,186
- Country
- DE
- Tail
- D-ATMJ
- Type
- CL60
- Flights observed
- 45
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 3C0BD2 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DATMJ | - | 45 | 2026-06-02 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | DATMJ | - | Jun 2, 17:30 UTC | Jun 2, 18:40 UTC | 1h 10m |
| 2026-06-02 | DATMJ | - | Jun 2, 13:40 UTC | Jun 2, 14:45 UTC | 1h 5m |
| 2026-06-01 | DATMJ | - | Jun 1, 07:30 UTC | Jun 1, 09:45 UTC | 2h 15m |
| 2026-06-01 | DATMJ | - | Jun 1, 04:10 UTC | Jun 1, 06:15 UTC | 2h 5m |
| 2026-05-30 | DATMJ | - | May 30, 16:25 UTC | May 30, 17:40 UTC | 1h 15m |
| 2026-05-29 | DATMJ | - | May 29, 10:40 UTC | May 29, 11:25 UTC | 45m |
| 2026-05-28 | DATMJ | - | May 28, 16:15 UTC | May 28, 17:00 UTC | 45m |
| 2026-05-28 | DATMJ | - | May 28, 14:20 UTC | May 28, 15:00 UTC | 40m |
| 2026-05-28 | DATMJ | LEJ → BQH | May 28, 10:00 UTC | May 28, 11:25 UTC | 1h 25m |
| 2026-05-27 | DATMJ | BQH → LEJ | May 27, 11:10 UTC | May 27, 12:30 UTC | 1h 20m |
| 2026-05-25 | DATMJ | NQY → BQH | May 25, 13:25 UTC | May 25, 14:20 UTC | 55m |
| 2026-05-24 | DATMJ | - | May 24, 07:25 UTC | May 24, 09:15 UTC | 1h 50m |
| 2026-05-23 | DATMJ | LBG → MUC | May 23, 14:10 UTC | May 23, 15:10 UTC | 1h 0m |
| 2026-05-22 | DATMJ | JMK → LBG | May 22, 10:35 UTC | May 22, 13:35 UTC | 3h 0m |
| 2026-05-22 | DATMJ | LIN → JMK | May 22, 07:05 UTC | May 22, 09:40 UTC | 2h 35m |
| 2026-05-21 | DATMJ | - | May 21, 08:20 UTC | May 21, 09:00 UTC | 40m |
| 2026-05-19 | DATMJ | LIN → GVA | May 19, 07:05 UTC | May 19, 07:40 UTC | 35m |
| 2026-05-19 | DATMJ | MXP → LIN | May 19, 05:45 UTC | May 19, 06:05 UTC | 20m |
| 2026-05-18 | DATMJ | - | May 18, 14:10 UTC | May 18, 16:55 UTC | 2h 45m |
| 2026-05-15 | DATMJ | - | May 15, 12:05 UTC | May 15, 14:10 UTC | 2h 5m |
| 2026-05-14 | DATMJ | - | May 14, 13:05 UTC | May 14, 14:25 UTC | 1h 20m |
| 2026-05-14 | DATMJ | - | May 14, 10:40 UTC | May 14, 11:40 UTC | 1h 0m |
| 2026-05-14 | DATMJ | - | May 14, 08:35 UTC | May 14, 09:15 UTC | 40m |
| 2026-05-10 | DATMJ | - | May 10, 19:50 UTC | May 10, 20:45 UTC | 55m |
| 2026-05-10 | DATMJ | NCE → CIA | May 10, 13:05 UTC | May 10, 13:55 UTC | 50m |
| 2026-05-09 | DATMJ | - | May 9, 09:30 UTC | May 9, 10:45 UTC | 1h 15m |
| 2026-05-09 | DATMJ | - | May 9, 05:10 UTC | May 9, 07:05 UTC | 1h 55m |
| 2026-05-06 | DATMJ | ZRH → TRF | May 6, 12:10 UTC | May 6, 14:00 UTC | 1h 50m |
| 2026-05-05 | DATMJ | - | May 5, 12:40 UTC | May 5, 13:15 UTC | 35m |
| 2026-05-03 | DATMJ | - | May 3, 18:14 UTC | May 3, 19:40 UTC | 1h 25m |
| 2026-05-01 | DATMJ | - | May 1, 09:20 UTC | May 1, 09:30 UTC | 10m |
| 2026-05-01 | DATMJ | - | May 1, 07:05 UTC | May 1, 08:15 UTC | 1h 10m |
| 2026-04-30 | DATMJ | OBF → MUC | Apr 30, 15:05 UTC | Apr 30, 15:20 UTC | 15m |
| 2026-04-26 | DATMJ | BQH → OBF | Apr 26, 13:20 UTC | Apr 26, 14:40 UTC | 1h 20m |
| 2026-04-26 | DATMJ | GVA → BQH | Apr 26, 11:00 UTC | Apr 26, 12:15 UTC | 1h 15m |
| 2026-04-23 | DATMJ | LIN → GVA | Apr 23, 09:40 UTC | Apr 23, 10:15 UTC | 35m |
| 2026-04-23 | DATMJ | - | Apr 23, 05:05 UTC | Apr 23, 05:45 UTC | 40m |
| 2026-04-22 | DATMJ | BQH → GVA | Apr 22, 11:15 UTC | Apr 22, 12:25 UTC | 1h 10m |
| 2026-04-21 | DATMJ | - | Apr 21, 14:15 UTC | Apr 21, 14:50 UTC | 35m |
| 2026-04-19 | DATMJ | - | Apr 19, 12:05 UTC | Apr 19, 14:25 UTC | 2h 20m |
| 2026-04-17 | DATMJ | - | Apr 17, 13:20 UTC | Apr 17, 13:35 UTC | 15m |
| 2026-04-17 | DATMJ | - | Apr 17, 11:20 UTC | Apr 17, 13:15 UTC | 1h 55m |
| 2026-04-17 | DATMJ | - | Apr 17, 11:05 UTC | Apr 17, 11:15 UTC | 10m |
| 2026-04-15 | DATMJ | - | Apr 15, 09:00 UTC | Apr 15, 10:10 UTC | 1h 10m |
| 2026-04-15 | DATMJ | - | Apr 15, 08:30 UTC | Apr 15, 08:55 UTC | 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.
Prefer a tail-number view? See the D-ATMJ page for operator, model, and routing details .