sensors Mode-S transponder
3FF111
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-MHKD · TL ULTRALIGHT TL-3000 Sirius
- Hex
- 3FF111
- Octal
- 17770421
- Decimal
- 4,190,481
- Country
- DE
- Tail
- D-MHKD
- Type
- TL30
- Flights observed
- 70
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 3FF111 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 |
|---|---|---|---|
| DMHKD | - | 70 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | DMHKD | - | Jul 17, 13:45 UTC | Jul 17, 15:35 UTC | 1h 50m |
| 2026-07-17 | DMHKD | - | Jul 17, 08:59 UTC | Jul 17, 12:19 UTC | 3h 20m |
| 2026-07-16 | DMHKD | - | Jul 16, 10:04 UTC | Jul 16, 12:30 UTC | 2h 25m |
| 2026-07-15 | DMHKD | - | Jul 15, 15:40 UTC | Jul 15, 15:50 UTC | 10m |
| 2026-07-15 | DMHKD | - | Jul 15, 13:50 UTC | Jul 15, 14:40 UTC | 50m |
| 2026-07-15 | DMHKD | - | Jul 15, 08:40 UTC | Jul 15, 09:45 UTC | 1h 5m |
| 2026-07-14 | DMHKD | - | Jul 14, 11:45 UTC | Jul 14, 13:50 UTC | 2h 5m |
| 2026-07-14 | DMHKD | - | Jul 14, 07:30 UTC | Jul 14, 10:15 UTC | 2h 45m |
| 2026-07-12 | DMHKD | - | Jul 12, 16:25 UTC | Jul 12, 17:10 UTC | 45m |
| 2026-07-12 | DMHKD | - | Jul 12, 13:30 UTC | Jul 12, 13:50 UTC | 20m |
| 2026-07-12 | DMHKD | - | Jul 12, 12:01 UTC | Jul 12, 12:35 UTC | 35m |
| 2026-07-12 | DMHKD | - | Jul 12, 08:55 UTC | Jul 12, 09:25 UTC | 30m |
| 2026-06-26 | DMHKD | - | Jun 26, 17:29 UTC | Jun 26, 18:29 UTC | 1h 0m |
| 2026-06-26 | DMHKD | - | Jun 26, 11:55 UTC | Jun 26, 13:30 UTC | 1h 35m |
| 2026-06-26 | DMHKD | - | Jun 26, 08:15 UTC | Jun 26, 08:54 UTC | 40m |
| 2026-06-25 | DMHKD | - | Jun 25, 13:14 UTC | Jun 25, 13:45 UTC | 30m |
| 2026-06-25 | DMHKD | - | Jun 25, 08:50 UTC | Jun 25, 09:34 UTC | 45m |
| 2026-06-24 | DMHKD | - | Jun 24, 12:50 UTC | Jun 24, 13:30 UTC | 40m |
| 2026-06-24 | DMHKD | - | Jun 24, 07:44 UTC | Jun 24, 09:19 UTC | 1h 35m |
| 2026-06-22 | DMHKD | - | Jun 22, 14:19 UTC | Jun 22, 15:10 UTC | 50m |
| 2026-06-22 | DMHKD | - | Jun 22, 08:19 UTC | Jun 22, 09:10 UTC | 50m |
| 2026-06-18 | DMHKD | - | Jun 18, 15:00 UTC | Jun 18, 15:45 UTC | 45m |
| 2026-06-18 | DMHKD | - | Jun 18, 06:05 UTC | Jun 18, 07:00 UTC | 55m |
| 2026-06-16 | DMHKD | - | Jun 16, 16:10 UTC | Jun 16, 17:00 UTC | 50m |
| 2026-06-16 | DMHKD | - | Jun 16, 14:15 UTC | Jun 16, 14:30 UTC | 15m |
| 2026-06-16 | DMHKD | - | Jun 16, 11:05 UTC | Jun 16, 11:55 UTC | 50m |
| 2026-06-16 | DMHKD | - | Jun 16, 08:15 UTC | Jun 16, 08:35 UTC | 20m |
| 2026-06-08 | DMHKD | - | Jun 8, 13:35 UTC | Jun 8, 14:50 UTC | 1h 15m |
| 2026-06-08 | DMHKD | - | Jun 8, 08:15 UTC | Jun 8, 09:10 UTC | 55m |
| 2026-05-30 | DMHKD | - | May 30, 07:50 UTC | May 30, 11:05 UTC | 3h 15m |
| 2026-05-29 | DMHKD | - | May 29, 13:05 UTC | May 29, 14:30 UTC | 1h 25m |
| 2026-05-29 | DMHKD | - | May 29, 09:10 UTC | May 29, 10:35 UTC | 1h 25m |
| 2026-05-28 | DMHKD | - | May 28, 10:05 UTC | May 28, 12:05 UTC | 2h 0m |
| 2026-05-28 | DMHKD | - | May 28, 08:25 UTC | May 28, 09:00 UTC | 35m |
| 2026-05-27 | DMHKD | - | May 27, 11:25 UTC | May 27, 12:35 UTC | 1h 10m |
| 2026-05-27 | DMHKD | - | May 27, 08:00 UTC | May 27, 09:15 UTC | 1h 15m |
| 2026-05-27 | DMHKD | - | May 27, 06:29 UTC | May 27, 07:10 UTC | 40m |
| 2026-05-26 | DMHKD | - | May 26, 12:24 UTC | May 26, 13:45 UTC | 1h 20m |
| 2026-05-26 | DMHKD | - | May 26, 08:59 UTC | May 26, 10:20 UTC | 1h 20m |
| 2026-05-25 | DMHKD | - | May 25, 11:05 UTC | May 25, 11:30 UTC | 25m |
| 2026-05-25 | DMHKD | - | May 25, 08:20 UTC | May 25, 08:45 UTC | 25m |
| 2026-05-24 | DMHKD | - | May 24, 17:45 UTC | May 24, 18:20 UTC | 35m |
| 2026-05-24 | DMHKD | - | May 24, 09:45 UTC | May 24, 10:15 UTC | 30m |
| 2026-05-23 | DMHKD | - | May 23, 18:35 UTC | May 23, 19:10 UTC | 35m |
| 2026-05-23 | DMHKD | - | May 23, 11:40 UTC | May 23, 12:10 UTC | 30m |
| 2026-05-22 | DMHKD | - | May 22, 15:45 UTC | May 22, 17:50 UTC | 2h 5m |
| 2026-05-22 | DMHKD | - | May 22, 08:25 UTC | May 22, 10:20 UTC | 1h 54m |
| 2026-05-10 | DMHKD | - | May 10, 12:25 UTC | May 10, 12:49 UTC | 25m |
| 2026-05-10 | DMHKD | - | May 10, 09:00 UTC | May 10, 10:00 UTC | 1h 0m |
| 2026-05-09 | DMHKD | - | May 9, 14:10 UTC | May 9, 15:45 UTC | 1h 35m |
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-MHKD page for operator, model, and routing details .