Train NS 2169 Amsterdam Centraal – Den Haag Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November +3 min

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

Next departure 20:20 today · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 31 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: +2 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

  • Fri 9 Oct Max en route +14 min · last fix heading to — +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=4
  • 100% T n=4
  • 67% F n=3
  • 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, 21 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
20:20on time on time
20:25≈ on time ≈ on time
20:35 / 20:37≈ on time ≈ +1 min
20:42≈ on time ≈ +1 min
20:57 / 21:02≈ on time ≈ +1 min
21: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— 21:14+3 min+3 min
Tue 3 Nov— 21:14No data—
Mon 2 Nov— 21:140 min+1 min
Sun 1 NovLeiden Centraal 21:170 min—
Sat 31 OctLeiden Centraal 21:160 min—
Fri 30 Oct— 21:20No data—
Thu 29 Oct— 21:140 min—
Wed 28 Oct— 21:140 min—
Tue 27 Oct— 21:15No data—
Mon 26 Oct— 21:14No data—
Sun 25 OctLeiden Centraal 21:16No data—
Sat 24 OctLeiden Centraal 21:220 min—
Fri 23 Oct— 21:17+1 min+2 min
Thu 22 Oct— 21:150 min—
Wed 21 Oct— 21:14No data—
Tue 20 Oct— 21:14No data—
Sun 18 OctLeiden Centraal 21:170 min—
Sat 17 OctLeiden Centraal 21:16No data—
Fri 16 Oct— 21:130 min—
Thu 15 Oct— 21:150 min—
Wed 14 Oct— 21:140 min—
Tue 13 Oct— 20:43No data—
Mon 12 Oct— 21:140 min—
Sun 11 OctAmsterdam Sloterdijk 20:400 min—
Sat 10 OctAmsterdam Sloterdijk 20:41+1 min+2 min
Fri 9 Oct— 21:41+14 min+14 min
Thu 8 Oct— 21:11+1 min+1 min
Wed 7 Oct— 21:14+1 min+2 min
Tue 6 Oct— 21:140 min—
Mon 5 Oct— 21:140 min—