Train NS 5420 Haarlem – Amsterdam Centraal

Haarlem 09:31 → Amsterdam Centraal 09:49 Daily 0 h 18 min · 5 stops NS (Nederlandse Spoorwegen)

Running now · updated 09:42

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 09:49 · 63 km/h

  1. Haarlem09:31
  2. Haarlem Spaarnwoude09:34
  3. Halfweg-Zwanenburg09:39
  4. Amsterdam Sloterdijk09:44
  5. Amsterdam Centraal09:49

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

On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 18 full · 2 partial · 10 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 27 full · 2 partial · 60 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 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

  • Tue 10 Nov Max en route +7 min · last fix heading to Amsterdam Sloterdijk +7 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 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
09:31on time on time
09:34≈ on time ≈ on time
09:39≈ on time ≈ on time
09:44≈ on time ≈ +1 min
09: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
Tue 17 NovHalfweg-Zwanenburg 09:39Partial coverage0 min—
Mon 16 NovAmsterdam Sloterdijk 09:58Partial coverage0 min—
Sun 15 NovAmsterdam Sloterdijk 09:580 min—
Sat 14 NovAmsterdam Sloterdijk 09:580 min—
Fri 13 NovAmsterdam Sloterdijk 09:580 min—
Thu 12 NovAmsterdam Sloterdijk 09:580 min—
Wed 11 NovAmsterdam Sloterdijk 09:580 min—
Tue 10 NovAmsterdam Sloterdijk 10:04+7 min+7 min
Mon 9 NovAmsterdam Sloterdijk 09:580 min—
Sun 8 NovAmsterdam Sloterdijk 09:580 min—
Sat 7 NovAmsterdam Sloterdijk 09:580 min—
Fri 6 NovAmsterdam Sloterdijk 09:58No data—
Thu 5 NovAmsterdam Sloterdijk 10:02No data—
Wed 4 NovAmsterdam Sloterdijk 09:580 min—
Tue 3 NovAmsterdam Sloterdijk 09:58No data—
Mon 2 NovAmsterdam Sloterdijk 09:580 min—
Sun 1 NovAmsterdam Sloterdijk 09:59+1 min+1 min
Sat 31 OctAmsterdam Sloterdijk 09:580 min—
Fri 30 OctAmsterdam Sloterdijk 09:58No data—
Thu 29 OctAmsterdam Sloterdijk 10:00No data—
Wed 28 OctAmsterdam Sloterdijk 09:580 min—
Tue 27 OctAmsterdam Sloterdijk 09:59No data—
Mon 26 OctAmsterdam Sloterdijk 09:59No data—
Sun 25 OctAmsterdam Sloterdijk 09:58No data—
Sat 24 OctAmsterdam Sloterdijk 10:00+1 min+1 min
Fri 23 OctAmsterdam Sloterdijk 09:580 min—
Thu 22 OctAmsterdam Sloterdijk 09:59No data—
Wed 21 OctAmsterdam Sloterdijk 09:580 min—
Tue 20 OctAmsterdam Sloterdijk 09:580 min—
Mon 19 OctAmsterdam Sloterdijk 09:58No data—