sensors Mode-S transponder
AE58F1
ICAO 24-bit transponder address
Currently assigned to 166252 · Raytheon T-6B Texan II
- Hex
- AE58F1
- Octal
- 53454361
- Decimal
- 11,426,033
- Tail
- 166252
- Type
- TEX2
- Flights observed
- 30
- Distinct callsigns
- 6
- Country
- -
- Last broadcast
- 29d ago
Last known position
Callsign history 6 distinct
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-05 | RN252 | - | May 5, 01:15 UTC | May 5, 02:10 UTC | 55m |
| 2026-05-04 | RN252 | - | May 4, 22:05 UTC | May 4, 23:45 UTC | 1h 40m |
| 2026-04-30 | BB252 | - | Apr 30, 17:35 UTC | Apr 30, 18:35 UTC | 1h 0m |
| 2026-04-29 | SH246 | - | Apr 29, 21:45 UTC | Apr 29, 22:45 UTC | 1h 0m |
| 2026-04-29 | SH246 | - | Apr 29, 16:15 UTC | Apr 29, 16:30 UTC | 15m |
| 2026-04-29 | SH252 | - | Apr 29, 13:25 UTC | Apr 29, 14:15 UTC | 50m |
| 2026-04-28 | RN252 | - | Apr 28, 20:45 UTC | Apr 28, 21:00 UTC | 15m |
| 2026-04-28 | RN252 | - | Apr 28, 17:40 UTC | Apr 28, 17:55 UTC | 15m |
| 2026-04-27 | RN252 | - | Apr 27, 20:05 UTC | Apr 27, 21:10 UTC | 1h 5m |
| 2026-04-27 | RN252 | - | Apr 27, 17:10 UTC | Apr 27, 18:10 UTC | 1h 0m |
| 2026-04-27 | RN252 | - | Apr 27, 12:45 UTC | Apr 27, 14:10 UTC | 1h 25m |
| 2026-04-25 | TEXN252 | - | Apr 25, 00:10 UTC | Apr 25, 01:30 UTC | 1h 20m |
| 2026-04-24 | TEXN252 | - | Apr 24, 21:15 UTC | Apr 24, 21:40 UTC | 25m |
| 2026-04-22 | SH223 | - | Apr 22, 16:40 UTC | Apr 22, 17:25 UTC | 45m |
| 2026-04-21 | BB252 | - | Apr 21, 23:45 UTC | Apr 22, 00:55 UTC | 1h 10m |
| 2026-04-21 | BB252 | - | Apr 21, 20:50 UTC | Apr 21, 22:15 UTC | 1h 25m |
| 2026-04-21 | BB252 | - | Apr 21, 16:45 UTC | Apr 21, 17:15 UTC | 30m |
| 2026-04-20 | SH252 | - | Apr 20, 20:25 UTC | Apr 20, 21:30 UTC | 1h 5m |
| 2026-04-20 | SH252 | - | Apr 20, 17:40 UTC | Apr 20, 18:20 UTC | 40m |
| 2026-04-20 | SH252 | - | Apr 20, 13:40 UTC | Apr 20, 14:25 UTC | 45m |
| 2026-04-18 | RN252 | - | Apr 18, 17:35 UTC | Apr 18, 18:10 UTC | 35m |
| 2026-04-18 | RN252 | - | Apr 18, 00:25 UTC | Apr 18, 00:35 UTC | 10m |
| 2026-04-17 | SH252 | - | Apr 17, 13:20 UTC | Apr 17, 14:25 UTC | 1h 5m |
| 2026-04-16 | RN252 | - | Apr 16, 17:15 UTC | Apr 16, 18:25 UTC | 1h 10m |
| 2026-04-16 | RN252 | - | Apr 16, 16:55 UTC | Apr 16, 17:10 UTC | 15m |
| 2026-04-14 | RN252 | - | Apr 14, 16:50 UTC | Apr 14, 18:00 UTC | 1h 10m |
| 2026-04-14 | RN252 | - | Apr 14, 13:50 UTC | Apr 14, 14:45 UTC | 55m |
| 2026-04-13 | SH252 | - | Apr 13, 22:55 UTC | Apr 13, 23:15 UTC | 20m |
| 2026-04-13 | SH252 | - | Apr 13, 21:45 UTC | Apr 13, 22:05 UTC | 20m |
| 2026-04-13 | BB252 | - | Apr 13, 17:35 UTC | Apr 13, 19:05 UTC | 1h 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.
Prefer a tail-number view? See the 166252 page for operator, model, and routing details .