Train NS 2175 Amsterdam Centraal – Haarlem

Amsterdam Centraal 21:50 → Haarlem 22:05 Fri, Sat, Sun 0 h 15 min · 3 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November +15 min

Next service: Friday 21:50 from Amsterdam Centraal · Fri 20 Nov

Next departure 21:50 Friday · Amsterdam Centraal
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 7 full · 2 partial · 2 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Sun 15 Nov Max en route +15 min · last fix heading to Amsterdam Sloterdijk +15 min
  • Sun 8 Nov Max en route +7 min · last fix heading to Amsterdam Sloterdijk +7 min

Distribution · 90 days

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

  • Early 10% · 2
  • On time 81% · 17
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=5
  • 100% S n=6
  • 71% S n=7

Stops and timetable

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

Last 90 days, 21 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
21:50on time on time
21:55≈ on time ≈ on time
22:05on 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
Sun 15 NovAmsterdam Sloterdijk 22:24Partial coverage+15 min+15 min
Sat 14 NovAmsterdam Sloterdijk 22:09Partial coverage0 min+1 min
Fri 13 Nov— 22:48+2 min+3 min
Sun 8 NovAmsterdam Sloterdijk 22:19+7 min+7 min
Sat 7 NovLeiden Centraal 22:44+1 min+2 min
Fri 6 Nov— 22:44+1 min—
Sun 1 NovAmsterdam Sloterdijk 22:090 min—
Sat 31 OctLeiden Centraal 22:46No data—
Sun 25 OctAmsterdam Sloterdijk 22:10No data—
Sat 24 OctLeiden Centraal 22:470 min—
Fri 23 Oct— 22:47+1 min—
Sun 18 OctAmsterdam Sloterdijk 22:100 min—
Sat 17 OctLeiden Centraal 22:46No data—
Fri 16 Oct— 22:450 min—
Sun 11 OctAmsterdam Sloterdijk 22:100 min—
Sat 10 OctAmsterdam Sloterdijk 22:090 min+1 min
Fri 9 Oct— 22:440 min—
Sun 4 OctAmsterdam Sloterdijk 00:04−1 min—
Sat 3 OctAmsterdam Sloterdijk 23:060 min—
Mon 28 SeptAmsterdam Sloterdijk 20:070 min—
Sun 27 SeptAmsterdam Sloterdijk 22:10No data—
Sat 26 SeptLeiden Centraal 22:46No data—
Mon 21 SeptAmsterdam Sloterdijk 22:200 min—
Sun 20 SeptAmsterdam Sloterdijk 22:10No data—
Sat 19 SeptLeiden Centraal 22:46No data—
Mon 14 SeptAmsterdam Sloterdijk 19:240 min—
Sun 13 SeptAmsterdam Sloterdijk 00:560 min—
Sat 12 SeptAmsterdam Sloterdijk 00:46−6 min+3 min
Sun 6 SeptAmsterdam Sloterdijk 22:09No data—
Sat 5 SeptLeiden Centraal 22:46No data—