Train NS 5418 Haarlem – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 09:29 0 min

  1. Haarlem09:01
  2. Haarlem Spaarnwoude09:04
  3. Halfweg-Zwanenburg09:09
  4. Amsterdam Sloterdijk09:14
  5. Amsterdam Centraal09:19

Next service: tomorrow 09:01 from Haarlem · Wed 18 Nov

Next departure 09:01 tomorrow · Haarlem
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 21 full · 2 partial · 7 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 31 full · 2 partial · 56 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 +5 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=6
  • 100% T n=4
  • 100% F n=3
  • 83% 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, 33 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
09:01on time on time
09:04≈ on time ≈ on time
09:09≈ on time ≈ on time
09:14≈ on time ≈ +1 min
09:19on 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 NovAmsterdam Sloterdijk 09:29Partial coverage0 min—
Mon 16 NovAmsterdam Sloterdijk 09:29Partial coverage+1 min+1 min
Sun 15 NovAmsterdam Sloterdijk 09:280 min—
Sat 14 NovAmsterdam Sloterdijk 09:280 min—
Fri 13 NovAmsterdam Sloterdijk 09:280 min—
Thu 12 NovAmsterdam Sloterdijk 09:280 min—
Wed 11 NovAmsterdam Sloterdijk 09:280 min—
Tue 10 NovAmsterdam Sloterdijk 09:34+5 min+5 min
Mon 9 NovAmsterdam Sloterdijk 09:280 min—
Sun 8 NovAmsterdam Sloterdijk 09:29+1 min—
Sat 7 NovAmsterdam Sloterdijk 09:29+4 min+4 min
Fri 6 NovAmsterdam Sloterdijk 09:28No data—
Thu 5 NovAmsterdam Sloterdijk 09:29No data—
Wed 4 NovAmsterdam Sloterdijk 09:280 min—
Tue 3 NovAmsterdam Sloterdijk 09:29No data—
Mon 2 NovAmsterdam Sloterdijk 09:28No data—
Sun 1 NovAmsterdam Sloterdijk 09:290 min—
Sat 31 OctAmsterdam Sloterdijk 09:280 min—
Fri 30 OctAmsterdam Sloterdijk 09:28No data—
Thu 29 OctAmsterdam Sloterdijk 09:290 min—
Wed 28 OctAmsterdam Sloterdijk 09:280 min—
Tue 27 OctAmsterdam Sloterdijk 09:280 min—
Mon 26 OctAmsterdam Sloterdijk 09:33No data—
Sun 25 OctAmsterdam Sloterdijk 09:28No data—
Sat 24 OctAmsterdam Sloterdijk 09:29+1 min—
Fri 23 OctAmsterdam Sloterdijk 09:280 min—
Thu 22 OctAmsterdam Sloterdijk 09:280 min—
Wed 21 OctAmsterdam Sloterdijk 09:280 min—
Tue 20 OctAmsterdam Sloterdijk 09:290 min—
Mon 19 OctAmsterdam Sloterdijk 09:290 min—