Train NS 2159 Amsterdam Centraal – Den Haag Centraal

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

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 17:50 from Amsterdam Centraal · Tue 10 Nov

Next departure 17:50 today · Amsterdam Centraal
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 11 full · 6 partial · 12 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 18 full · 6 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Den Haag 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 29 Oct Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Haarlem +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 100% W n=2
  • 67% T n=3
  • 100% F n=3
  • 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, 24 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:50on time on time
17:55≈ on time ≈ on time
18:05 / 18:06≈ on time ≈ on time
18:11≈ on time ≈ +1 min
18:26 / 18:28≈ on time ≈ +1 min
18:39on 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
Mon 9 NovHeemstede-Aerdenhout 18:39Partial coverage+1 min+1 min
Sun 8 NovLeiden Centraal 18:470 min+1 min
Sat 7 NovLeiden Centraal 18:470 min—
Fri 6 NovLeiden Centraal 18:440 min+1 min
Thu 5 NovHeemstede-Aerdenhout 18:44No data—
Wed 4 NovHeemstede-Aerdenhout 18:39No data—
Tue 3 NovHeemstede-Aerdenhout 18:39No data—
Mon 2 NovHaarlem 18:47Partial coverage+4 min+4 min
Sun 1 NovLeiden Centraal 18:470 min—
Sat 31 OctLeiden Centraal 18:460 min—
Fri 30 OctLeiden Centraal 18:46No data—
Thu 29 OctAmsterdam Sloterdijk 18:51Partial coverage+4 min+4 min
Wed 28 OctHeemstede-Aerdenhout 18:41Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 18:42No data—
Mon 26 OctHaarlem 18:400 min—
Sun 25 OctLeiden Centraal 18:47No data—
Sat 24 OctLeiden Centraal 18:490 min—
Fri 23 OctLeiden Centraal 18:48+2 min+3 min
Thu 22 OctLeiden Centraal 18:49Partial coverage0 min—
Wed 21 OctLeiden Centraal 18:42No data—
Tue 20 OctLeiden Centraal 18:43Partial coverage0 min—
Mon 19 OctLeiden Centraal 18:43No data—
Sun 18 OctLeiden Centraal 18:460 min—
Sat 17 OctLeiden Centraal 18:460 min—
Fri 16 OctLeiden Centraal 18:46No data—
Thu 15 OctLeiden Centraal 18:43No data—
Wed 14 OctLeiden Centraal 18:42No data—
Tue 13 OctLeiden Centraal 18:47No data—
Mon 12 OctLeiden Centraal 18:530 min—
Sun 11 OctAmsterdam Sloterdijk 18:090 min—