Train NS 2179 Amsterdam Centraal – Den Haag Centraal

Amsterdam Centraal 22:50 → Den Haag Centraal 23:43 Fri, Sat 0 h 53 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 22:50 from Amsterdam Centraal · Sat 7 Nov

Next departure 22:50 today · Amsterdam Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 0 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 23% · 3
  • On time 77% · 10
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=5
  • 100% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 13 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
22:50on time on time
22:55≈ on time ≈ on time
23:05 / 23:07≈ on time ≈ on time
23:12≈ on time ≈ on time
23:27 / 23:32≈ on time ≈ on time
23:43on time on time

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 6 Nov— 23:440 min—
Sat 31 OctHeemstede-Aerdenhout 23:470 min—
Fri 30 Oct— 23:470 min—
Fri 23 Oct— 23:450 min—
Sat 17 OctLeiden Centraal 23:460 min—
Fri 16 Oct— 23:48+2 min+6 min
Sat 10 Oct— 23:080 min+1 min
Fri 9 Oct— 23:440 min—
Sat 3 OctAmsterdam Sloterdijk 00:52−1 min+2 min
Sat 26 SeptAmsterdam Sloterdijk 00:39−1 min+1 min
Sat 19 SeptAmsterdam Centraal 00:16−1 min—
Mon 14 SeptAmsterdam Sloterdijk 19:240 min—
Sun 13 SeptAmsterdam Sloterdijk 23:10No data—
Sat 12 SeptAmsterdam Sloterdijk 23:09No data—
Sat 5 SeptAmsterdam Sloterdijk 00:55−2 min+1 min
Sun 23 AugLeiden Centraal 23:48No data—
Sat 22 AugLeiden Centraal 23:46No data—
Sat 15 AugHeemstede-Aerdenhout 23:21No data—