sensors Mode-S transponder
3FF76E
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-MOCT · FLIGHT DESIGN CT
- Hex
- 3FF76E
- Octal
- 17773556
- Decimal
- 4,192,110
- Country
- DE
- Tail
- D-MOCT
- Type
- FDCT
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 3FF76E 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 |
|---|---|---|---|
| DMOCT | - | 55 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | DMOCT | - | Jul 26, 09:40 UTC | Jul 26, 11:00 UTC | 1h 20m |
| 2026-07-24 | DMOCT | - | Jul 24, 15:00 UTC | Jul 24, 16:25 UTC | 1h 25m |
| 2026-07-21 | DMOCT | - | Jul 21, 09:45 UTC | Jul 21, 09:55 UTC | 10m |
| 2026-07-21 | DMOCT | - | Jul 21, 06:00 UTC | Jul 21, 06:35 UTC | 35m |
| 2026-07-20 | DMOCT | - | Jul 20, 10:30 UTC | Jul 20, 10:50 UTC | 20m |
| 2026-07-19 | DMOCT | - | Jul 19, 05:00 UTC | Jul 19, 05:20 UTC | 20m |
| 2026-07-11 | DMOCT | - | Jul 11, 14:55 UTC | Jul 11, 15:25 UTC | 30m |
| 2026-07-11 | DMOCT | - | Jul 11, 11:30 UTC | Jul 11, 12:00 UTC | 30m |
| 2026-06-28 | DMOCT | - | Jun 28, 15:34 UTC | Jun 28, 16:19 UTC | 45m |
| 2026-06-28 | DMOCT | - | Jun 28, 13:34 UTC | Jun 28, 14:25 UTC | 50m |
| 2026-06-28 | DMOCT | - | Jun 28, 08:50 UTC | Jun 28, 10:24 UTC | 1h 35m |
| 2026-06-26 | DMOCT | - | Jun 26, 17:15 UTC | Jun 26, 18:29 UTC | 1h 15m |
| 2026-06-26 | DMOCT | - | Jun 26, 09:39 UTC | Jun 26, 11:05 UTC | 1h 25m |
| 2026-06-23 | DMOCT | - | Jun 23, 17:09 UTC | Jun 23, 19:19 UTC | 2h 10m |
| 2026-06-23 | DMOCT | - | Jun 23, 07:09 UTC | Jun 23, 07:29 UTC | 20m |
| 2026-06-22 | DMOCT | - | Jun 22, 13:10 UTC | Jun 22, 13:54 UTC | 45m |
| 2026-06-22 | DMOCT | - | Jun 22, 11:24 UTC | Jun 22, 12:15 UTC | 50m |
| 2026-06-21 | DMOCT | - | Jun 21, 16:25 UTC | Jun 21, 17:15 UTC | 50m |
| 2026-06-20 | DMOCT | - | Jun 20, 14:05 UTC | Jun 20, 15:09 UTC | 1h 5m |
| 2026-06-19 | DMOCT | - | Jun 19, 12:34 UTC | Jun 19, 13:54 UTC | 1h 20m |
| 2026-06-19 | DMOCT | - | Jun 19, 08:50 UTC | Jun 19, 09:14 UTC | 25m |
| 2026-06-19 | DMOCT | - | Jun 19, 07:49 UTC | Jun 19, 08:14 UTC | 25m |
| 2026-06-18 | DMOCT | - | Jun 18, 17:35 UTC | Jun 18, 18:00 UTC | 25m |
| 2026-06-16 | DMOCT | - | Jun 16, 17:49 UTC | Jun 16, 18:39 UTC | 50m |
| 2026-06-11 | DMOCT | - | Jun 11, 17:20 UTC | Jun 11, 17:55 UTC | 35m |
| 2026-06-11 | DMOCT | - | Jun 11, 16:25 UTC | Jun 11, 16:40 UTC | 15m |
| 2026-06-11 | DMOCT | - | Jun 11, 14:30 UTC | Jun 11, 15:45 UTC | 1h 15m |
| 2026-06-08 | DMOCT | - | Jun 8, 09:15 UTC | Jun 8, 09:45 UTC | 30m |
| 2026-06-07 | DMOCT | - | Jun 7, 08:40 UTC | Jun 7, 09:00 UTC | 20m |
| 2026-06-06 | DMOCT | - | Jun 6, 07:25 UTC | Jun 6, 08:50 UTC | 1h 25m |
| 2026-06-03 | DMOCT | - | Jun 3, 18:05 UTC | Jun 3, 18:25 UTC | 20m |
| 2026-05-31 | DMOCT | - | May 31, 14:30 UTC | May 31, 15:30 UTC | 1h 0m |
| 2026-05-31 | DMOCT | - | May 31, 10:45 UTC | May 31, 11:20 UTC | 35m |
| 2026-05-31 | DMOCT | - | May 31, 08:35 UTC | May 31, 09:35 UTC | 1h 0m |
| 2026-05-30 | DMOCT | - | May 30, 18:25 UTC | May 30, 19:25 UTC | 1h 0m |
| 2026-05-19 | DMOCT | - | May 19, 14:15 UTC | May 19, 16:00 UTC | 1h 45m |
| 2026-05-16 | DMOCT | - | May 16, 17:01 UTC | May 16, 18:35 UTC | 1h 35m |
| 2026-05-16 | DMOCT | - | May 16, 08:20 UTC | May 16, 10:16 UTC | 1h 55m |
| 2026-05-14 | DMOCT | - | May 14, 09:20 UTC | May 14, 09:30 UTC | 10m |
| 2026-05-14 | DMOCT | - | May 14, 08:00 UTC | May 14, 08:50 UTC | 50m |
| 2026-05-09 | DMOCT | - | May 9, 16:35 UTC | May 9, 16:55 UTC | 20m |
| 2026-05-07 | DMOCT | - | May 7, 13:10 UTC | May 7, 14:00 UTC | 50m |
| 2026-05-07 | DMOCT | - | May 7, 10:20 UTC | May 7, 11:10 UTC | 50m |
| 2026-05-06 | DMOCT | - | May 6, 14:40 UTC | May 6, 15:35 UTC | 55m |
| 2026-05-06 | DMOCT | - | May 6, 12:40 UTC | May 6, 13:50 UTC | 1h 10m |
| 2026-05-02 | DMOCT | - | May 2, 10:15 UTC | May 2, 11:05 UTC | 50m |
| 2026-05-01 | DMOCT | - | May 1, 15:40 UTC | May 1, 16:45 UTC | 1h 5m |
| 2026-05-01 | DMOCT | - | May 1, 09:35 UTC | May 1, 10:05 UTC | 30m |
| 2026-05-01 | DMOCT | - | May 1, 08:15 UTC | May 1, 08:40 UTC | 25m |
| 2026-04-30 | DMOCT | - | Apr 30, 15:30 UTC | Apr 30, 16:55 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.
Prefer a tail-number view? See the D-MOCT page for operator, model, and routing details .