Train NS 2178 Den Haag Centraal – Amsterdam Centraal

Den Haag Centraal 23:17 → Amsterdam Centraal 00:10 Fri, Sat 0 h 53 min · 6 stops NS (Nederlandse Spoorwegen)

Running now · updated 00:04

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 00:10 · 4 km/h

  1. Den Haag Centraal23:17
  2. Leiden Centraal23:28
  3. Heemstede-Aerdenhout23:48
  4. Haarlem23:53
  5. Amsterdam Sloterdijk00:04
  6. Amsterdam Centraal00:10

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 6 runs arrived on time.

On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 2 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 7 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=4
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 8 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 10Today
23:17on time on time
23:28 / 23:33≈ on time ≈ on time
23:48≈ on time ≈ +1 min
23:53 / 23:55≈ on time ≈ +2 min
00:04≈ on time ≈ +2 min
00:10on time +2 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 6 Nov— 23:590 min—
Sat 31 OctDen Haag Centraal 00:14No data—
Sat 24 Oct— 00:110 min—
Fri 23 Oct— 00:140 min—
Sat 17 OctAmsterdam Sloterdijk 00:19No data—
Fri 16 Oct— 00:11+1 min—
Sat 10 Oct— 00:120 min—
Fri 9 Oct— 00:110 min—
Sat 3 OctHaarlem 23:54No data—
Sat 26 SeptLeiden Centraal 23:47No data—
Sun 13 SeptAmsterdam Sloterdijk 00:19+1 min+2 min
Sun 23 AugHeemstede-Aerdenhout 00:05No data—
Sat 22 AugHeemstede-Aerdenhout 00:04No data—
Sat 15 AugDen Haag Centraal 23:21No data—
Sun 9 AugAmsterdam Sloterdijk 01:00+6 min+17 min