Train NS 2154 Den Haag Centraal – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Friday 13 November +1 min

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

Next departure 17:17 today · Den Haag Centraal
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 9 full · 7 partial · 13 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 17 full · 8 partial · 63 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: +2 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 +13 min · last fix heading to Haarlem +12 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Fri 6 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 50% T n=2
  • 100% W n=2
  • 80% T n=5
  • 80% F n=5
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 25 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
17:17on time on time
17:28 / 17:33≈ on time ≈ +1 min
17:48≈ on time ≈ +2 min
17:53 / 17:55≈ on time ≈ +2 min
18:04≈ on time ≈ +3 min
18:10on 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
Fri 13 NovAmsterdam Sloterdijk 18:18Partial coverage+1 min+2 min
Thu 12 NovAmsterdam Sloterdijk 18:18+1 min+1 min
Wed 11 NovAmsterdam Sloterdijk 18:18+1 min+3 min
Tue 10 NovAmsterdam Sloterdijk 18:18+5 min+6 min
Mon 9 NovAmsterdam Sloterdijk 18:18+1 min—
Sun 8 NovAmsterdam Sloterdijk 18:19No data—
Sat 7 NovAmsterdam Sloterdijk 18:19Partial coverage+1 min+1 min
Fri 6 NovAmsterdam Sloterdijk 18:18Partial coverage+3 min+3 min
Thu 5 NovAmsterdam Sloterdijk 18:180 min—
Wed 4 NovDen Haag Centraal 18:44No data—
Tue 3 NovAmsterdam Sloterdijk 18:18No data—
Mon 2 NovAmsterdam Sloterdijk 18:18No data—
Sun 1 NovAmsterdam Sloterdijk 18:20Partial coverage0 min+1 min
Sat 31 OctAmsterdam Sloterdijk 18:19Partial coverage0 min+1 min
Fri 30 OctAmsterdam Sloterdijk 18:18Partial coverage0 min—
Thu 29 OctHaarlem 18:120 min—
Wed 28 OctAmsterdam Sloterdijk 18:18No data—
Tue 27 OctHaarlem 18:34No data—
Mon 26 OctAmsterdam Sloterdijk 18:18+1 min—
Sun 25 OctAmsterdam Sloterdijk 18:19No data—
Sat 24 OctAmsterdam Sloterdijk 18:220 min—
Fri 23 OctAmsterdam Sloterdijk 18:190 min—
Thu 22 OctAmsterdam Sloterdijk 18:18No data—
Wed 21 OctAmsterdam Sloterdijk 18:18No data—
Tue 20 OctAmsterdam Sloterdijk 18:18No data—
Mon 19 OctAmsterdam Sloterdijk 18:18No data—
Sun 18 OctAmsterdam Sloterdijk 18:19Partial coverage0 min+1 min
Sat 17 OctAmsterdam Sloterdijk 18:21No data—
Fri 16 OctAmsterdam Sloterdijk 18:19No data—
Thu 15 OctAmsterdam Sloterdijk 18:180 min—