Train NS 2164 Haarlem – Amsterdam Centraal

Haarlem 20:25 → Amsterdam Centraal 20:40 Daily 0 h 15 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 20:25 from Haarlem · Sun 15 Nov

Next departure 20:25 today · Haarlem
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 17 full · 1 partial · 9 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 29 full · 1 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Thu 8 Oct Max en route +14 min · last fix heading to — +14 min
  • Wed 4 Nov Max en route +7 min · last fix heading to — +6 min
  • Thu 12 Nov Max en route +5 min · last fix heading to — +5 min
  • Thu 29 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 26
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 80% W n=5
  • 25% T n=4
  • 100% F n=5
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 30 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
20:25on time on time
20:34≈ on time ≈ +3 min
20:40on time +5 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 14 NovAmsterdam Sloterdijk 20:49Partial coverage+1 min+2 min
Fri 13 Nov— 20:43+1 min+1 min
Thu 12 Nov— 20:34+5 min+5 min
Wed 11 Nov— 20:39+1 min+1 min
Tue 10 Nov— 20:39+1 min+1 min
Mon 9 Nov— 20:42+1 min—
Sun 8 NovAmsterdam Sloterdijk 20:49No data—
Sat 7 NovAmsterdam Sloterdijk 20:52+2 min+3 min
Fri 6 Nov— 20:420 min+1 min
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:48+6 min+7 min
Mon 2 Nov— 20:390 min—
Sun 1 NovAmsterdam Sloterdijk 20:49+1 min—
Sat 31 OctAmsterdam Sloterdijk 20:50+2 min+3 min
Thu 29 Oct— 20:41+5 min+5 min
Wed 28 Oct— 19:530 min—
Tue 27 Oct— 20:48No data—
Mon 26 OctDen Haag Centraal 20:47No data—
Sun 25 OctAmsterdam Sloterdijk 20:49No data—
Sat 24 OctHaarlem 21:190 min—
Fri 23 Oct— 20:410 min—
Thu 22 Oct— 20:41No data—
Wed 21 Oct— 20:42No data—
Tue 20 Oct— 20:42No data—
Mon 19 Oct— 19:470 min—
Sun 18 OctAmsterdam Sloterdijk 20:490 min+1 min
Sat 17 OctAmsterdam Sloterdijk 20:51No data—
Fri 16 OctDen Haag Centraal 20:42+1 min—
Thu 15 Oct— 20:450 min—
Wed 14 OctDen Haag Centraal 20:420 min—