Train NS 2120 Haarlem – Amsterdam Centraal

Haarlem 09:25 → Amsterdam Centraal 09:40 Mon, Tue, Wed, Thu, Fri, Sat 0 h 15 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November +5 min

Next service: today 09:25 from Haarlem · Mon 16 Nov

Next departure 09:25 today · Haarlem
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 14 full · 4 partial · 6 no data
On-time · 90 days
91%
59/65 runs under 3 min
RT coverage: 60 full · 5 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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 +11 min · last fix heading to Amsterdam Sloterdijk +11 min
  • Tue 15 Sept Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Sat 14 Nov Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Wed 23 Sept Max en route +9 min · last fix heading to Haarlem +4 min
  • Sun 13 Sept Max en route +30 min · last fix heading to Haarlem +4 min

Distribution · 90 days

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

  • Early 31% · 20
  • On time 60% · 39
  • 3–10 min 8% · 5
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 80% T n=10
  • 90% W n=10
  • 100% T n=11
  • 100% F n=12
  • 91% S n=11
  • 0% S n=1

Stops and timetable

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

Last 90 days, 65 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:25on time on time
09:34≈ on time ≈ +2 min
09:40on time +3 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 09:53Partial coverage+5 min+5 min
Fri 13 NovAmsterdam Sloterdijk 09:49+1 min—
Thu 12 NovAmsterdam Sloterdijk 09:50+1 min—
Wed 11 NovAmsterdam Sloterdijk 09:490 min+1 min
Tue 10 NovAmsterdam Sloterdijk 09:58+11 min+11 min
Mon 9 NovAmsterdam Sloterdijk 09:49+3 min+3 min
Sat 7 NovAmsterdam Sloterdijk 09:49Partial coverage+1 min—
Fri 6 NovAmsterdam Sloterdijk 09:49No data—
Thu 5 NovAmsterdam Sloterdijk 09:57No data—
Wed 4 NovAmsterdam Sloterdijk 09:490 min+1 min
Tue 3 NovAmsterdam Sloterdijk 09:59No data—
Mon 2 NovAmsterdam Sloterdijk 10:09No data—
Sat 31 OctAmsterdam Sloterdijk 09:49Partial coverage+1 min—
Fri 30 OctAmsterdam Sloterdijk 09:490 min—
Thu 29 OctAmsterdam Sloterdijk 09:510 min—
Wed 28 OctAmsterdam Sloterdijk 09:490 min—
Tue 27 OctAmsterdam Sloterdijk 09:490 min—
Mon 26 OctAmsterdam Sloterdijk 09:49No data—
Sat 24 OctAmsterdam Sloterdijk 09:49Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 09:490 min—
Thu 22 OctAmsterdam Sloterdijk 09:490 min—
Wed 21 OctAmsterdam Sloterdijk 09:54No data—
Tue 20 OctAmsterdam Sloterdijk 09:480 min—
Mon 19 OctAmsterdam Sloterdijk 09:490 min—
Sat 17 OctAmsterdam Sloterdijk 09:50Partial coverage+1 min+2 min
Fri 16 OctAmsterdam Sloterdijk 09:500 min—
Thu 15 OctHaarlem 10:58No data—
Wed 14 OctAmsterdam Sloterdijk 09:49No data—
Tue 13 OctAmsterdam Sloterdijk 09:49No data—
Mon 12 OctAmsterdam Sloterdijk 09:490 min—