sensors Mode-S transponder
AE6BA7
ICAO 24-bit transponder address
Currently assigned to 169454 · Bell/Boeing CMV-22B Osprey
- Hex
- AE6BA7
- Octal
- 53465647
- Decimal
- 11,430,823
- Tail
- 169454
- Type
- V22
- Flights observed
- 28
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- May 5, 04:20 UTC
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RUDY24 | - | 28 | 2026-05-05 |
Recent flights last 28
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-05 | RUDY24 | - | May 5, 03:50 UTC | May 5, 04:20 UTC | 30m |
| 2026-05-05 | RUDY24 | - | May 5, 03:00 UTC | May 5, 03:45 UTC | 45m |
| 2026-05-05 | RUDY24 | - | May 5, 02:01 UTC | May 5, 02:15 UTC | 15m |
| 2026-05-05 | RUDY24 | - | May 5, 00:20 UTC | May 5, 00:55 UTC | 35m |
| 2026-05-04 | RUDY24 | - | May 4, 23:00 UTC | May 4, 23:20 UTC | 20m |
| 2026-05-04 | RUDY24 | - | May 4, 22:00 UTC | May 4, 22:15 UTC | 15m |
| 2026-05-04 | RUDY24 | - | May 4, 21:05 UTC | May 4, 21:15 UTC | 10m |
| 2026-05-04 | RUDY24 | - | May 4, 19:45 UTC | May 4, 20:00 UTC | 15m |
| 2026-04-27 | RUDY24 | - | Apr 27, 18:55 UTC | Apr 27, 19:10 UTC | 15m |
| 2026-04-25 | RUDY24 | - | Apr 25, 17:10 UTC | Apr 25, 17:30 UTC | 20m |
| 2026-04-25 | RUDY24 | - | Apr 25, 15:05 UTC | Apr 25, 15:15 UTC | 10m |
| 2026-04-22 | RUDY24 | - | Apr 22, 22:25 UTC | Apr 22, 22:40 UTC | 15m |
| 2026-04-22 | RUDY24 | - | Apr 22, 20:10 UTC | Apr 22, 20:25 UTC | 15m |
| 2026-04-21 | RUDY24 | - | Apr 21, 22:45 UTC | Apr 21, 23:05 UTC | 20m |
| 2026-04-21 | RUDY24 | - | Apr 21, 20:00 UTC | Apr 21, 20:05 UTC | 5m |
| 2026-04-20 | RUDY24 | - | Apr 20, 20:20 UTC | Apr 20, 20:35 UTC | 15m |
| 2026-04-15 | RUDY24 | - | Apr 15, 05:45 UTC | Apr 15, 06:05 UTC | 20m |
| 2026-04-15 | RUDY24 | - | Apr 15, 03:30 UTC | Apr 15, 03:40 UTC | 10m |
| 2026-04-15 | RUDY24 | HII → HII | Apr 15, 02:55 UTC | Apr 15, 03:00 UTC | 5m |
| 2026-04-15 | RUDY24 | - | Apr 15, 00:55 UTC | Apr 15, 02:50 UTC | 1h 55m |
| 2026-04-14 | RUDY24 | - | Apr 14, 23:20 UTC | Apr 15, 00:00 UTC | 40m |
| 2026-04-14 | RUDY24 | - | Apr 14, 22:55 UTC | Apr 14, 23:00 UTC | 5m |
| 2026-04-14 | RUDY24 | - | Apr 14, 22:20 UTC | Apr 14, 22:50 UTC | 30m |
| 2026-04-14 | RUDY24 | NZY → NZY | Apr 14, 21:30 UTC | Apr 14, 22:00 UTC | 30m |
| 2026-04-13 | RUDY24 | - | Apr 13, 22:45 UTC | Apr 13, 23:40 UTC | 55m |
| 2026-04-13 | RUDY24 | - | Apr 13, 19:50 UTC | Apr 13, 22:05 UTC | 2h 15m |
| 2026-04-13 | RUDY24 | - | Apr 13, 19:05 UTC | Apr 13, 20:10 UTC | 1h 5m |
| 2026-04-13 | RUDY24 | - | Apr 13, 18:05 UTC | Apr 13, 18:30 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 169454 page for operator, model, and routing details .