Flight
HARAMB1
Flight history and live tracking for HARAMB1. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 17 flights since Oct 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-07estimated | ? | HKJK | 14:05Z | 17:40 EAT | 0h 34m | 1806 |
| 2026-10-07estimated | ? | HKJK | 14:05Z | 17:38 EAT | 0h 32m | 4C20E |
| 2026-10-03partial | HKNW | ? | 18:39 EAT | 4C20E | ||
| 2026-09-26partial | ? | ? | 05:55Z | 4C20E | ||
| 2026-09-17partial | HKNW | ? | 18:51 EAT | 4C20D | ||
| 2026-09-11estimated | ? | ? | 05:37Z | 06:02Z | 0h 24m | 4C20D |
| 2026-09-10estimated | ? | HKJK | 12:44Z | 16:10 EAT | 0h 25m | 4C20D |
| 2026-09-09estimated | ? | ? | 07:50Z | 08:12Z | 0h 21m | 4C20D |
Earlier flights (9) - back to 2025-10-20
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-25estimated | HKJK | ? | 09:19 EAT | 06:40Z | 0h 20m | 4C20D |
| 2026-08-14partial | HKNW | ? | 18:25 EAT | 4C20D | ||
| 2026-08-13estimated | ? | ? | 04:41Z | 04:58Z | 0h 16m | 4C20D |
| 2026-07-12estimated | HKRE | ? | 16:12 EAT | 13:34Z | 0h 22m | 4C20D |
| 2026-02-11partial | HKNW | ? | 07:09 EAT | 4C20E | ||
| 2026-02-07 | HKJK | HKRE | 17:42 EAT | 18:04 EAT | 0h 22m | 4C20E |
| 2026-02-05estimated | ? | ? | 04:33Z | 04:50Z | 0h 16m | 4C20E |
| 2025-10-20partial | HKNW | ? | 17:21 EAT | 4C20E | ||
| 2025-10-20estimated | ? | ? | 04:55Z | 05:20Z | 0h 24m | 4C20E |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when HARAMB1 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our archive (from $9.99, with a free one-day sample). Questions: [email protected]