Train NS 5482 Zandvoort aan Zee – Haarlem

Zandvoort aan Zee 00:51 → Haarlem 01:02 Fri, Sat 0 h 11 min · 3 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:04 +1 min

  1. Zandvoort aan Zee00:51
  2. Overveen00:58
  3. Haarlem01:02

Next service: Friday 00:51 from Zandvoort aan Zee · Fri 13 Nov

Next departure 00:51 Friday · Zandvoort aan Zee
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 3 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 4 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 Haarlem, 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

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

  • Early 0% · 0
  • On time 100% · 6
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=5
  • 100% S n=1

Stops and timetable

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

Last 90 days, 6 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
00:51on time on time
00:58≈ on time ≈ +1 min
01:02on 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
Sat 7 Nov— 01:04+1 min—
Sun 1 Nov— 01:03No data—
Sat 31 Oct— 01:030 min—
Sun 25 Oct— 01:04No data—
Sat 24 Oct— 01:040 min—
Sun 18 OctOverveen 01:16No data—
Sat 17 Oct— 01:03+1 min—
Sun 11 Oct— 01:040 min—
Sat 10 Oct— 01:030 min—
Mon 24 AugAmsterdam Sloterdijk 01:26No data—