Train NS 4214 Den Haag Centraal – Haarlem

Den Haag Centraal 07:25 → Haarlem 08:13 Mon, Tue, Wed, Thu, Fri 0 h 48 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heemstede-Aerdenhout at 08:24 +3 min

  1. Den Haag Centraal07:25
  2. Den Haag Mariahoeve07:31
  3. Voorschoten07:36
  4. Leiden Centraal07:43
  5. Voorhout07:55
  6. Heemstede-Aerdenhout08:08
  7. Haarlem08:13

Next service: tomorrow 07:25 from Den Haag Centraal · Wed 18 Nov

Next departure 07:25 tomorrow · Den Haag Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 4 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 9 full · 14 partial · 41 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 Haarlem, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:25on time on time
07:28≈ on time ≈ on time
07:31≈ on time ≈ on time
07:36≈ on time ≈ on time
07:39≈ on time ≈ on time
07:43 / 07:50≈ on time ≈ on time
07:55≈ on time ≈ on time
08:02≈ on time ≈ on time
08:08≈ on time ≈ on time
08:13on 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
Tue 17 NovHeemstede-Aerdenhout 08:24Partial coverage+3 min+3 min
Mon 16 NovHeemstede-Aerdenhout 08:22Partial coverage+1 min—
Fri 13 NovHeemstede-Aerdenhout 08:220 min—
Thu 12 NovHeemstede-Aerdenhout 08:23Partial coverage+1 min—
Wed 11 NovHeemstede-Aerdenhout 08:23Partial coverage+1 min+1 min
Tue 10 NovHeemstede-Aerdenhout 08:23Partial coverage+1 min+1 min
Mon 9 NovHeemstede-Aerdenhout 08:22Partial coverage0 min—
Fri 6 NovAmsterdam Sloterdijk 08:44No data—
Thu 5 NovAmsterdam Sloterdijk 08:440 min—
Wed 4 NovAmsterdam Sloterdijk 08:440 min—
Tue 3 NovAmsterdam Sloterdijk 08:440 min—
Mon 2 NovAmsterdam Sloterdijk 08:440 min—
Fri 30 OctHeemstede-Aerdenhout 08:220 min—
Thu 29 OctHeemstede-Aerdenhout 08:25Partial coverage0 min—
Wed 28 OctHeemstede-Aerdenhout 08:22No data—
Tue 27 OctHeemstede-Aerdenhout 08:22No data—
Mon 26 OctHeemstede-Aerdenhout 08:22Partial coverage0 min—
Fri 23 OctHeemstede-Aerdenhout 08:220 min—
Thu 22 OctHeemstede-Aerdenhout 08:23Partial coverage0 min—
Wed 21 OctHeemstede-Aerdenhout 08:23No data—
Tue 20 OctVoorschoten 08:53Partial coverage0 min—
Mon 19 OctHeemstede-Aerdenhout 08:22Partial coverage0 min—
Fri 16 OctHeemstede-Aerdenhout 08:220 min—
Thu 15 OctHeemstede-Aerdenhout 08:22No data—
Wed 14 OctHeemstede-Aerdenhout 08:22No data—
Tue 13 OctHeemstede-Aerdenhout 08:23No data—
Mon 12 OctHeemstede-Aerdenhout 08:23No data—
Fri 9 OctHeemstede-Aerdenhout 08:220 min—
Thu 8 OctHeemstede-Aerdenhout 08:22Partial coverage0 min—
Wed 7 OctHeemstede-Aerdenhout 08:22Partial coverage0 min—