sensors Mode-S transponder
3D3D5C
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-EVMI · PIPER PA-28R-180/200/201
- Hex
- 3D3D5C
- Octal
- 17236534
- Decimal
- 4,013,404
- Country
- DE
- Tail
- D-EVMI
- Type
- P28R
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 3D3D5C 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 |
|---|---|---|---|
| DEVMI | - | 50 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | DEVMI | - | May 29, 12:40 UTC | May 29, 12:50 UTC | 10m |
| 2026-05-29 | DEVMI | - | May 29, 10:15 UTC | May 29, 11:45 UTC | 1h 30m |
| 2026-05-29 | DEVMI | - | May 29, 07:10 UTC | May 29, 09:05 UTC | 1h 55m |
| 2026-05-26 | DEVMI | - | May 26, 17:55 UTC | May 26, 18:45 UTC | 50m |
| 2026-05-25 | DEVMI | - | May 25, 17:35 UTC | May 25, 18:45 UTC | 1h 10m |
| 2026-05-25 | DEVMI | - | May 25, 13:45 UTC | May 25, 14:45 UTC | 1h 0m |
| 2026-05-24 | DEVMI | - | May 24, 15:55 UTC | May 24, 16:50 UTC | 55m |
| 2026-05-24 | DEVMI | - | May 24, 07:35 UTC | May 24, 08:40 UTC | 1h 5m |
| 2026-05-22 | DEVMI | - | May 22, 16:15 UTC | May 22, 18:05 UTC | 1h 50m |
| 2026-05-22 | DEVMI | - | May 22, 13:15 UTC | May 22, 15:05 UTC | 1h 50m |
| 2026-05-19 | DEVMI | - | May 19, 09:15 UTC | May 19, 09:50 UTC | 35m |
| 2026-05-18 | DEVMI | - | May 18, 13:15 UTC | May 18, 14:30 UTC | 1h 15m |
| 2026-05-17 | DEVMI | - | May 17, 17:35 UTC | May 17, 17:40 UTC | 5m |
| 2026-05-17 | DEVMI | - | May 17, 12:55 UTC | May 17, 15:20 UTC | 2h 25m |
| 2026-05-17 | DEVMI | - | May 17, 09:55 UTC | May 17, 11:25 UTC | 1h 30m |
| 2026-05-16 | DEVMI | - | May 16, 14:01 UTC | May 16, 14:31 UTC | 30m |
| 2026-05-15 | DEVMI | - | May 15, 15:45 UTC | May 15, 16:30 UTC | 45m |
| 2026-05-15 | DEVMI | - | May 15, 10:25 UTC | May 15, 12:00 UTC | 1h 35m |
| 2026-05-14 | DEVMI | LEI → TTU | May 14, 13:45 UTC | May 14, 15:30 UTC | 1h 45m |
| 2026-05-14 | DEVMI | - | May 14, 11:50 UTC | May 14, 12:00 UTC | 10m |
| 2026-05-13 | DEVMI | - | May 13, 15:40 UTC | May 13, 18:25 UTC | 2h 45m |
| 2026-05-13 | DEVMI | - | May 13, 12:15 UTC | May 13, 14:05 UTC | 1h 50m |
| 2026-05-13 | DEVMI | - | May 13, 07:35 UTC | May 13, 10:40 UTC | 3h 5m |
| 2026-05-12 | DEVMI | - | May 12, 17:00 UTC | May 12, 17:10 UTC | 10m |
| 2026-05-06 | DEVMI | - | May 6, 09:30 UTC | May 6, 09:40 UTC | 10m |
| 2026-05-06 | DEVMI | - | May 6, 06:30 UTC | May 6, 08:20 UTC | 1h 50m |
| 2026-05-04 | DEVMI | - | May 4, 16:35 UTC | May 4, 16:50 UTC | 15m |
| 2026-05-03 | DEVMI | - | May 3, 17:05 UTC | May 3, 17:45 UTC | 40m |
| 2026-05-03 | DEVMI | - | May 3, 13:15 UTC | May 3, 14:00 UTC | 45m |
| 2026-05-02 | DEVMI | - | May 2, 13:25 UTC | May 2, 16:50 UTC | 3h 25m |
| 2026-05-01 | DEVMI | - | May 1, 07:05 UTC | May 1, 10:20 UTC | 3h 15m |
| 2026-04-30 | DEVMI | - | Apr 30, 14:10 UTC | Apr 30, 15:05 UTC | 55m |
| 2026-04-29 | DEVMI | - | Apr 29, 09:05 UTC | Apr 29, 11:05 UTC | 2h 0m |
| 2026-04-26 | DEVMI | - | Apr 26, 15:20 UTC | Apr 26, 16:05 UTC | 45m |
| 2026-04-26 | DEVMI | - | Apr 26, 13:15 UTC | Apr 26, 14:30 UTC | 1h 15m |
| 2026-04-25 | DEVMI | - | Apr 25, 16:40 UTC | Apr 25, 18:00 UTC | 1h 20m |
| 2026-04-25 | DEVMI | - | Apr 25, 06:35 UTC | Apr 25, 08:00 UTC | 1h 25m |
| 2026-04-24 | DEVMI | - | Apr 24, 17:30 UTC | Apr 24, 18:50 UTC | 1h 20m |
| 2026-04-23 | DEVMI | - | Apr 23, 08:01 UTC | Apr 23, 09:35 UTC | 1h 35m |
| 2026-04-22 | DEVMI | - | Apr 22, 17:40 UTC | Apr 22, 18:40 UTC | 1h 0m |
| 2026-04-22 | DEVMI | - | Apr 22, 15:30 UTC | Apr 22, 16:40 UTC | 1h 10m |
| 2026-04-22 | DEVMI | - | Apr 22, 07:05 UTC | Apr 22, 07:50 UTC | 45m |
| 2026-04-21 | DEVMI | - | Apr 21, 15:45 UTC | Apr 21, 16:25 UTC | 40m |
| 2026-04-21 | DEVMI | - | Apr 21, 13:01 UTC | Apr 21, 13:50 UTC | 50m |
| 2026-04-21 | DEVMI | - | Apr 21, 11:25 UTC | Apr 21, 12:20 UTC | 55m |
| 2026-04-18 | DEVMI | - | Apr 18, 17:10 UTC | Apr 18, 18:05 UTC | 55m |
| 2026-04-18 | DEVMI | - | Apr 18, 08:30 UTC | Apr 18, 09:30 UTC | 1h 0m |
| 2026-04-13 | DEVMI | - | Apr 13, 09:10 UTC | Apr 13, 10:00 UTC | 50m |
| 2026-04-13 | DEVMI | - | Apr 13, 07:45 UTC | Apr 13, 08:10 UTC | 25m |
| 2026-04-12 | DEVMI | - | Apr 12, 17:15 UTC | Apr 12, 18:15 UTC | 1h 0m |
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-EVMI page for operator, model, and routing details .