sensors Mode-S transponder
AE5735
ICAO 24-bit transponder address
Currently assigned to 169018 · Lockheed Martin KC-130J Hercules
- Hex
- AE5735
- Octal
- 53453465
- Decimal
- 11,425,589
- Tail
- 169018
- Type
- C30J
- Flights observed
- 60
- Distinct callsigns
- 7
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | RANGR91 | - | Jul 16, 19:45 UTC | Jul 16, 20:25 UTC | 40m |
| 2026-07-16 | RANGR91 | - | Jul 16, 11:45 UTC | Jul 16, 13:25 UTC | 1h 40m |
| 2026-07-16 | RANGR91 | - | Jul 16, 07:05 UTC | Jul 16, 09:25 UTC | 2h 20m |
| 2026-07-15 | RANGR92 | - | Jul 15, 09:55 UTC | Jul 15, 11:50 UTC | 1h 55m |
| 2026-07-14 | RANGR92 | - | Jul 14, 09:15 UTC | Jul 14, 12:45 UTC | 3h 30m |
| 2026-07-13 | RANGR92 | - | Jul 13, 13:25 UTC | Jul 13, 15:25 UTC | 2h 0m |
| 2026-07-13 | RANGR92 | - | Jul 13, 11:10 UTC | Jul 13, 11:25 UTC | 15m |
| 2026-07-10 | RANGR92 | - | Jul 10, 11:10 UTC | Jul 10, 13:45 UTC | 2h 35m |
| 2026-07-09 | RANGR92 | - | Jul 9, 18:10 UTC | Jul 9, 19:35 UTC | 1h 25m |
| 2026-07-08 | RANGR92 | - | Jul 8, 14:55 UTC | Jul 8, 21:50 UTC | 6h 55m |
| 2026-07-01 | RANGR55 | - | Jul 1, 18:25 UTC | Jul 1, 20:30 UTC | 2h 5m |
| 2026-07-01 | RANGR36 | - | Jul 1, 01:20 UTC | Jul 1, 06:00 UTC | 4h 40m |
| 2026-06-30 | RANGR36 | - | Jun 30, 01:19 UTC | Jun 30, 05:15 UTC | 3h 56m |
| 2026-06-27 | RANGR55 | - | Jun 27, 22:25 UTC | Jun 28, 00:15 UTC | 1h 50m |
| 2026-06-27 | RANGR55 | - | Jun 27, 16:10 UTC | Jun 27, 21:10 UTC | 5h 0m |
| 2026-06-26 | RANGR55 | - | Jun 26, 17:59 UTC | Jun 26, 20:40 UTC | 2h 40m |
| 2026-06-21 | RANGR91 | - | Jun 21, 15:44 UTC | Jun 21, 21:14 UTC | 5h 30m |
| 2026-06-20 | RANGR91 | - | Jun 20, 17:29 UTC | Jun 20, 19:40 UTC | 2h 10m |
| 2026-06-20 | RANGR91 | - | Jun 20, 07:39 UTC | Jun 20, 09:34 UTC | 1h 55m |
| 2026-06-19 | RANGR91 | - | Jun 19, 08:09 UTC | Jun 19, 13:04 UTC | 4h 55m |
| 2026-06-18 | RANGR91 | - | Jun 18, 10:20 UTC | Jun 18, 14:50 UTC | 4h 30m |
| 2026-06-17 | RANGR91 | MHZ → MHZ | Jun 17, 11:10 UTC | Jun 17, 11:40 UTC | 30m |
| 2026-06-15 | RANGR91 | - | Jun 15, 10:15 UTC | Jun 15, 15:15 UTC | 5h 0m |
| 2026-06-14 | RANGR92 | - | Jun 14, 09:20 UTC | Jun 14, 11:35 UTC | 2h 15m |
| 2026-06-12 | RANGR92 | - | Jun 12, 18:40 UTC | Jun 12, 20:20 UTC | 1h 40m |
| 2026-06-11 | RANGR92 | - | Jun 11, 15:15 UTC | Jun 11, 17:05 UTC | 1h 50m |
| 2026-06-11 | RANGR92 | GDN → RMS | Jun 11, 09:40 UTC | Jun 11, 11:30 UTC | 1h 50m |
| 2026-06-09 | RANGR92 | LPL → GDN | Jun 9, 11:00 UTC | Jun 9, 13:35 UTC | 2h 35m |
| 2026-06-08 | RANGR91 | MHZ → LPL | Jun 8, 18:55 UTC | Jun 8, 19:35 UTC | 40m |
| 2026-06-08 | RANGR91 | LPL → MHZ | Jun 8, 16:55 UTC | Jun 8, 17:45 UTC | 50m |
| 2026-06-08 | RANGR91 | - | Jun 8, 08:20 UTC | Jun 8, 13:50 UTC | 5h 30m |
| 2026-06-05 | RANGR91 | - | Jun 5, 19:20 UTC | Jun 5, 20:50 UTC | 1h 30m |
| 2026-06-04 | RANGR91 | - | Jun 4, 14:15 UTC | Jun 4, 20:50 UTC | 6h 35m |
| 2026-05-17 | RANGR04 | - | May 17, 01:55 UTC | May 17, 03:45 UTC | 1h 50m |
| 2026-05-16 | RANGR04 | - | May 16, 22:00 UTC | May 17, 00:40 UTC | 2h 40m |
| 2026-05-15 | RANGR55 | - | May 15, 22:30 UTC | May 16, 00:30 UTC | 2h 0m |
| 2026-05-15 | RANGR55 | - | May 15, 20:50 UTC | May 15, 21:00 UTC | 10m |
| 2026-05-14 | RANGR55 | HII → FTW | May 14, 18:40 UTC | May 14, 21:25 UTC | 2h 45m |
| 2026-05-14 | RANGR55 | - | May 14, 16:50 UTC | May 14, 17:40 UTC | 50m |
| 2026-05-14 | RANGR55 | - | May 14, 15:05 UTC | May 14, 15:35 UTC | 30m |
| 2026-05-13 | RANGR55 | - | May 13, 20:30 UTC | May 13, 21:00 UTC | 30m |
| 2026-05-13 | RANGR55 | - | May 13, 17:40 UTC | May 13, 18:35 UTC | 55m |
| 2026-05-13 | RANGR55 | - | May 13, 14:55 UTC | May 13, 15:40 UTC | 45m |
| 2026-05-12 | RANGR55 | - | May 12, 20:01 UTC | May 12, 20:15 UTC | 15m |
| 2026-05-12 | RANGR55 | - | May 12, 16:00 UTC | May 12, 17:20 UTC | 1h 20m |
| 2026-05-11 | RANGR55 | - | May 11, 17:25 UTC | May 11, 20:15 UTC | 2h 50m |
| 2026-05-06 | RANGR95 | - | May 6, 18:15 UTC | May 6, 22:15 UTC | 4h 0m |
| 2026-05-05 | RANGR95 | - | May 5, 21:40 UTC | May 5, 22:40 UTC | 1h 0m |
| 2026-05-04 | RANGR95 | - | May 4, 14:00 UTC | May 4, 18:55 UTC | 4h 56m |
| 2026-05-02 | - | - | May 2, 13:35 UTC | May 2, 15:45 UTC | 2h 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 169018 page for operator, model, and routing details .