sensors Mode-S transponder
3C6564
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AIKD · AIRBUS A-330-300
- Hex
- 3C6564
- Octal
- 17062544
- Decimal
- 3,958,116
- Country
- DE
- Tail
- D-AIKD
- Type
- A333
- Flights observed
- 161
- Distinct callsigns
- 20
- Country
- DE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 3C6564 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 |
|---|---|---|---|
| OCN133 | - | 13 | 2026-07-13 |
| OCN132W | - | 13 | 2026-07-11 |
| OCN76 | - | 12 | 2026-07-14 |
| OCN135K | - | 12 | 2026-06-25 |
| OCN12 | - | 11 | 2026-07-07 |
| OCN11 | - | 11 | 2026-07-06 |
| OCN77 | O Air | 8 | 2026-05-12 |
| OCN137 | - | 8 | 2026-06-30 |
| OCN539 | - | 6 | 2026-07-13 |
| OCN131 | - | 6 | 2026-07-10 |
| OCN69 | - | 5 | 2026-07-10 |
| OCN68 | - | 5 | 2026-07-09 |
| OCN659 | - | 5 | 2026-07-05 |
| OCN642 | - | 5 | 2026-07-05 |
| OCN52 | - | 5 | 2026-07-13 |
| OCN5 | - | 5 | 2026-04-22 |
| OCN51 | - | 4 | 2026-07-03 |
| OCN50 | O Air | 4 | 2026-07-03 |
| OCN74 | O Air | 3 | 2026-05-10 |
| OCN3 | O Air | 3 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | OCN76 | FRA → YYC | Jul 14, 11:55 UTC | Jul 14, 21:05 UTC | 9h 10m |
| 2026-07-13 | OCN539 | MSP → FRA | Jul 13, 21:00 UTC | Jul 14, 05:20 UTC | 8h 20m |
| 2026-07-13 | OCN52 | FRA → MSP | Jul 13, 10:15 UTC | Jul 13, 18:55 UTC | 8h 40m |
| 2026-07-13 | OCN133 | - | Jul 13, 01:10 UTC | Jul 13, 03:05 UTC | 1h 55m |
| 2026-07-12 | OCN133 | - | Jul 12, 03:45 UTC | Jul 13, 03:01 UTC | 23h 15m |
| 2026-07-11 | OCN132W | - | Jul 11, 20:35 UTC | Jul 12, 04:30 UTC | 7h 55m |
| 2026-07-10 | OCN131 | - | Jul 10, 21:05 UTC | Jul 11, 15:50 UTC | 18h 45m |
| 2026-07-10 | OCN131 | - | Jul 10, 19:05 UTC | Jul 11, 15:50 UTC | 20h 45m |
| 2026-07-10 | OCN69 | MCO → FRA | Jul 10, 01:35 UTC | Jul 10, 10:10 UTC | 8h 35m |
| 2026-07-09 | OCN68 | FRA → MCO | Jul 9, 12:55 UTC | Jul 9, 22:30 UTC | 9h 35m |
| 2026-07-07 | OCN12 | - | Jul 7, 04:15 UTC | Jul 7, 14:15 UTC | 10h 0m |
| 2026-07-06 | OCN11 | - | Jul 6, 12:10 UTC | Jul 6, 23:35 UTC | 11h 25m |
| 2026-07-05 | OCN659 | TPA → FRA | Jul 5, 22:05 UTC | Jul 6, 06:45 UTC | 8h 40m |
| 2026-07-05 | OCN642 | FRA → TPA | Jul 5, 09:55 UTC | Jul 5, 19:40 UTC | 9h 45m |
| 2026-07-04 | OCN659 | TPA → FRA | Jul 4, 22:10 UTC | Jul 5, 06:55 UTC | 8h 45m |
| 2026-07-04 | OCN642 | FRA → TPA | Jul 4, 10:35 UTC | Jul 4, 20:20 UTC | 9h 45m |
| 2026-07-03 | OCN51 | - | Jul 3, 22:00 UTC | Jul 4, 04:55 UTC | 6h 55m |
| 2026-07-03 | OCN50 | FRA → PHL | Jul 3, 11:35 UTC | Jul 3, 20:00 UTC | 8h 25m |
| 2026-07-03 | OCN133 | - | Jul 3, 00:45 UTC | Jul 3, 03:10 UTC | 2h 25m |
| 2026-07-02 | OCN133 | - | Jul 2, 03:55 UTC | Jul 3, 03:00 UTC | 23h 5m |
| 2026-07-01 | OCN132W | FRA → WDH | Jul 1, 20:30 UTC | Jul 2, 04:35 UTC | 8h 5m |
| 2026-06-30 | OCN137 | - | Jun 30, 21:10 UTC | Jul 1, 16:55 UTC | 19h 45m |
| 2026-06-30 | OCN137 | - | Jun 30, 19:05 UTC | Jul 1, 16:55 UTC | 21h 50m |
| 2026-06-30 | OCN136 | FRA → FRA | Jun 30, 17:50 UTC | Jul 1, 16:55 UTC | 23h 5m |
| 2026-06-30 | OCN12 | LAS → FRA | Jun 30, 04:15 UTC | Jun 30, 14:10 UTC | 9h 55m |
| 2026-06-29 | OCN11 | FRA → LAS | Jun 29, 12:34 UTC | Jun 29, 23:14 UTC | 10h 40m |
| 2026-06-28 | OCN659 | TPA → FRA | Jun 28, 22:04 UTC | Jun 29, 06:34 UTC | 8h 30m |
| 2026-06-28 | OCN642 | FRA → TPA | Jun 28, 10:00 UTC | Jun 28, 20:04 UTC | 10h 5m |
| 2026-06-28 | OCN133 | - | Jun 28, 01:15 UTC | Jun 28, 03:09 UTC | 1h 55m |
| 2026-06-26 | OCN132W | FRA → WDH | Jun 26, 20:29 UTC | Jun 26, 22:10 UTC | 1h 40m |
| 2026-06-25 | OCN135K | - | Jun 25, 19:05 UTC | Jun 26, 16:30 UTC | 21h 25m |
| 2026-06-25 | OCN135K | FRA → FRA | Jun 25, 18:15 UTC | Jun 26, 16:30 UTC | 22h 15m |
| 2026-06-25 | OCN12 | LAS → FRA | Jun 25, 04:35 UTC | Jun 25, 14:55 UTC | 10h 20m |
| 2026-06-24 | OCN11 | FRA → LAS | Jun 24, 12:14 UTC | Jun 24, 23:24 UTC | 11h 10m |
| 2026-06-22 | OCN539 | MSP → FRA | Jun 22, 21:25 UTC | Jun 23, 05:24 UTC | 8h 0m |
| 2026-06-22 | OCN52 | FRA → MSP | Jun 22, 10:19 UTC | Jun 22, 19:09 UTC | 8h 50m |
| 2026-06-21 | OCN12 | LAS → FRA | Jun 21, 05:00 UTC | Jun 21, 15:15 UTC | 10h 15m |
| 2026-06-20 | OCN11 | FRA → LAS | Jun 20, 12:24 UTC | Jun 20, 23:19 UTC | 10h 55m |
| 2026-06-19 | OCN659 | - | Jun 19, 22:30 UTC | Jun 20, 07:00 UTC | 8h 30m |
| 2026-06-19 | OCN642 | FRA → TPA | Jun 19, 10:09 UTC | Jun 19, 20:04 UTC | 9h 55m |
| 2026-06-18 | OCN51 | - | Jun 18, 22:45 UTC | Jun 19, 05:49 UTC | 7h 4m |
| 2026-06-18 | OCN50 | FRA → PHL | Jun 18, 12:10 UTC | Jun 18, 20:30 UTC | 8h 20m |
| 2026-06-16 | OCN131 | MBA → FRA | Jun 16, 19:05 UTC | Jun 17, 14:35 UTC | 19h 31m |
| 2026-06-16 | OCN12 | LAS → FRA | Jun 16, 04:15 UTC | Jun 16, 14:55 UTC | 10h 40m |
| 2026-06-15 | OCN11 | CUN → FRA | Jun 15, 12:10 UTC | Jun 15, 22:54 UTC | 10h 45m |
| 2026-06-14 | OCN12 | LAS → FRA | Jun 14, 05:05 UTC | Jun 14, 15:20 UTC | 10h 15m |
| 2026-06-13 | OCN11 | CUN → FRA | Jun 13, 12:20 UTC | Jun 13, 23:10 UTC | 10h 50m |
| 2026-06-12 | OCN539 | MSP → FRA | Jun 12, 22:45 UTC | Jun 13, 06:50 UTC | 8h 4m |
| 2026-06-12 | OCN52 | FRA → MSP | Jun 12, 09:55 UTC | Jun 12, 18:55 UTC | 9h 0m |
| 2026-06-12 | OCN133 | - | Jun 12, 01:50 UTC | Jun 12, 03:55 UTC | 2h 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-AIKD page for operator, model, and routing details .