sensors Mode-S transponder
AE5718
ICAO 24-bit transponder address
Currently assigned to 168980 · Boeing C-40A Clipper
- Hex
- AE5718
- Octal
- 53453430
- Decimal
- 11,425,560
- Tail
- 168980
- Type
- B737
- Flights observed
- 57
- Distinct callsigns
- 10
- Country
- -
- Last broadcast
- 19h ago
Last known position
Callsign history 10 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-18 | CNV8602 | - | Jun 18, 05:45 UTC | Jun 18, 09:35 UTC | 3h 50m |
| 2026-06-18 | CNV8602 | - | Jun 18, 04:05 UTC | Jun 18, 04:45 UTC | 40m |
| 2026-06-17 | CNV8602 | - | Jun 17, 07:45 UTC | Jun 17, 08:30 UTC | 45m |
| 2026-06-16 | CNV8602 | - | Jun 16, 06:25 UTC | Jun 16, 07:05 UTC | 40m |
| 2026-06-16 | CNV8602 | - | Jun 16, 01:25 UTC | Jun 16, 01:55 UTC | 30m |
| 2026-06-15 | CNV8602 | - | Jun 15, 01:10 UTC | Jun 15, 05:20 UTC | 4h 10m |
| 2026-06-14 | CNV8602 | NJA → OKO | Jun 14, 23:05 UTC | Jun 14, 23:20 UTC | 14m |
| 2026-06-11 | CNV8601 | - | Jun 11, 08:30 UTC | Jun 11, 12:15 UTC | 3h 45m |
| 2026-06-11 | CNV8601 | - | Jun 11, 07:25 UTC | Jun 11, 08:00 UTC | 35m |
| 2026-06-10 | CNV8601 | - | Jun 10, 07:05 UTC | Jun 10, 07:50 UTC | 45m |
| 2026-06-09 | CNV8601 | - | Jun 9, 01:45 UTC | Jun 9, 02:30 UTC | 45m |
| 2026-06-08 | CNV8601 | - | Jun 8, 05:50 UTC | Jun 8, 06:25 UTC | 35m |
| 2026-06-08 | CNV7930 | - | Jun 8, 00:40 UTC | Jun 8, 04:35 UTC | 3h 55m |
| 2026-06-07 | CNV7930 | NJA → OKO | Jun 7, 23:20 UTC | Jun 7, 23:35 UTC | 15m |
| 2026-06-04 | CNV7930 | - | Jun 4, 07:00 UTC | Jun 4, 07:35 UTC | 35m |
| 2026-06-03 | CNV7930 | - | Jun 3, 04:40 UTC | Jun 3, 04:50 UTC | 10m |
| 2026-06-03 | CNV7930 | - | Jun 3, 01:30 UTC | Jun 3, 01:40 UTC | 10m |
| 2026-05-31 | CNV7930 | - | May 31, 23:45 UTC | May 31, 23:55 UTC | 10m |
| 2026-05-30 | CNV7930 | - | May 30, 22:10 UTC | May 30, 22:45 UTC | 35m |
| 2026-05-30 | CNV7930 | OKO → NJA | May 30, 02:30 UTC | May 30, 02:45 UTC | 15m |
| 2026-05-30 | CNV7930 | NJA → OKO | May 30, 00:55 UTC | May 30, 01:15 UTC | 20m |
| 2026-05-27 | CNV7212 | - | May 27, 00:10 UTC | May 27, 09:50 UTC | 9h 40m |
| 2026-05-24 | CNV7212 | - | May 24, 23:40 UTC | May 24, 23:46 UTC | 6m |
| 2026-05-23 | CNV7212 | - | May 23, 22:35 UTC | May 24, 04:35 UTC | 6h 0m |
| 2026-05-23 | CNV7212 | OKO → NJA | May 23, 02:20 UTC | May 23, 02:40 UTC | 19m |
| 2026-05-23 | CNV7212 | NJA → OKO | May 23, 00:50 UTC | May 23, 01:05 UTC | 15m |
| 2026-05-21 | CNV4750 | HNL → NJA | May 21, 22:10 UTC | May 22, 08:30 UTC | 10h 20m |
| 2026-05-19 | CNV4750 | - | May 19, 21:45 UTC | May 20, 03:55 UTC | 6h 10m |
| 2026-05-19 | CNV4750 | - | May 19, 17:40 UTC | May 19, 20:20 UTC | 2h 40m |
| 2026-05-19 | CNV4750 | - | May 19, 14:25 UTC | May 19, 16:40 UTC | 2h 15m |
| 2026-05-10 | CNV4950 | - | May 10, 23:25 UTC | May 11, 01:00 UTC | 1h 35m |
| 2026-05-10 | CNV4950 | - | May 10, 17:34 UTC | May 10, 21:54 UTC | 4h 20m |
| 2026-05-09 | CNV4950 | - | May 9, 21:14 UTC | May 10, 02:55 UTC | 5h 40m |
| 2026-05-09 | CNV4950 | - | May 9, 18:55 UTC | May 9, 20:10 UTC | 1h 15m |
| 2026-05-09 | CNV4950 | - | May 9, 16:10 UTC | May 9, 17:35 UTC | 1h 25m |
| 2026-05-09 | CNV4950 | - | May 9, 13:55 UTC | May 9, 15:10 UTC | 1h 15m |
| 2026-05-08 | CNV4950 | - | May 8, 23:25 UTC | May 9, 00:05 UTC | 40m |
| 2026-05-08 | CNV4950 | - | May 8, 15:30 UTC | May 8, 17:20 UTC | 1h 50m |
| 2026-05-08 | CNV4950 | - | May 8, 13:20 UTC | May 8, 14:20 UTC | 1h 0m |
| 2026-05-07 | CNV4912 | - | May 7, 17:45 UTC | May 7, 19:50 UTC | 2h 5m |
| 2026-05-04 | CNV4914 | - | May 4, 22:50 UTC | May 5, 02:30 UTC | 3h 40m |
| 2026-05-04 | CNV4914 | - | May 4, 21:15 UTC | May 4, 21:35 UTC | 20m |
| 2026-05-04 | CNV4914 | - | May 4, 19:40 UTC | May 4, 20:00 UTC | 20m |
| 2026-05-04 | CNV4914 | - | May 4, 18:10 UTC | May 4, 18:35 UTC | 26m |
| 2026-05-04 | CNV4914 | - | May 4, 16:10 UTC | May 4, 16:35 UTC | 25m |
| 2026-05-03 | CNV4914 | - | May 3, 17:20 UTC | May 3, 23:04 UTC | 5h 45m |
| 2026-05-03 | CNV4914 | - | May 3, 14:50 UTC | May 3, 16:00 UTC | 1h 10m |
| 2026-05-02 | CNV4914 | - | May 2, 19:15 UTC | May 2, 20:50 UTC | 1h 35m |
| 2026-05-02 | CNV4914 | - | May 2, 16:25 UTC | May 2, 18:25 UTC | 2h 0m |
| 2026-05-02 | CNV4914 | - | May 2, 13:05 UTC | May 2, 15:10 UTC | 2h 5m |
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 168980 page for operator, model, and routing details .