sensors Mode-S transponder
AE1E00
ICAO 24-bit transponder address
Currently assigned to 166034
- Hex
- AE1E00
- Octal
- 53417000
- Decimal
- 11,410,944
- Tail
- 166034
- Type
- TEX2
- Flights observed
- 30
- Distinct callsigns
- 6
- Country
- -
- Last broadcast
- 7h ago
Last known position
Callsign history 6 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-15 | SH034 | - | May 15, 01:35 UTC | May 15, 02:40 UTC | 1h 5m |
| 2026-05-14 | SH034 | - | May 14, 21:50 UTC | May 14, 22:50 UTC | 1h 0m |
| 2026-05-14 | SH034 | - | May 14, 17:50 UTC | May 14, 19:10 UTC | 1h 20m |
| 2026-05-14 | SH034 | - | May 14, 14:35 UTC | May 14, 16:00 UTC | 1h 25m |
| 2026-05-14 | BB034 | - | May 14, 01:10 UTC | May 14, 02:20 UTC | 1h 10m |
| 2026-05-13 | BB034 | - | May 13, 22:00 UTC | May 13, 23:25 UTC | 1h 25m |
| 2026-05-13 | BB034 | - | May 13, 17:20 UTC | May 13, 17:35 UTC | 15m |
| 2026-05-13 | BB034 | - | May 13, 14:10 UTC | May 13, 14:40 UTC | 30m |
| 2026-05-13 | BB034 | - | May 13, 02:10 UTC | May 13, 02:25 UTC | 15m |
| 2026-05-13 | BB034 | - | May 13, 01:15 UTC | May 13, 01:35 UTC | 20m |
| 2026-05-12 | BB034 | - | May 12, 21:45 UTC | May 12, 22:45 UTC | 1h 0m |
| 2026-05-11 | RN034 | - | May 11, 16:25 UTC | May 11, 16:50 UTC | 25m |
| 2026-05-08 | SH034 | - | May 8, 12:39 UTC | May 8, 13:25 UTC | 45m |
| 2026-05-07 | RN034 | - | May 7, 23:24 UTC | May 8, 00:34 UTC | 1h 10m |
| 2026-05-07 | BB034 | - | May 7, 00:35 UTC | May 7, 01:30 UTC | 55m |
| 2026-05-06 | BB034 | - | May 6, 22:05 UTC | May 6, 23:05 UTC | 1h 0m |
| 2026-05-05 | RN034 | - | May 5, 22:15 UTC | May 5, 22:40 UTC | 25m |
| 2026-05-05 | RN034 | - | May 5, 18:50 UTC | May 5, 19:30 UTC | 40m |
| 2026-05-01 | BB034 | - | May 1, 13:20 UTC | May 1, 14:15 UTC | 55m |
| 2026-04-30 | RN034 | - | Apr 30, 23:15 UTC | Apr 30, 23:50 UTC | 35m |
| 2026-04-30 | RN078 | - | Apr 30, 15:45 UTC | Apr 30, 15:55 UTC | 10m |
| 2026-04-30 | RN034 | BFM → BFM | Apr 30, 13:40 UTC | Apr 30, 14:10 UTC | 30m |
| 2026-04-30 | RN078 | - | Apr 30, 12:30 UTC | Apr 30, 13:00 UTC | 30m |
| 2026-04-29 | BB034 | - | Apr 29, 22:00 UTC | Apr 29, 22:35 UTC | 35m |
| 2026-04-29 | BB034 | - | Apr 29, 18:35 UTC | Apr 29, 19:05 UTC | 30m |
| 2026-04-28 | RN213 | - | Apr 28, 18:15 UTC | Apr 28, 18:50 UTC | 35m |
| 2026-04-28 | RN034 | - | Apr 28, 14:50 UTC | Apr 28, 15:05 UTC | 15m |
| 2026-04-27 | BB034 | - | Apr 27, 19:30 UTC | Apr 27, 19:55 UTC | 25m |
| 2026-04-24 | BB034 | - | Apr 24, 19:05 UTC | Apr 24, 19:25 UTC | 20m |
| 2026-04-24 | MX034 | - | Apr 24, 12:55 UTC | Apr 24, 13:20 UTC | 25m |
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 166034 page for operator, model, and routing details .