Train NS 5485 Amsterdam Centraal – Zandvoort aan Zee

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

✓ Today’s run finished

Today, last fix heading to — at 00:42 0 min

  1. Amsterdam Centraal00:11
  2. Amsterdam Sloterdijk00:16
  3. Halfweg-Zwanenburg00:21
  4. Haarlem Spaarnwoude00:26
  5. Haarlem00:29
  6. Overveen00:35
  7. Zandvoort aan Zee00:41

Next service: tomorrow 00:11 from Amsterdam Centraal · Sun 8 Nov

Next departure 00:11 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 2 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • 100% T n=4
  • 100% W n=3
  • 100% T n=4
  • 100% F n=2
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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:11on time on time
00:16≈ on time ≈ on time
00:21≈ on time ≈ on time
00:26≈ on time ≈ on time
00:29 / 00:31≈ on time ≈ on time
00:35≈ on time ≈ on time
00:41on time on time

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— 00:420 min—
Fri 6 Nov— 00:29No data—
Thu 5 Nov— 00:290 min—
Tue 3 Nov— 00:290 min—
Sun 1 NovHaarlem Spaarnwoude 00:390 min—
Sat 31 Oct— 00:420 min—
Fri 30 Oct— 00:300 min—
Thu 29 Oct— 00:350 min—
Wed 28 Oct— 00:310 min—
Tue 27 Oct— 00:300 min—
Sun 25 OctHaarlem Spaarnwoude 00:40No data—
Sat 24 Oct— 00:430 min—
Thu 22 Oct— 00:300 min—
Wed 21 Oct— 00:300 min—
Tue 20 Oct— 00:310 min—
Sun 18 OctHaarlem Spaarnwoude 00:400 min—
Sat 17 Oct— 00:420 min—
Sun 11 OctHaarlem Spaarnwoude 00:40+2 min+2 min
Sat 10 Oct— 00:420 min—
Fri 9 Oct— 00:440 min—
Thu 8 Oct— 00:300 min—
Wed 7 Oct— 00:300 min—
Tue 6 Oct— 00:360 min—
Sun 4 OctOverveen 00:49No data—
Sun 27 SeptHaarlem Spaarnwoude 00:40No data—
Mon 21 SeptHaarlem Spaarnwoude 00:47No data—
Sun 13 SeptHaarlem Spaarnwoude 00:40No data—
Sun 6 SeptHaarlem Spaarnwoude 00:40No data—
Sun 30 AugHaarlem Spaarnwoude 00:40No data—
Mon 24 AugHaarlem 00:49No data—