sensors Mode-S transponder
AE08F0
ICAO 24-bit transponder address
Currently assigned to 83-0499 · BEECH 200 Super King Air
- Hex
- AE08F0
- Octal
- 53404360
- Decimal
- 11,405,552
- Tail
- 83-0499
- Type
- BE20
- Flights observed
- 27
- Distinct callsigns
- 3
- Country
- -
- Last broadcast
- 3h ago
Last known position
Callsign history 3 distinct
Recent flights last 27
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | RUBIK33 | - | Jun 8, 10:55 UTC | Jun 8, 11:40 UTC | 45m |
| 2026-05-28 | RUBIK33 | - | May 28, 10:00 UTC | May 28, 10:50 UTC | 50m |
| 2026-05-27 | RUBIK33 | - | May 27, 04:24 UTC | May 27, 07:35 UTC | 3h 10m |
| 2026-05-26 | RUBIK33 | - | May 26, 11:30 UTC | May 26, 14:05 UTC | 2h 35m |
| 2026-05-26 | RUBIK33 | - | May 26, 09:35 UTC | May 26, 10:44 UTC | 1h 10m |
| 2026-05-26 | RUBIK33 | - | May 26, 06:54 UTC | May 26, 07:40 UTC | 45m |
| 2026-05-22 | RUBIC33 | - | May 22, 10:30 UTC | May 22, 12:40 UTC | 2h 10m |
| 2026-05-20 | DUNA95 | BUD → BUD | May 20, 06:45 UTC | May 20, 08:05 UTC | 1h 20m |
| 2026-05-09 | RUBIK33 | - | May 9, 13:00 UTC | May 9, 16:20 UTC | 3h 20m |
| 2026-05-09 | RUBIK33 | - | May 9, 10:10 UTC | May 9, 12:05 UTC | 1h 55m |
| 2026-05-06 | RUBIK33 | - | May 6, 14:00 UTC | May 6, 16:55 UTC | 2h 55m |
| 2026-05-06 | RUBIK33 | - | May 6, 08:05 UTC | May 6, 12:35 UTC | 4h 30m |
| 2026-04-29 | RUBIK33 | TBS → BUD | Apr 29, 12:45 UTC | Apr 29, 20:30 UTC | 7h 45m |
| 2026-04-29 | RUBIK33 | - | Apr 29, 10:30 UTC | Apr 29, 11:55 UTC | 1h 25m |
| 2026-04-26 | RUBIK33 | - | Apr 26, 08:00 UTC | Apr 26, 09:40 UTC | 1h 40m |
| 2026-04-25 | RUBIK33 | BUD → TBS | Apr 25, 07:40 UTC | Apr 25, 14:10 UTC | 6h 30m |
| 2026-04-24 | RUBIK33 | - | Apr 24, 09:20 UTC | Apr 24, 10:40 UTC | 1h 20m |
| 2026-04-23 | RUBIK33 | - | Apr 23, 14:55 UTC | Apr 23, 15:25 UTC | 30m |
| 2026-04-23 | RUBIK33 | NUE → BEG | Apr 23, 12:15 UTC | Apr 23, 14:25 UTC | 2h 10m |
| 2026-04-23 | RUBIK33 | BUD → NUE | Apr 23, 09:35 UTC | Apr 23, 11:10 UTC | 1h 35m |
| 2026-04-23 | RUBIK33 | BUD → BUD | Apr 23, 07:40 UTC | Apr 23, 08:01 UTC | 20m |
| 2026-04-20 | RUBIK33 | - | Apr 20, 17:15 UTC | Apr 20, 18:20 UTC | 1h 5m |
| 2026-04-20 | RUBIK33 | NUE → AVB | Apr 20, 13:55 UTC | Apr 20, 15:05 UTC | 1h 10m |
| 2026-04-20 | RUBIK33 | - | Apr 20, 10:00 UTC | Apr 20, 12:15 UTC | 2h 15m |
| 2026-04-20 | RUBIK33 | BUD → BEG | Apr 20, 08:10 UTC | Apr 20, 09:00 UTC | 50m |
| 2026-04-15 | DUNA95 | - | Apr 15, 11:00 UTC | Apr 15, 12:20 UTC | 1h 20m |
| 2026-04-15 | DUNA95 | - | Apr 15, 09:00 UTC | Apr 15, 10:55 UTC | 1h 55m |
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 83-0499 page for operator, model, and routing details .