Train NS 2161 Amsterdam Centraal – Den Haag Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:20 from Amsterdam Centraal · Thu 5 Nov

Next departure 18:20 today · Amsterdam Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 10 full · 5 partial · 13 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 12 full · 5 partial · 52 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 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 8 Oct Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
18:20on time on time
18:25≈ on time ≈ on time
18:35 / 18:37≈ on time ≈ on time
18:42≈ on time ≈ on time
18:57 / 19:02≈ on time ≈ +1 min
19:13on 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
Wed 4 Nov— 19:09No data—
Mon 2 NovAmsterdam Centraal 19:09No data—
Sun 1 NovLeiden Centraal 19:14Partial coverage0 min—
Sat 31 OctLeiden Centraal 19:17Partial coverage+1 min+1 min
Fri 30 OctHeemstede-Aerdenhout 19:140 min—
Thu 29 Oct— 01:250 min+2 min
Wed 28 Oct— 19:110 min—
Tue 27 Oct— 19:21No data—
Mon 26 Oct— 19:11No data—
Sun 25 OctLeiden Centraal 19:16No data—
Sat 24 OctLeiden Centraal 19:180 min—
Fri 23 OctLeiden Centraal 19:17Partial coverage+1 min+2 min
Thu 22 OctHeemstede-Aerdenhout 19:11No data—
Wed 21 OctHaarlem 19:11No data—
Tue 20 OctHeemstede-Aerdenhout 19:11No data—
Mon 19 OctHeemstede-Aerdenhout 18:55No data—
Sun 18 OctLeiden Centraal 19:19Partial coverage+1 min+2 min
Sat 17 OctLeiden Centraal 19:17No data—
Fri 16 OctLeiden Centraal 19:160 min—
Thu 15 OctAmsterdam Sloterdijk 19:19No data—
Wed 14 OctLeiden Centraal 19:31No data—
Tue 13 OctHaarlem 19:10No data—
Mon 12 OctHeemstede-Aerdenhout 19:110 min—
Sun 11 OctAmsterdam Sloterdijk 18:400 min—
Sat 10 OctAmsterdam Sloterdijk 18:390 min—
Fri 9 OctAmsterdam Sloterdijk 19:15Partial coverage0 min+1 min
Thu 8 Oct— 19:27+8 min+9 min
Wed 7 Oct— 19:10+1 min+1 min
Tue 6 Oct— 19:100 min—
Mon 5 Oct— 19:110 min—