sensors Mode-S transponder
AE6285
ICAO 24-bit transponder address
Currently assigned to 163648
- Hex
- AE6285
- Octal
- 53461205
- Decimal
- 11,428,485
- Tail
- 163648
- Type
- HAWK
- Flights observed
- 30
- Distinct callsigns
- 11
- Country
- -
- Last broadcast
- 15h ago
Last known position
Callsign history 11 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | ROKT32 | - | Jul 17, 20:35 UTC | Jul 17, 21:05 UTC | 30m |
| 2026-07-17 | ROKT61 | - | Jul 17, 17:55 UTC | Jul 17, 19:20 UTC | 1h 25m |
| 2026-07-16 | ROKT42 | - | Jul 16, 20:39 UTC | Jul 16, 21:00 UTC | 20m |
| 2026-07-16 | ROKT41 | - | Jul 16, 18:10 UTC | Jul 16, 18:59 UTC | 50m |
| 2026-07-16 | ROKT12 | - | Jul 16, 16:00 UTC | Jul 16, 16:44 UTC | 45m |
| 2026-07-16 | ROKT11 | - | Jul 16, 13:15 UTC | Jul 16, 14:25 UTC | 1h 10m |
| 2026-07-15 | ROKT61 | - | Jul 15, 17:35 UTC | Jul 15, 17:55 UTC | 20m |
| 2026-07-14 | ROKT41 | - | Jul 14, 18:35 UTC | Jul 14, 19:20 UTC | 45m |
| 2026-07-14 | ROKT42 | - | Jul 14, 16:20 UTC | Jul 14, 16:50 UTC | 30m |
| 2026-07-14 | ROKT31 | - | Jul 14, 12:45 UTC | Jul 14, 13:45 UTC | 1h 0m |
| 2026-07-10 | ROKT31 | - | Jul 10, 15:10 UTC | Jul 10, 16:20 UTC | 1h 10m |
| 2026-07-09 | ROKT61 | - | Jul 9, 20:25 UTC | Jul 9, 20:35 UTC | 10m |
| 2026-07-09 | ROKT61 | - | Jul 9, 19:40 UTC | Jul 9, 20:20 UTC | 40m |
| 2026-07-07 | ROKT11 | NPA → NPA | Jul 7, 15:45 UTC | Jul 7, 16:35 UTC | 50m |
| 2026-07-01 | ROKT11 | - | Jul 1, 22:35 UTC | Jul 1, 23:25 UTC | 50m |
| 2026-06-29 | ROKT22 | - | Jun 29, 13:19 UTC | Jun 29, 13:54 UTC | 35m |
| 2026-06-26 | ROKT61 | - | Jun 26, 18:04 UTC | Jun 26, 19:09 UTC | 1h 5m |
| 2026-06-25 | ROKT21 | - | Jun 25, 12:25 UTC | Jun 25, 13:14 UTC | 50m |
| 2026-06-23 | ROKT22 | - | Jun 23, 16:05 UTC | Jun 23, 16:35 UTC | 30m |
| 2026-06-23 | ROKT21 | - | Jun 23, 13:00 UTC | Jun 23, 13:15 UTC | 15m |
| 2026-06-17 | ROKT41 | - | Jun 17, 21:10 UTC | Jun 17, 21:30 UTC | 20m |
| 2026-06-17 | ROKT42 | - | Jun 17, 18:40 UTC | Jun 17, 19:15 UTC | 35m |
| 2026-06-15 | ROKT11 | - | Jun 15, 17:45 UTC | Jun 15, 18:40 UTC | 55m |
| 2026-06-13 | ROKT11 | - | Jun 13, 15:50 UTC | Jun 13, 17:05 UTC | 1h 15m |
| 2026-06-13 | ROKT11 | - | Jun 13, 13:25 UTC | Jun 13, 14:35 UTC | 1h 10m |
| 2026-06-12 | ROKT61 | - | Jun 12, 20:35 UTC | Jun 12, 21:35 UTC | 1h 0m |
| 2026-06-12 | ROKT61 | - | Jun 12, 18:05 UTC | Jun 12, 19:00 UTC | 55m |
| 2026-06-11 | ROKT41 | - | Jun 11, 16:35 UTC | Jun 11, 17:25 UTC | 50m |
| 2026-06-10 | ROKT62 | - | Jun 10, 21:15 UTC | Jun 10, 21:50 UTC | 35m |
| 2026-06-01 | ROKT99 | - | Jun 1, 14:05 UTC | Jun 1, 15:15 UTC | 1h 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 163648 page for operator, model, and routing details .