Train NS 2170 Den Haag Centraal – Amsterdam Centraal

Den Haag Centraal 21:17 → Amsterdam Centraal 22:10 Daily 0 h 53 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 21:17 from Den Haag Centraal · Sat 14 Nov

Next departure 21:17 today · Den Haag Centraal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 18 full · 4 partial · 6 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 29 full · 4 partial · 20 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 Amsterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=2
  • 100% W n=5
  • 100% T n=6
  • 100% F n=5
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 33 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:17on time on time
21:28 / 21:33≈ on time ≈ on time
21:48≈ on time ≈ +1 min
21:53 / 21:55≈ on time ≈ +1 min
22:04≈ on time ≈ +1 min
22:10on 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
Fri 13 Nov— 22:090 min—
Thu 12 Nov— 21:54+1 min+1 min
Wed 11 Nov— 21:540 min—
Mon 9 Nov— 21:530 min—
Sun 8 NovAmsterdam Sloterdijk 22:190 min+2 min
Sat 7 NovAmsterdam Sloterdijk 22:18Partial coverage0 min+1 min
Fri 6 Nov— 22:12+1 min+1 min
Thu 5 Nov— 21:540 min—
Wed 4 Nov— 21:540 min—
Tue 3 Nov— 21:54No data—
Mon 2 Nov— 21:530 min—
Sun 1 NovAmsterdam Sloterdijk 22:19Partial coverage0 min+1 min
Sat 31 OctAmsterdam Sloterdijk 22:22Partial coverage0 min—
Fri 30 Oct— 22:11No data—
Thu 29 Oct— 21:57+2 min+2 min
Wed 28 Oct— 21:540 min—
Tue 27 Oct— 21:55No data—
Mon 26 Oct— 21:530 min—
Sun 25 OctAmsterdam Sloterdijk 22:19No data—
Sat 24 OctAmsterdam Sloterdijk 22:190 min—
Fri 23 Oct— 22:12+1 min—
Thu 22 Oct— 21:550 min—
Wed 21 Oct— 21:55No data—
Tue 20 Oct— 21:54No data—
Mon 19 Oct— 21:540 min—
Sun 18 OctAmsterdam Sloterdijk 22:20+1 min+2 min
Sat 17 OctAmsterdam Sloterdijk 22:23Partial coverage0 min—
Fri 16 Oct— 22:120 min+1 min
Thu 15 Oct— 21:570 min—
Wed 14 Oct— 21:590 min—