Train NS 2125 Amsterdam Centraal – Haarlem

Amsterdam Centraal 09:20 → Haarlem 09:35 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 0 min

Next service: today 09:20 from Amsterdam Centraal · Mon 16 Nov

Next departure 09:20 today · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 5 no data
On-time · 90 days
95%
63/66 runs under 3 min
RT coverage: 62 full · 4 partial · 10 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 Haarlem, 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 +8 min · last fix heading to Leiden Centraal +7 min
  • Sat 22 Aug Max en route +10 min · last fix heading to Heemstede-Aerdenhout +7 min
  • Fri 25 Sept Max en route +10 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 29% · 19
  • On time 67% · 44
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 90% T n=10
  • 100% W n=10
  • 100% T n=11
  • 92% F n=12
  • 91% S n=11
  • 100% S n=2

Stops and timetable

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

Last 90 days, 67 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:20on time on time
09:25≈ on time ≈ +1 min
09:35on 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
Sat 14 NovAmsterdam Sloterdijk 09:39Partial coverage0 min—
Fri 13 NovLeiden Centraal 10:170 min+2 min
Thu 12 NovLeiden Centraal 10:12+1 min+1 min
Wed 11 NovLeiden Centraal 10:12+1 min+1 min
Tue 10 NovLeiden Centraal 10:18+7 min+8 min
Mon 9 NovLeiden Centraal 10:120 min—
Sat 7 NovAmsterdam Sloterdijk 09:39Partial coverage+1 min—
Fri 6 NovLeiden Centraal 10:17No data—
Thu 5 NovLeiden Centraal 10:13No data—
Wed 4 NovLeiden Centraal 10:13+2 min+2 min
Tue 3 NovLeiden Centraal 10:13No data—
Mon 2 NovLeiden Centraal 10:130 min—
Sat 31 OctAmsterdam Sloterdijk 09:40Partial coverage0 min+1 min
Fri 30 OctLeiden Centraal 10:170 min—
Thu 29 OctLeiden Centraal 10:120 min—
Wed 28 OctLeiden Centraal 10:12No data—
Tue 27 OctLeiden Centraal 10:120 min—
Mon 26 OctLeiden Centraal 10:120 min—
Sat 24 OctAmsterdam Sloterdijk 09:40Partial coverage+1 min—
Fri 23 OctLeiden Centraal 10:170 min—
Thu 22 OctLeiden Centraal 10:120 min—
Wed 21 OctLeiden Centraal 10:15No data—
Tue 20 OctLeiden Centraal 10:120 min—
Mon 19 OctLeiden Centraal 10:120 min—
Sat 17 OctAmsterdam Sloterdijk 09:40No data—
Fri 16 OctLeiden Centraal 10:160 min—
Thu 15 OctAmsterdam Sloterdijk 10:58No data—
Wed 14 OctLeiden Centraal 10:130 min—
Tue 13 OctLeiden Centraal 10:12No data—
Mon 12 OctLeiden Centraal 10:12No data—