Train NS 5476 Zandvoort aan Zee – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 23:19 from Zandvoort aan Zee · Mon 16 Nov

Next departure 23:19 today · Zandvoort aan Zee
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 12 full · 6 partial · 10 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 23 full · 6 partial · 23 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: 0 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

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 100% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=5
  • 100% 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 10
23:19on time on time
23:25≈ on time ≈ on time
23:30 / 23:31≈ on time ≈ on time
23:34≈ on time ≈ +1 min
23:39≈ on time ≈ +1 min
23:44≈ on time ≈ +1 min
23:49on 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 NovAmsterdam Sloterdijk 23:58Partial coverage0 min—
Sat 14 Nov— 23:490 min—
Fri 13 Nov— 23:29+1 min—
Thu 12 Nov— 23:490 min—
Wed 11 Nov— 23:490 min—
Tue 10 Nov— 23:490 min—
Mon 9 Nov— 23:53+2 min+2 min
Sun 8 NovAmsterdam Sloterdijk 23:58Partial coverage0 min—
Sat 7 NovZandvoort aan Zee 23:49Partial coverage0 min—
Fri 6 Nov— 23:340 min+1 min
Thu 5 Nov— 23:490 min—
Wed 4 Nov— 23:490 min—
Mon 2 Nov— 23:490 min—
Sun 1 NovAmsterdam Sloterdijk 23:58Partial coverage0 min—
Sat 31 OctZandvoort aan Zee 23:33Partial coverage0 min—
Fri 30 Oct— 23:33No data—
Thu 29 Oct— 23:500 min—
Wed 28 Oct— 23:52No data—
Tue 27 Oct— 23:51No data—
Mon 26 Oct— 23:50No data—
Sun 25 Oct— 23:28No data—
Sat 24 Oct— 23:51No data—
Fri 23 Oct— 23:500 min—
Thu 22 Oct— 23:31No data—
Wed 21 Oct— 23:51No data—
Tue 20 Oct— 23:50No data—
Mon 19 Oct— 23:50No data—
Sun 18 OctAmsterdam Sloterdijk 23:58Partial coverage0 min—
Sat 17 OctOverveen 23:460 min—
Fri 16 Oct— 23:32+1 min+2 min