Train NS 5469 Amsterdam Centraal – Zandvoort aan Zee
✓ Today’s run finished
Today, last fix heading to Overveen at 20:49 +1 min
- Amsterdam Centraal20:11
- Amsterdam Sloterdijk20:16
- Halfweg-Zwanenburg20:21
- Haarlem Spaarnwoude20:26
- Haarlem20:29
- Overveen20:35
- Zandvoort aan Zee20:41
Next service: tomorrow 20:11 from Amsterdam Centraal · Mon 16 Nov
Last 30 days
Arrival delay at Zandvoort aan Zee, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 10 Nov Max en route +11 min · last fix heading to — +10 min
- Wed 11 Nov Max en route +7 min · last fix heading to — +6 min
- Fri 9 Oct Max en route +5 min · last fix heading to — +4 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 24
- 3–10 min 7% · 2
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 50% T n=2
- 80% W n=5
- 100% T n=4
- 80% F n=5
- 100% S n=4
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 27 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 20:11 | on time | +1 min | |
| 20:16 | ≈ on time | ≈ +1 min | |
| 20:21 | ≈ on time | ≈ +2 min | |
| 20:26 | ≈ on time | ≈ +2 min | |
| 20:29 / 20:31 | ≈ on time | ≈ +2 min | |
| 20:35 | ≈ on time | ≈ +3 min | |
| 20:41 | on time | +3 min |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 15 Nov | Overveen 20:49Partial coverage | +1 min | +1 min |
| Sat 14 Nov | Overveen 20:52Partial coverage | +2 min | +2 min |
| Fri 13 Nov | — 20:43 | 0 min | — |
| Thu 12 Nov | — 20:44 | +2 min | +2 min |
| Wed 11 Nov | — 20:44 | +6 min | +7 min |
| Tue 10 Nov | — 20:54 | +10 min | +11 min |
| Mon 9 Nov | — 20:42 | 0 min | — |
| Sun 8 Nov | Overveen 20:53 | +3 min | +3 min |
| Sat 7 Nov | Overveen 20:49 | 0 min | — |
| Fri 6 Nov | — 20:43 | 0 min | — |
| Thu 5 Nov | — 20:45 | No data | — |
| Wed 4 Nov | — 20:43 | 0 min | — |
| Mon 2 Nov | — 20:42 | No data | — |
| Sun 1 Nov | Overveen 20:49 | 0 min | — |
| Sat 31 Oct | Overveen 20:50 | 0 min | — |
| Fri 30 Oct | — 20:42 | No data | — |
| Thu 29 Oct | — 20:42 | 0 min | — |
| Wed 28 Oct | — 20:42 | 0 min | — |
| Tue 27 Oct | — 20:43 | No data | — |
| Mon 26 Oct | — 20:42 | No data | — |
| Sun 25 Oct | Overveen 20:49 | No data | — |
| Sat 24 Oct | Overveen 20:53 | No data | — |
| Fri 23 Oct | — 20:42 | 0 min | — |
| Thu 22 Oct | — 20:43 | 0 min | — |
| Wed 21 Oct | — 20:43 | No data | — |
| Tue 20 Oct | — 20:42 | No data | — |
| Mon 19 Oct | — 20:43 | No data | — |
| Sun 18 Oct | Overveen 20:49 | 0 min | — |
| Sat 17 Oct | Overveen 20:47 | No data | — |
| Fri 16 Oct | — 20:42 | +1 min | +1 min |