Train NS 5467 Amsterdam Centraal – Zandvoort aan Zee

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

✓ Today’s run finished

Today, last fix heading to Overveen at 20:24 +6 min

  1. Amsterdam Centraal19:41
  2. Amsterdam Sloterdijk19:46
  3. Halfweg-Zwanenburg19:51
  4. Haarlem Spaarnwoude19:56
  5. Haarlem19:59
  6. Overveen20:05
  7. Zandvoort aan Zee20:11

Next service: tomorrow 19:41 from Amsterdam Centraal · Mon 16 Nov

Next departure 19:41 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 10 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 23 full · 2 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

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

  • Sun 15 Nov Max en route +6 min · last fix heading to Overveen +6 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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 10
19:41on time on time
19:46≈ on time ≈ on time
19:51≈ on time ≈ on time
19:56≈ on time ≈ on time
19:59 / 20:01≈ on time ≈ on time
20:05≈ on time ≈ +1 min
20:11on time +1 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 NovOverveen 20:24Partial coverage+6 min+6 min
Sat 14 NovOverveen 20:19Partial coverage0 min—
Fri 13 Nov— 20:14+2 min+3 min
Thu 12 Nov— 20:190 min+7 min
Wed 11 Nov— 20:130 min—
Tue 10 Nov— 20:140 min—
Mon 9 Nov— 20:14+1 min—
Sun 8 NovOverveen 20:190 min+1 min
Sat 7 NovOverveen 20:190 min—
Fri 6 Nov— 20:130 min—
Thu 5 Nov— 20:13No data—
Wed 4 Nov— 20:140 min—
Sun 1 NovOverveen 20:190 min—
Sat 31 OctOverveen 20:20No data—
Fri 30 Oct— 20:150 min—
Thu 29 Oct— 20:140 min—
Wed 28 Oct— 20:130 min—
Tue 27 Oct— 20:16No data—
Mon 26 OctHalfweg-Zwanenburg 20:13No data—
Sun 25 OctOverveen 20:19No data—
Sat 24 OctOverveen 20:21No data—
Fri 23 Oct— 20:15+1 min+1 min
Thu 22 Oct— 20:14No data—
Wed 21 Oct— 20:13No data—
Tue 20 Oct— 20:14No data—
Mon 19 Oct— 20:13No data—
Sun 18 OctOverveen 20:200 min—
Sat 17 OctOverveen 20:140 min—
Fri 16 OctHalfweg-Zwanenburg 20:13No data—
Thu 15 Oct— 20:07No data—