sensors Mode-S transponder
AE4EE6
ICAO 24-bit transponder address
Currently assigned to 11-0123 · Cirrus T-53A Kaydet II
- Hex
- AE4EE6
- Octal
- 53447346
- Decimal
- 11,423,462
- Tail
- 11-0123
- Type
- SR20
- Flights observed
- 43
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 18h ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SHARK73 | - | 43 | 2026-06-15 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-15 | SHARK73 | - | Jun 15, 15:50 UTC | Jun 15, 17:15 UTC | 1h 25m |
| 2026-06-15 | SHARK73 | - | Jun 15, 12:19 UTC | Jun 15, 13:50 UTC | 1h 30m |
| 2026-06-12 | SHARK73 | - | Jun 12, 19:20 UTC | Jun 12, 20:45 UTC | 1h 25m |
| 2026-06-12 | SHARK73 | - | Jun 12, 16:05 UTC | Jun 12, 17:40 UTC | 1h 35m |
| 2026-06-12 | SHARK73 | - | Jun 12, 12:45 UTC | Jun 12, 14:20 UTC | 1h 35m |
| 2026-06-11 | SHARK73 | - | Jun 11, 16:30 UTC | Jun 11, 18:05 UTC | 1h 35m |
| 2026-06-11 | SHARK73 | - | Jun 11, 12:50 UTC | Jun 11, 14:30 UTC | 1h 40m |
| 2026-06-10 | SHARK73 | - | Jun 10, 15:45 UTC | Jun 10, 17:25 UTC | 1h 40m |
| 2026-06-10 | SHARK73 | - | Jun 10, 12:55 UTC | Jun 10, 14:30 UTC | 1h 35m |
| 2026-06-09 | SHARK73 | - | Jun 9, 13:55 UTC | Jun 9, 14:40 UTC | 45m |
| 2026-06-08 | SHARK73 | - | Jun 8, 15:15 UTC | Jun 8, 16:40 UTC | 1h 25m |
| 2026-06-08 | SHARK73 | - | Jun 8, 12:50 UTC | Jun 8, 14:20 UTC | 1h 30m |
| 2026-06-06 | SHARK73 | - | Jun 6, 16:14 UTC | Jun 6, 18:00 UTC | 1h 45m |
| 2026-06-06 | SHARK73 | - | Jun 6, 13:54 UTC | Jun 6, 15:10 UTC | 1h 15m |
| 2026-06-05 | SHARK73 | - | Jun 5, 16:00 UTC | Jun 5, 17:55 UTC | 1h 55m |
| 2026-06-05 | SHARK73 | - | Jun 5, 12:50 UTC | Jun 5, 14:25 UTC | 1h 35m |
| 2026-06-04 | SHARK73 | - | Jun 4, 16:15 UTC | Jun 4, 17:35 UTC | 1h 20m |
| 2026-06-03 | SHARK73 | - | Jun 3, 16:00 UTC | Jun 3, 17:30 UTC | 1h 30m |
| 2026-06-03 | SHARK73 | - | Jun 3, 13:10 UTC | Jun 3, 14:30 UTC | 1h 20m |
| 2026-06-01 | SHARK73 | - | Jun 1, 16:00 UTC | Jun 1, 17:20 UTC | 1h 20m |
| 2026-06-01 | SHARK73 | - | Jun 1, 13:20 UTC | Jun 1, 14:55 UTC | 1h 35m |
| 2026-06-01 | SHARK73 | - | Jun 1, 12:20 UTC | Jun 1, 12:30 UTC | 10m |
| 2026-05-26 | SHARK73 | - | May 26, 17:50 UTC | May 26, 19:25 UTC | 1h 35m |
| 2026-05-26 | SHARK73 | - | May 26, 14:40 UTC | May 26, 16:00 UTC | 1h 20m |
| 2026-05-21 | SHARK73 | - | May 21, 17:40 UTC | May 21, 19:00 UTC | 1h 20m |
| 2026-05-15 | SHARK73 | - | May 15, 17:40 UTC | May 15, 19:05 UTC | 1h 25m |
| 2026-05-15 | SHARK73 | - | May 15, 14:50 UTC | May 15, 16:15 UTC | 1h 25m |
| 2026-05-14 | SHARK73 | - | May 14, 18:00 UTC | May 14, 18:35 UTC | 35m |
| 2026-05-07 | SHARK73 | - | May 7, 19:55 UTC | May 7, 21:25 UTC | 1h 30m |
| 2026-05-07 | SHARK73 | - | May 7, 16:45 UTC | May 7, 17:50 UTC | 1h 5m |
| 2026-05-07 | SHARK73 | - | May 7, 13:45 UTC | May 7, 15:05 UTC | 1h 20m |
| 2026-04-28 | SHARK73 | - | Apr 28, 19:40 UTC | Apr 28, 20:55 UTC | 1h 15m |
| 2026-04-28 | SHARK73 | - | Apr 28, 16:35 UTC | Apr 28, 18:00 UTC | 1h 25m |
| 2026-04-27 | SHARK73 | - | Apr 27, 13:45 UTC | Apr 27, 15:10 UTC | 1h 25m |
| 2026-04-24 | SHARK73 | - | Apr 24, 18:45 UTC | Apr 24, 19:25 UTC | 40m |
| 2026-04-24 | SHARK73 | - | Apr 24, 16:40 UTC | Apr 24, 17:35 UTC | 55m |
| 2026-04-24 | SHARK73 | - | Apr 24, 13:25 UTC | Apr 24, 15:00 UTC | 1h 35m |
| 2026-04-22 | SHARK73 | - | Apr 22, 16:10 UTC | Apr 22, 17:50 UTC | 1h 40m |
| 2026-04-21 | SHARK73 | AFF → AFF | Apr 21, 19:35 UTC | Apr 21, 21:10 UTC | 1h 35m |
| 2026-04-20 | SHARK73 | - | Apr 20, 16:30 UTC | Apr 20, 17:55 UTC | 1h 25m |
| 2026-04-15 | SHARK73 | - | Apr 15, 21:05 UTC | Apr 15, 21:15 UTC | 10m |
| 2026-04-15 | SHARK73 | - | Apr 15, 20:10 UTC | Apr 15, 21:00 UTC | 50m |
| 2026-04-15 | SHARK73 | - | Apr 15, 17:15 UTC | Apr 15, 18:30 UTC | 1h 15m |
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 11-0123 page for operator, model, and routing details .