sensors Mode-S transponder
3FF0DB
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-MAPO · B&F TECHNIK FK-9
- Hex
- 3FF0DB
- Octal
- 17770333
- Decimal
- 4,190,427
- Country
- DE
- Tail
- D-MAPO
- Type
- FK9
- Flights observed
- 70
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 3FF0DB 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 |
|---|---|---|---|
| DMMFQ | - | 70 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | DMMFQ | - | Jul 17, 18:50 UTC | Jul 17, 19:55 UTC | 1h 5m |
| 2026-07-17 | DMMFQ | - | Jul 17, 17:15 UTC | Jul 17, 17:25 UTC | 10m |
| 2026-07-16 | DMMFQ | - | Jul 16, 15:14 UTC | Jul 16, 15:45 UTC | 30m |
| 2026-07-16 | DMMFQ | - | Jul 16, 13:54 UTC | Jul 16, 14:15 UTC | 20m |
| 2026-07-16 | DMMFQ | - | Jul 16, 12:25 UTC | Jul 16, 13:15 UTC | 50m |
| 2026-07-15 | DMMFQ | - | Jul 15, 15:10 UTC | Jul 15, 15:20 UTC | 10m |
| 2026-07-14 | DMMFQ | - | Jul 14, 15:20 UTC | Jul 14, 15:30 UTC | 10m |
| 2026-07-14 | DMMFQ | - | Jul 14, 14:00 UTC | Jul 14, 14:40 UTC | 40m |
| 2026-07-11 | DMMFQ | - | Jul 11, 10:20 UTC | Jul 11, 11:00 UTC | 40m |
| 2026-07-11 | DMMFQ | - | Jul 11, 08:45 UTC | Jul 11, 09:25 UTC | 40m |
| 2026-07-09 | DMMFQ | - | Jul 9, 17:10 UTC | Jul 9, 17:50 UTC | 40m |
| 2026-07-09 | DMMFQ | - | Jul 9, 14:05 UTC | Jul 9, 14:35 UTC | 30m |
| 2026-07-03 | DMMFQ | - | Jul 3, 11:40 UTC | Jul 3, 12:05 UTC | 25m |
| 2026-07-03 | DMMFQ | - | Jul 3, 10:15 UTC | Jul 3, 10:40 UTC | 25m |
| 2026-07-02 | DMMFQ | - | Jul 2, 15:00 UTC | Jul 2, 15:20 UTC | 20m |
| 2026-06-30 | DMMFQ | - | Jun 30, 14:10 UTC | Jun 30, 14:50 UTC | 40m |
| 2026-06-20 | DMMFQ | - | Jun 20, 09:39 UTC | Jun 20, 10:09 UTC | 30m |
| 2026-06-20 | DMMFQ | HOQ → HOQ | Jun 20, 07:54 UTC | Jun 20, 08:34 UTC | 40m |
| 2026-06-19 | DMMFQ | - | Jun 19, 15:29 UTC | Jun 19, 16:39 UTC | 1h 10m |
| 2026-06-19 | DMMFQ | - | Jun 19, 13:20 UTC | Jun 19, 14:15 UTC | 55m |
| 2026-06-19 | DMMFQ | - | Jun 19, 09:19 UTC | Jun 19, 10:29 UTC | 1h 10m |
| 2026-06-19 | DMMFQ | - | Jun 19, 07:09 UTC | Jun 19, 08:24 UTC | 1h 15m |
| 2026-06-18 | DMMFQ | - | Jun 18, 15:05 UTC | Jun 18, 15:35 UTC | 30m |
| 2026-06-17 | DMMFQ | - | Jun 17, 10:20 UTC | Jun 17, 11:05 UTC | 45m |
| 2026-06-05 | DMMFQ | - | Jun 5, 14:45 UTC | Jun 5, 15:25 UTC | 40m |
| 2026-05-28 | DMMFQ | - | May 28, 16:55 UTC | May 28, 17:30 UTC | 35m |
| 2026-05-28 | DMMFQ | - | May 28, 15:30 UTC | May 28, 16:20 UTC | 50m |
| 2026-05-28 | DMMFQ | - | May 28, 11:50 UTC | May 28, 12:40 UTC | 50m |
| 2026-05-24 | DMMFQ | - | May 24, 08:55 UTC | May 24, 10:45 UTC | 1h 50m |
| 2026-05-23 | DMMFQ | - | May 23, 07:10 UTC | May 23, 10:40 UTC | 3h 30m |
| 2026-05-22 | DMMFQ | - | May 22, 10:30 UTC | May 22, 10:55 UTC | 25m |
| 2026-05-22 | DMMFQ | - | May 22, 09:45 UTC | May 22, 10:10 UTC | 25m |
| 2026-05-21 | DMMFQ | - | May 21, 15:00 UTC | May 21, 17:00 UTC | 2h 0m |
| 2026-05-19 | DMMFQ | - | May 19, 14:45 UTC | May 19, 15:30 UTC | 45m |
| 2026-05-18 | DMMFQ | - | May 18, 12:20 UTC | May 18, 12:40 UTC | 20m |
| 2026-05-17 | DMMFQ | - | May 17, 15:40 UTC | May 17, 16:40 UTC | 1h 0m |
| 2026-05-17 | DMMFQ | - | May 17, 11:10 UTC | May 17, 12:10 UTC | 1h 0m |
| 2026-05-16 | DMMFQ | - | May 16, 07:51 UTC | May 16, 09:51 UTC | 2h 0m |
| 2026-05-09 | DMMFQ | - | May 9, 13:25 UTC | May 9, 13:45 UTC | 20m |
| 2026-05-09 | DMMFQ | - | May 9, 11:35 UTC | May 9, 12:40 UTC | 1h 5m |
| 2026-05-09 | DMMFQ | - | May 9, 10:30 UTC | May 9, 10:55 UTC | 25m |
| 2026-05-08 | DMMFQ | - | May 8, 17:20 UTC | May 8, 17:35 UTC | 15m |
| 2026-05-08 | DMMFQ | - | May 8, 14:30 UTC | May 8, 15:50 UTC | 1h 20m |
| 2026-05-08 | DMMFQ | - | May 8, 13:25 UTC | May 8, 13:50 UTC | 25m |
| 2026-05-06 | DMMFQ | - | May 6, 14:30 UTC | May 6, 14:55 UTC | 25m |
| 2026-05-06 | DMMFQ | - | May 6, 11:35 UTC | May 6, 13:20 UTC | 1h 45m |
| 2026-05-05 | DMMFQ | HOQ → HOQ | May 5, 14:15 UTC | May 5, 14:55 UTC | 40m |
| 2026-05-04 | DMMFQ | - | May 4, 14:40 UTC | May 4, 16:55 UTC | 2h 15m |
| 2026-05-03 | DMMFQ | - | May 3, 15:35 UTC | May 3, 16:15 UTC | 40m |
| 2026-05-03 | DMMFQ | - | May 3, 11:25 UTC | May 3, 14:35 UTC | 3h 10m |
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-MAPO page for operator, model, and routing details .