Train NS 4212 Den Haag Centraal – Amsterdam Centraal

Den Haag Centraal 06:55 → Amsterdam Centraal 08:05 Mon, Tue, Wed, Thu, Fri, Sat 1 h 10 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Den Haag Centraal06:55
  2. Den Haag Mariahoeve07:01
  3. De Vink07:09
  4. Hillegom07:34
  5. Haarlem07:45
  6. Amsterdam Sloterdijk08:00
  7. Amsterdam Centraal08:05

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

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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=3
  • — S n=0

Stops and timetable

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

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