Train NS 4216 Den Haag Centraal – Amsterdam Centraal

Den Haag Centraal 07:55 → Amsterdam Centraal 09:05 Daily 1 h 10 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 09:14 No data

  1. Den Haag Centraal07:55
  2. Den Haag Mariahoeve08:01
  3. De Vink08:09
  4. Hillegom08:34
  5. Haarlem08:45
  6. Amsterdam Sloterdijk09:00
  7. Amsterdam Centraal09:05

Next service: tomorrow 07:55 from Den Haag Centraal · Sat 7 Nov

Next departure 07:55 tomorrow · Den Haag Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 9 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 60 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 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
07:55on time on time
07:58≈ on time ≈ on time
08:01≈ on time ≈ on time
08:06≈ on time ≈ on time
08:09≈ on time ≈ on time
08:13 / 08:21≈ on time ≈ on time
08:26≈ on time ≈ on time
08:34≈ on time ≈ on time
08:40≈ on time ≈ on time
08:45 / 08:47≈ on time ≈ on time
08:50≈ on time ≈ on time
08:55≈ on time ≈ on time
09:00≈ on time ≈ on time
09:05on 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 NovAmsterdam Sloterdijk 09:14No data—
Thu 5 NovAmsterdam Sloterdijk 09:14No data—
Wed 4 NovAmsterdam Sloterdijk 09:14Partial coverage+2 min+2 min
Tue 3 NovAmsterdam Sloterdijk 09:14No data—
Mon 2 NovAmsterdam Sloterdijk 09:14No data—
Sun 1 NovHeemstede-Aerdenhout 08:520 min+1 min
Sat 31 OctHeemstede-Aerdenhout 08:520 min—
Fri 30 OctHeemstede-Aerdenhout 08:520 min—
Thu 29 OctHeemstede-Aerdenhout 08:540 min—
Wed 28 OctHeemstede-Aerdenhout 08:520 min—
Tue 27 OctHeemstede-Aerdenhout 08:520 min—
Mon 26 OctHeemstede-Aerdenhout 08:520 min—
Sun 25 OctHeemstede-Aerdenhout 08:52No data—
Sat 24 OctHeemstede-Aerdenhout 08:520 min—
Fri 23 OctHeemstede-Aerdenhout 08:570 min—
Thu 22 OctHeemstede-Aerdenhout 08:520 min—
Wed 21 OctHeemstede-Aerdenhout 08:520 min—
Tue 20 OctHeemstede-Aerdenhout 08:550 min—
Mon 19 OctHeemstede-Aerdenhout 08:520 min—
Sun 18 OctHeemstede-Aerdenhout 08:520 min—
Sat 17 OctHeemstede-Aerdenhout 08:520 min—
Fri 16 OctHeemstede-Aerdenhout 08:52No data—
Thu 15 OctHeemstede-Aerdenhout 08:52No data—
Wed 14 OctHeemstede-Aerdenhout 08:52No data—
Tue 13 OctHeemstede-Aerdenhout 08:52No data—
Mon 12 OctHeemstede-Aerdenhout 08:520 min—
Fri 9 OctHeemstede-Aerdenhout 08:54+2 min+2 min
Thu 8 OctHeemstede-Aerdenhout 08:53+2 min+2 min
Wed 7 OctHeemstede-Aerdenhout 08:520 min—
Tue 6 OctHeemstede-Aerdenhout 08:520 min—