Not currently tracked · last seen 53m ago
- Flights observed
- 66 showing last 50
- Avg flight time
- 51m
- Typical route
- NQI → NQI
- Last seen
- 53m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | NQI → NQI | Jun 2, 20:55 UTC | Jun 2, 21:35 UTC | 40m |
| 2026-06-02 | - | Jun 2, 15:45 UTC | Jun 2, 16:30 UTC | 45m |
| 2026-06-02 | NQI → NQI | Jun 2, 01:35 UTC | Jun 2, 02:40 UTC | 1h 5m |
| 2026-06-01 | - | Jun 1, 19:35 UTC | Jun 1, 19:50 UTC | 15m |
| 2026-06-01 | NQI → NQI | Jun 1, 15:30 UTC | Jun 1, 16:20 UTC | 50m |
| 2026-05-31 | NQI → NQI | May 31, 18:05 UTC | May 31, 19:20 UTC | 1h 15m |
| 2026-05-29 | NQI → NQI | May 29, 19:35 UTC | May 29, 20:50 UTC | 1h 15m |
| 2026-05-29 | NQI → NQI | May 29, 13:30 UTC | May 29, 14:30 UTC | 1h 0m |
| 2026-05-29 | NQI → NQI | May 29, 01:20 UTC | May 29, 02:30 UTC | 1h 10m |
| 2026-05-28 | NQI → NQI | May 28, 21:35 UTC | May 28, 22:30 UTC | 55m |
| 2026-05-28 | NQI → NQI | May 28, 19:35 UTC | May 28, 20:00 UTC | 25m |
| 2026-05-28 | NQI → NQI | May 28, 16:25 UTC | May 28, 17:25 UTC | 1h 0m |
| 2026-05-28 | NQI → NQI | May 28, 14:00 UTC | May 28, 14:55 UTC | 55m |
| 2026-05-27 | - | May 27, 21:45 UTC | May 27, 22:45 UTC | 1h 0m |
| 2026-05-27 | NQI → NQI | May 27, 20:15 UTC | May 27, 21:05 UTC | 50m |
| 2026-05-26 | - | May 26, 22:39 UTC | May 26, 23:14 UTC | 35m |
| 2026-05-26 | NQI → NQI | May 26, 20:54 UTC | May 26, 21:59 UTC | 1h 5m |
| 2026-05-26 | NQI → NQI | May 26, 18:50 UTC | May 26, 19:40 UTC | 50m |
| 2026-05-26 | NQI → NQI | May 26, 15:05 UTC | May 26, 16:15 UTC | 1h 10m |
| 2026-05-21 | NQI → NQI | May 21, 18:20 UTC | May 21, 19:10 UTC | 50m |
| 2026-05-20 | - | May 20, 21:15 UTC | May 20, 21:35 UTC | 20m |
| 2026-05-20 | - | May 20, 17:35 UTC | May 20, 17:50 UTC | 15m |
| 2026-05-20 | NQI → NQI | May 20, 01:35 UTC | May 20, 02:45 UTC | 1h 10m |
| 2026-05-19 | - | May 19, 17:50 UTC | May 19, 18:35 UTC | 45m |
| 2026-05-19 | NQI → NQI | May 19, 15:15 UTC | May 19, 16:15 UTC | 1h 0m |
| 2026-05-18 | NQI → NQI | May 18, 21:35 UTC | May 18, 22:45 UTC | 1h 10m |
| 2026-05-15 | - | May 15, 18:40 UTC | May 15, 19:30 UTC | 50m |
| 2026-05-15 | NQI → NQI | May 15, 17:20 UTC | May 15, 18:10 UTC | 50m |
| 2026-05-15 | - | May 15, 15:00 UTC | May 15, 15:25 UTC | 25m |
| 2026-05-13 | NQI → NQI | May 13, 03:25 UTC | May 13, 04:30 UTC | 1h 5m |
| 2026-05-13 | - | May 13, 02:10 UTC | May 13, 02:55 UTC | 45m |
| 2026-05-12 | - | May 12, 21:10 UTC | May 12, 21:55 UTC | 45m |
| 2026-05-12 | NQI → NQI | May 12, 18:15 UTC | May 12, 18:50 UTC | 35m |
| 2026-05-11 | NQI → NQI | May 11, 16:30 UTC | May 11, 17:30 UTC | 1h 1m |
| 2026-05-11 | NQI → NQI | May 11, 15:00 UTC | May 11, 15:55 UTC | 55m |
| 2026-05-05 | - | May 5, 16:00 UTC | May 5, 16:50 UTC | 50m |
| 2026-05-03 | - | May 3, 21:14 UTC | May 3, 22:00 UTC | 45m |
| 2026-05-03 | - | May 3, 17:40 UTC | May 3, 18:34 UTC | 55m |
| 2026-04-30 | NQI → NQI | Apr 30, 20:30 UTC | Apr 30, 21:25 UTC | 55m |
| 2026-04-30 | - | Apr 30, 00:40 UTC | Apr 30, 01:35 UTC | 55m |
| 2026-04-29 | - | Apr 29, 17:35 UTC | Apr 29, 18:05 UTC | 30m |
| 2026-04-29 | - | Apr 29, 15:00 UTC | Apr 29, 16:05 UTC | 1h 5m |
| 2026-04-29 | NQI → NQI | Apr 29, 01:30 UTC | Apr 29, 02:30 UTC | 1h 0m |
| 2026-04-28 | NQI → NQI | Apr 28, 20:55 UTC | Apr 28, 22:00 UTC | 1h 5m |
| 2026-04-28 | - | Apr 28, 19:05 UTC | Apr 28, 19:30 UTC | 25m |
| 2026-04-28 | - | Apr 28, 17:20 UTC | Apr 28, 17:55 UTC | 35m |
| 2026-04-28 | NQI → NQI | Apr 28, 15:20 UTC | Apr 28, 16:15 UTC | 55m |
| 2026-04-27 | - | Apr 27, 22:30 UTC | Apr 27, 23:20 UTC | 50m |
| 2026-04-27 | - | Apr 27, 19:30 UTC | Apr 27, 20:30 UTC | 1h 0m |
| 2026-04-27 | NQI → NQI | Apr 27, 16:55 UTC | Apr 27, 18:10 UTC | 1h 15m |
Specifications
| Registration | 165643 |
| Mode-S code | AE6300 · 53461400 (octal) |
Looking for transponder-level data? View the Mode-S AE6300 page for country allocation, callsign history, and ADS-B signal details.
165643 frequently asked
What is the Mode-S transponder code for 165643?
165643 broadcasts on Mode-S (ICAO 24-bit) address AE6300 (octal 53461400). View the transponder page.
What route does 165643 typically fly?
165643 most frequently flies between NQI and NQI based on observed flights.
Where is 165643 right now?
165643 is not currently being tracked; last seen 53m ago.