Flight
KLM596
Flight history and live tracking for KLM596, operated by KLM Royal Dutch Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | KLM Royal Dutch Airlines |
| Observed route | EHVB → EHAM |
Flight history 42 flights since Dec 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (42) - back to 2025-12-16
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-05-25 | ? | EHAM | 09:09Z | 19:10 CEST | 8h 01m | PH-BQM |
| 2026-05-22estimated | ? | ? | 09:03Z | 16:58Z | 7h 55m | PH-BQP |
| 2026-05-20estimated | EHVB | EHAM | 04:36 CEST | 19:20 CEST | 14h 43m | PH-BHG |
| 2026-05-19estimated | FNPA | EHRD | 03:32 WAT | 18:56 CEST | 14h 23m | PH-BQN |
| 2026-05-11 | FNPA | EHAM | 10:00 WAT | 18:58 CEST | 7h 57m | PH-BQA |
| 2026-05-08estimated | FNPA | EHAM | 09:54 WAT | 19:02 CEST | 8h 07m | PH-BQA |
| 2026-05-06 | FNPA | EHAM | 09:35 WAT | 18:48 CEST | 8h 12m | PH-BHN |
| 2026-05-04estimated | FNPA | EHAM | 09:50 WAT | 21:34 CEST | 10h 43m | PH-BQG |
| 2026-05-01 | FNPA | EHAM | 09:37 WAT | 18:48 CEST | 8h 10m | PH-BHP |
| 2026-04-29estimated | LFMD | EHAM | 17:37 CEST | 19:06 CEST | 1h 28m | PH-BQO |
| 2026-04-27 | ? | EHAM | 10:18Z | 18:54 CEST | 6h 35m | PH-BQL |
| 2026-04-24estimated | EHVB | EHAM | 10:41 CEST | 18:52 CEST | 8h 11m | PH-BQG |
| 2026-04-22estimated | ? | ? | 08:54Z | 17:02Z | 8h 07m | PH-BQN |
| 2026-04-20estimated | ? | ? | 08:55Z | 20:06Z | 11h 10m | PH-BHG |
| 2026-04-17estimated | EHVB | EHAM | 10:46 CEST | 18:56 CEST | 8h 09m | PH-BQL |
| 2026-04-15estimated | ? | ? | 08:45Z | 17:18Z | 8h 32m | PH-BQB |
| 2026-04-06estimated | ? | ? | 08:50Z | 16:38Z | 7h 47m | PH-BQP |
| 2026-04-03estimated | ? | ? | 10:10Z | 18:26Z | 8h 16m | PH-BVC |
| 2026-04-01estimated | ? | ? | 09:17Z | 10:00Z | 0h 42m | PH-BVI |
| 2026-03-30estimated | ? | ? | 08:49Z | 17:08Z | 8h 18m | PH-BQB |
| 2026-03-29estimated | EHVB | EHAM | 11:23 CEST | 19:22 CEST | 7h 58m | PH-BQG |
| 2026-03-28estimated | EHVB | EHAM | 16:07 CET | 18:20 CET | 2h 12m | PH-BQO |
| 2026-03-15estimated | ? | ? | 09:12Z | 20:14Z | 11h 01m | PH-BQG |
| 2026-03-14estimated | ? | ? | 09:15Z | 20:34Z | 11h 18m | PH-BHF |
| 2026-03-13estimated | EHVB | EHAM | 10:31 CET | 18:46 CET | 8h 14m | PH-BQN |
| 2026-03-10 | FACT | ? | 08:17 SAST | 09:20Z | 3h 03m | 484CBC |
| 2026-03-07 | FACT | ? | 08:12 SAST | 09:24Z | 3h 12m | 4851B1 |
| 2026-03-06 | FACT | ? | 08:36 SAST | 09:44Z | 3h 08m | 4841AD |
| 2026-03-03 | FACT | FNPA | 08:12 SAST | 10:19 WAT | 3h 07m | 48436E |
| 2026-03-01 | FACT | FNPA | 09:19 SAST | 11:24 WAT | 3h 05m | 4851F7 |
| 2026-02-28 | FACT | FNLU | 08:22 SAST | 10:38 WAT | 3h 15m | 485788 |
| 2026-02-24 | FACT | ? | 08:08 SAST | 09:32Z | 3h 23m | 48436A |
| 2026-02-22 | FACT | ? | 08:08 SAST | 09:33Z | 3h 24m | 484371 |
| 2026-02-21 | FACT | ? | 08:10 SAST | 09:34Z | 3h 23m | 4851B1 |
| 2026-02-20 | FACT | FNLU | 08:15 SAST | 10:35 WAT | 3h 20m | 484369 |
| 2026-02-15 | FACT | ? | 08:10 SAST | 15:59Z | 9h 49m | 484370 |
| 2026-02-14 | FACT | ? | 08:14 SAST | 15:25Z | 9h 10m | 485785 |
| 2026-02-08 | FACT | ? | 09:07 SAST | 16:41Z | 9h 34m | 4841AD |
| 2026-02-07 | FACT | FZAG | 08:16 SAST | 10:53 WAT | 3h 37m | 485343 |
| 2026-01-30 | FACT | LFLU | 08:23 SAST | 17:25 CET | 10h 02m | 4843F3 |
| 2026-01-24 | FACT | ? | 08:00 SAST | 15:23Z | 9h 22m | 485341 |
| 2025-12-16 | FACT | LFQI | 08:19 SAST | 18:01 CET | 10h 42m | 4843F2 |
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 KLM596 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 own receiver network archive. Questions: [email protected]