sensors Mode-S transponder
AE6826
ICAO 24-bit transponder address
- Hex
- AE6826
- Octal
- 53464046
- Decimal
- 11,429,926
- Flights observed
- 39
- Distinct callsigns
- 3
- Country
- -
- Last broadcast
- Jun 12, 18:10 UTC
Last known position
Callsign history 3 distinct
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | - | - | Jun 12, 14:55 UTC | Jun 12, 18:10 UTC | 3h 15m |
| 2026-06-10 | - | - | Jun 10, 16:45 UTC | Jun 10, 17:55 UTC | 1h 10m |
| 2026-06-10 | - | - | Jun 10, 14:50 UTC | Jun 10, 15:40 UTC | 50m |
| 2026-06-10 | 0 P | - | Jun 10, 12:15 UTC | Jun 10, 13:40 UTC | 1h 25m |
| 2026-06-08 | 0 YP | - | Jun 8, 17:20 UTC | Jun 8, 20:15 UTC | 2h 55m |
| 2026-06-08 | 6U1V 8 | - | Jun 8, 13:55 UTC | Jun 8, 15:20 UTC | 1h 25m |
| 2026-06-04 | - | NIP → NIP | Jun 4, 15:55 UTC | Jun 4, 20:55 UTC | 5h 0m |
| 2026-06-02 | - | - | Jun 2, 17:00 UTC | Jun 2, 19:10 UTC | 2h 10m |
| 2026-06-02 | - | - | Jun 2, 15:05 UTC | Jun 2, 16:25 UTC | 1h 20m |
| 2026-06-01 | 0 P | - | Jun 1, 13:55 UTC | Jun 1, 17:40 UTC | 3h 45m |
| 2026-05-27 | 0 YP | - | May 27, 16:20 UTC | May 27, 20:00 UTC | 3h 40m |
| 2026-05-27 | 0 YP | - | May 27, 12:40 UTC | May 27, 15:00 UTC | 2h 20m |
| 2026-05-19 | - | - | May 19, 14:10 UTC | May 19, 19:10 UTC | 5h 0m |
| 2026-05-13 | - | - | May 13, 22:30 UTC | May 14, 00:50 UTC | 2h 20m |
| 2026-05-13 | - | - | May 13, 19:55 UTC | May 13, 22:25 UTC | 2h 30m |
| 2026-05-13 | - | - | May 13, 09:10 UTC | May 13, 09:45 UTC | 35m |
| 2026-05-13 | - | - | May 13, 03:55 UTC | May 13, 04:30 UTC | 35m |
| 2026-05-06 | - | - | May 6, 15:25 UTC | May 6, 23:15 UTC | 7h 50m |
| 2026-05-05 | - | - | May 5, 19:10 UTC | May 5, 19:35 UTC | 25m |
| 2026-05-05 | 0 YP | - | May 5, 12:35 UTC | May 5, 15:45 UTC | 3h 10m |
| 2026-04-29 | 0 P | - | Apr 29, 13:20 UTC | Apr 29, 18:15 UTC | 4h 55m |
| 2026-04-28 | 0 YP | - | Apr 28, 17:15 UTC | Apr 28, 20:15 UTC | 3h 0m |
| 2026-04-23 | - | - | Apr 23, 16:50 UTC | Apr 23, 19:15 UTC | 2h 24m |
| 2026-04-23 | 0 YP | - | Apr 23, 14:40 UTC | Apr 23, 15:50 UTC | 1h 10m |
| 2026-04-20 | - | - | Apr 20, 16:55 UTC | Apr 20, 19:50 UTC | 2h 55m |
| 2026-04-20 | 0 YP | - | Apr 20, 14:10 UTC | Apr 20, 16:15 UTC | 2h 5m |
| 2026-04-15 | - | - | Apr 15, 21:05 UTC | Apr 15, 21:20 UTC | 15m |
| 2026-04-15 | - | - | Apr 15, 20:30 UTC | Apr 15, 21:00 UTC | 30m |
| 2026-04-15 | - | - | Apr 15, 19:05 UTC | Apr 15, 19:50 UTC | 45m |
| 2026-04-15 | - | - | Apr 15, 18:30 UTC | Apr 15, 19:00 UTC | 30m |
| 2026-04-15 | - | - | Apr 15, 17:05 UTC | Apr 15, 17:35 UTC | 30m |
| 2026-04-14 | - | - | Apr 14, 16:50 UTC | Apr 14, 18:05 UTC | 1h 15m |
| 2026-04-14 | - | - | Apr 14, 15:05 UTC | Apr 14, 16:45 UTC | 1h 40m |
| 2026-04-14 | - | - | Apr 14, 13:10 UTC | Apr 14, 14:05 UTC | 55m |
| 2026-04-13 | - | - | Apr 13, 20:45 UTC | Apr 13, 21:20 UTC | 35m |
| 2026-04-13 | - | - | Apr 13, 19:45 UTC | Apr 13, 19:55 UTC | 10m |
| 2026-04-13 | - | - | Apr 13, 19:10 UTC | Apr 13, 19:55 UTC | 45m |
| 2026-04-13 | - | - | Apr 13, 16:15 UTC | Apr 13, 16:35 UTC | 20m |
| 2026-04-13 | - | - | Apr 13, 15:45 UTC | Apr 13, 16:15 UTC | 30m |
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.