Train NS 5464 Zandvoort aan Zee – Amsterdam Centraal

Zandvoort aan Zee 20:19 → Amsterdam Centraal 20:49 Daily 0 h 30 min · 7 stops NS (Nederlandse Spoorwegen)

Running now · updated 20:57

Position estimated from the timetable

Heading to Amsterdam Centraal +5 min

Estimated arrival at Amsterdam Centraal 20:54 20:49

  1. Zandvoort aan Zee20:19
  2. Overveen20:25
  3. Haarlem20:30
  4. Haarlem Spaarnwoude20:34
  5. Halfweg-Zwanenburg20:39
  6. Amsterdam Sloterdijk20:44
  7. Amsterdam Centraal20:49

Today it is running worse than usual: typical arrival delay is 0 min; 86% of the last 21 runs arrived on time.

On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 14 full · 7 partial · 8 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 22 full · 7 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Amsterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min
  • Thu 29 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

29 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 86% · 25
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 75% W n=4
  • 50% T n=2
  • 100% F n=5
  • 100% S n=5
  • 80% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 stops).

Last 90 days, 29 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.

StopSched.Usually 9 days in 10Today
20:19on time on time
20:25≈ on time ≈ +1 min
20:30 / 20:31≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:39≈ on time ≈ +2 min
20:44≈ on time ≈ +2 min
20:49on 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

DateLast stopFinalMax
Sun 15 NovAmsterdam Sloterdijk 20:54Partial coverage+5 min+5 min
Sat 14 NovAmsterdam Sloterdijk 20:59Partial coverage+2 min+2 min
Fri 13 Nov— 20:490 min—
Thu 12 Nov— 20:29No data—
Wed 11 Nov— 20:320 min—
Tue 10 Nov— 20:490 min—
Mon 9 Nov— 20:490 min—
Sun 8 NovAmsterdam Sloterdijk 20:59Partial coverage+1 min—
Sat 7 NovAmsterdam Sloterdijk 20:59Partial coverage+1 min+1 min
Fri 6 Nov— 20:49+2 min+2 min
Thu 5 Nov— 20:50No data—
Wed 4 Nov— 20:54+5 min+5 min
Mon 2 Nov— 20:490 min—
Sun 1 NovAmsterdam Sloterdijk 20:58Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 20:58Partial coverage0 min—
Fri 30 Oct— 20:51No data—
Thu 29 Oct— 20:54+3 min+3 min
Wed 28 Oct— 20:520 min—
Tue 27 Oct— 20:510 min—
Mon 26 Oct— 20:500 min—
Sun 25 OctHaarlem 20:50No data—
Sat 24 OctAmsterdam Sloterdijk 20:59No data—
Fri 23 Oct— 20:500 min—
Thu 22 Oct— 20:51No data—
Wed 21 Oct— 20:53No data—
Tue 20 Oct— 20:50No data—
Mon 19 Oct— 20:510 min—
Sun 18 OctAmsterdam Sloterdijk 20:59Partial coverage0 min—
Sat 17 OctOverveen 20:460 min—
Fri 16 Oct— 20:500 min—