sensors Mode-S transponder
4D2444
ICAO 24-bit transponder address
Currently assigned to 9H-DGN · DIAMOND DA-62
- Hex
- 4D2444
- Octal
- 23222104
- Decimal
- 5,055,556
- Tail
- 9H-DGN
- Type
- DA62
- Flights observed
- 32
- Distinct callsigns
- 3
- Country
- -
- Last broadcast
- 7d ago
Last known position
Callsign history 3 distinct
Recent flights last 32
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | OSPREY1 | - | Jul 22, 17:05 UTC | Jul 22, 17:20 UTC | 15m |
| 2026-07-22 | OSPREY1 | - | Jul 22, 00:00 UTC | Jul 22, 00:15 UTC | 15m |
| 2026-07-21 | OSPREY1 | - | Jul 21, 17:05 UTC | Jul 21, 17:25 UTC | 20m |
| 2026-07-20 | OSPREY1 | - | Jul 20, 10:55 UTC | Jul 20, 11:15 UTC | 20m |
| 2026-07-17 | EKT31 | - | Jul 17, 08:25 UTC | Jul 17, 10:00 UTC | 1h 35m |
| 2026-07-13 | EKT31 | - | Jul 13, 02:15 UTC | Jul 13, 04:50 UTC | 2h 35m |
| 2026-07-11 | OSPREY1 | - | Jul 11, 17:50 UTC | Jul 11, 18:05 UTC | 15m |
| 2026-07-11 | OSPREY1 | - | Jul 11, 14:10 UTC | Jul 11, 14:25 UTC | 15m |
| 2026-07-10 | OSPREY1 | - | Jul 10, 18:50 UTC | Jul 10, 19:05 UTC | 15m |
| 2026-07-10 | OSPREY1 | - | Jul 10, 15:10 UTC | Jul 10, 15:25 UTC | 15m |
| 2026-07-08 | OSPREY1 | - | Jul 8, 14:30 UTC | Jul 8, 14:50 UTC | 20m |
| 2026-07-08 | OSPREY1 | - | Jul 8, 11:55 UTC | Jul 8, 12:25 UTC | 30m |
| 2026-07-06 | OSPREY1 | - | Jul 6, 07:00 UTC | Jul 6, 07:15 UTC | 15m |
| 2026-07-03 | OSPREY1 | - | Jul 3, 14:40 UTC | Jul 3, 14:55 UTC | 15m |
| 2026-07-03 | OSPREY1 | - | Jul 3, 11:05 UTC | Jul 3, 11:25 UTC | 20m |
| 2026-07-02 | OSPREY1 | - | Jul 2, 18:30 UTC | Jul 2, 18:55 UTC | 25m |
| 2026-07-02 | OSPREY1 | - | Jul 2, 14:05 UTC | Jul 2, 14:25 UTC | 20m |
| 2026-07-01 | OSPREY1 | - | Jul 1, 11:15 UTC | Jul 1, 11:30 UTC | 15m |
| 2026-06-26 | OSPREY1 | - | Jun 26, 19:24 UTC | Jun 26, 19:35 UTC | 10m |
| 2026-06-26 | OSPREY1 | - | Jun 26, 14:05 UTC | Jun 26, 14:15 UTC | 10m |
| 2026-06-25 | OSPREY1 | - | Jun 25, 18:34 UTC | Jun 25, 18:50 UTC | 15m |
| 2026-06-24 | OSPREY1 | - | Jun 24, 18:34 UTC | Jun 24, 18:50 UTC | 15m |
| 2026-06-24 | OSPREY1 | - | Jun 24, 14:09 UTC | Jun 24, 14:24 UTC | 15m |
| 2026-06-22 | OSPREY1 | - | Jun 22, 08:44 UTC | Jun 22, 09:00 UTC | 15m |
| 2026-06-19 | EKT43 | - | Jun 19, 14:44 UTC | Jun 19, 16:19 UTC | 1h 35m |
| 2026-06-19 | EKT43 | LMP → MLA | Jun 19, 06:44 UTC | Jun 19, 07:39 UTC | 55m |
| 2026-06-15 | OSPREY1 | - | Jun 15, 11:10 UTC | Jun 15, 11:30 UTC | 20m |
| 2026-06-14 | OSPREY1 | - | Jun 14, 14:40 UTC | Jun 14, 16:00 UTC | 1h 20m |
| 2026-06-14 | OSPREY1 | - | Jun 14, 10:55 UTC | Jun 14, 11:10 UTC | 15m |
| 2026-06-13 | OSPREY1 | - | Jun 13, 04:40 UTC | Jun 13, 04:50 UTC | 10m |
| 2026-06-12 | EKT43 | - | Jun 12, 15:20 UTC | Jun 12, 16:05 UTC | 45m |
| 2026-06-12 | EKT43 | MLA → MLA | Jun 12, 13:45 UTC | Jun 12, 14:30 UTC | 45m |
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 9H-DGN page for operator, model, and routing details .