Train NS 2166 Haarlem – Amsterdam Centraal

Haarlem 20:55 → Amsterdam Centraal 21:10 Daily 0 h 15 min · 3 stops NS (Nederlandse Spoorwegen)

Running now · updated 20:57

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 21:10 · 49 km/h

  1. Haarlem20:55
  2. Amsterdam Sloterdijk21:04
  3. Amsterdam Centraal21:10

Today it is running no worse than usual: typical arrival delay is +1 min; 90% of the last 21 runs arrived on time.

On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 7 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 29 full · 1 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

  • Thu 8 Oct Max en route +14 min · last fix heading to — +13 min
  • Wed 4 Nov Max en route +10 min · last fix heading to — +10 min
  • Sun 8 Nov Max en route +6 min · last fix heading to Amsterdam Sloterdijk +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 90% · 27
  • 3–10 min 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=2
  • 67% W n=3
  • 67% T n=3
  • 100% F n=6
  • 100% S n=5
  • 80% S n=5

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 10Today
20:55on time on time
21:04≈ on time ≈ +2 min
21:10+1 min +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
Sun 15 NovHaarlem 20:54Partial coverage0 min—
Sat 14 NovAmsterdam Sloterdijk 21:190 min—
Fri 13 Nov— 21:09+1 min—
Thu 12 Nov— 20:540 min—
Wed 11 Nov— 21:09+1 min—
Tue 10 Nov— 21:09+1 min+2 min
Mon 9 Nov— 21:12+1 min+1 min
Sun 8 NovAmsterdam Sloterdijk 21:24+5 min+6 min
Sat 7 NovAmsterdam Sloterdijk 21:19+1 min—
Fri 6 Nov— 21:090 min—
Thu 5 Nov— 21:12No data—
Wed 4 Nov— 21:24+10 min+10 min
Tue 3 Nov— 21:20No data—
Mon 2 Nov— 21:12+1 min+1 min
Sun 1 NovAmsterdam Sloterdijk 21:19+1 min—
Sat 31 OctAmsterdam Sloterdijk 21:220 min—
Fri 30 Oct— 21:150 min—
Wed 28 Oct— 21:12No data—
Tue 27 Oct— 21:24No data—
Mon 26 Oct— 21:120 min—
Sun 25 OctAmsterdam Sloterdijk 21:19No data—
Sat 24 OctAmsterdam Sloterdijk 21:280 min—
Fri 23 Oct— 21:13+1 min—
Thu 22 Oct— 21:120 min—
Wed 21 Oct— 21:12No data—
Mon 19 Oct— 21:140 min—
Sun 18 OctAmsterdam Sloterdijk 21:20+1 min+2 min
Sat 17 OctAmsterdam Sloterdijk 21:19No data—
Fri 16 Oct— 21:13+2 min+2 min
Thu 15 Oct— 21:14No data—