Train NS 4226 Den Haag Centraal → Haarlem

Den Haag Centraal 10:25 → Haarlem 11:13 Daily 0 h 48 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 10:25 from Den Haag Centraal · Sat 21 Nov

Next departure 10:25 today · Den Haag Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 17 full · 3 partial · 7 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 25 full · 5 partial · 52 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

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

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

On-time by weekday

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

Stops and timetable

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

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