sensors Mode-S transponder
AE5F0D
ICAO 24-bit transponder address
Currently assigned to 16-5859 · Lockheed Martin C-130J-30 Hercules
- Hex
- AE5F0D
- Octal
- 53457415
- Decimal
- 11,427,597
- Tail
- 16-5859
- Type
- C30J
- Flights observed
- 31
- Distinct callsigns
- 8
- Country
- -
- Last broadcast
- 3d ago
Last known position
Callsign history 8 distinct
Recent flights last 31
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | DERBY82 | - | Jul 10, 17:20 UTC | Jul 10, 22:40 UTC | 5h 21m |
| 2026-07-09 | DERBY82 | - | Jul 9, 02:00 UTC | Jul 9, 05:50 UTC | 3h 50m |
| 2026-07-09 | DERBY82 | EIL → FRN | Jul 9, 00:50 UTC | Jul 9, 01:40 UTC | 50m |
| 2026-07-08 | DERBY82 | - | Jul 8, 17:30 UTC | Jul 8, 23:10 UTC | 5h 40m |
| 2026-07-07 | DERBY82 | - | Jul 7, 14:30 UTC | Jul 7, 19:05 UTC | 4h 35m |
| 2026-06-26 | DERBY81 | - | Jun 26, 15:29 UTC | Jun 26, 18:20 UTC | 2h 50m |
| 2026-06-25 | DERBY81 | - | Jun 25, 21:29 UTC | Jun 25, 22:45 UTC | 1h 15m |
| 2026-06-25 | DERBY81 | - | Jun 25, 10:09 UTC | Jun 25, 10:59 UTC | 50m |
| 2026-06-24 | DERBY81 | - | Jun 24, 07:59 UTC | Jun 24, 09:49 UTC | 1h 50m |
| 2026-06-22 | DERBY83 | - | Jun 22, 17:10 UTC | Jun 22, 17:29 UTC | 20m |
| 2026-06-22 | DERBY83 | - | Jun 22, 15:50 UTC | Jun 22, 16:10 UTC | 20m |
| 2026-06-22 | DERBY81 | - | Jun 22, 09:40 UTC | Jun 22, 10:55 UTC | 1h 15m |
| 2026-06-16 | DERBY81 | - | Jun 16, 16:30 UTC | Jun 16, 18:55 UTC | 2h 25m |
| 2026-06-16 | DERB81 | - | Jun 16, 08:05 UTC | Jun 16, 08:49 UTC | 45m |
| 2026-06-15 | DERBY82 | - | Jun 15, 10:30 UTC | Jun 15, 14:24 UTC | 3h 55m |
| 2026-06-15 | DERBY82 | - | Jun 15, 07:29 UTC | Jun 15, 09:00 UTC | 1h 30m |
| 2026-06-10 | DERBY81 | - | Jun 10, 07:55 UTC | Jun 10, 08:10 UTC | 15m |
| 2026-06-09 | DERBY82 | - | Jun 9, 12:55 UTC | Jun 9, 13:45 UTC | 50m |
| 2026-06-09 | DERBY82 | - | Jun 9, 10:20 UTC | Jun 9, 11:30 UTC | 1h 10m |
| 2026-06-08 | DERBY81 | - | Jun 8, 11:00 UTC | Jun 8, 13:10 UTC | 2h 10m |
| 2026-06-08 | DERBY81 | - | Jun 8, 08:10 UTC | Jun 8, 09:00 UTC | 50m |
| 2026-05-31 | DERBY81 | - | May 31, 09:20 UTC | May 31, 10:55 UTC | 1h 35m |
| 2026-05-29 | DERBY81 | - | May 29, 15:05 UTC | May 29, 15:55 UTC | 50m |
| 2026-05-28 | DERBY81 | - | May 28, 15:20 UTC | May 29, 15:15 UTC | 23h 55m |
| 2026-05-28 | DERBY81 | - | May 28, 12:40 UTC | May 28, 16:45 UTC | 4h 5m |
| 2026-05-19 | DERBY21 | - | May 19, 17:20 UTC | May 19, 17:35 UTC | 15m |
| 2026-05-15 | DERBY31 | - | May 15, 02:25 UTC | May 15, 02:35 UTC | 10m |
| 2026-05-14 | DERBY21 | - | May 14, 18:50 UTC | May 14, 19:10 UTC | 20m |
| 2026-05-14 | DERBY21 | - | May 14, 16:25 UTC | May 14, 16:50 UTC | 25m |
| 2026-05-13 | DERBY22 | - | May 13, 18:05 UTC | May 13, 19:15 UTC | 1h 10m |
| 2026-05-12 | DERBY23 | - | May 12, 17:30 UTC | May 12, 18:50 UTC | 1h 20m |
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 16-5859 page for operator, model, and routing details .