Train NS 4210 Den Haag Centraal – Amsterdam Centraal

Den Haag Centraal 06:25 → Amsterdam Centraal 07:35 Mon, Tue, Wed, Thu, Fri 1 h 10 min · 14 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:25 from Den Haag Centraal · Mon 9 Nov

Next departure 06:25 Monday · Den Haag Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 16 full · 2 partial · 3 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 44 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 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
06:25on time on time
06:28≈ on time ≈ on time
06:31≈ on time ≈ on time
06:36≈ on time ≈ on time
06:39≈ on time ≈ on time
06:43 / 06:51≈ on time ≈ on time
06:56≈ on time ≈ on time
07:04≈ on time ≈ on time
07:10≈ on time ≈ +1 min
07:15 / 07:17≈ on time ≈ +1 min
07:20≈ on time ≈ +1 min
07:25≈ on time ≈ +1 min
07:30≈ on time ≈ +1 min
07:35on 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
Fri 6 NovAmsterdam Sloterdijk 07:44No data—
Thu 5 NovAmsterdam Sloterdijk 07:44No data—
Wed 4 NovAmsterdam Sloterdijk 07:44Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 07:44Partial coverage0 min—
Mon 2 NovAmsterdam Sloterdijk 07:44No data—
Fri 30 OctHeemstede-Aerdenhout 07:220 min—
Thu 29 OctHeemstede-Aerdenhout 07:230 min—
Wed 28 OctHeemstede-Aerdenhout 07:220 min—
Tue 27 OctHeemstede-Aerdenhout 07:23+1 min—
Mon 26 OctHeemstede-Aerdenhout 07:25+1 min+1 min
Fri 23 OctHeemstede-Aerdenhout 07:220 min—
Thu 22 OctHeemstede-Aerdenhout 07:220 min—
Wed 21 OctHeemstede-Aerdenhout 07:220 min—
Tue 20 OctHeemstede-Aerdenhout 07:230 min—
Mon 19 OctHeemstede-Aerdenhout 07:220 min—
Fri 16 OctHeemstede-Aerdenhout 07:23+1 min+1 min
Thu 15 OctHeemstede-Aerdenhout 07:230 min—
Wed 14 OctHeemstede-Aerdenhout 07:220 min—
Tue 13 OctHeemstede-Aerdenhout 07:220 min—
Mon 12 OctHeemstede-Aerdenhout 07:220 min—
Fri 9 OctHeemstede-Aerdenhout 07:220 min—
Thu 8 OctHeemstede-Aerdenhout 07:22+1 min—
Wed 7 OctHeemstede-Aerdenhout 07:22No data—
Tue 6 OctHeemstede-Aerdenhout 07:220 min—
Mon 5 OctHeemstede-Aerdenhout 07:24No data—
Fri 2 OctHeemstede-Aerdenhout 07:23No data—
Thu 1 OctHeemstede-Aerdenhout 07:23No data—
Wed 30 SeptHeemstede-Aerdenhout 07:22No data—
Tue 29 SeptHeemstede-Aerdenhout 07:22No data—
Mon 28 SeptHeemstede-Aerdenhout 07:23No data—