Train NS 4222 Den Haag Centraal – Haarlem

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

✓ Today’s run finished

Today, last fix heading to Heemstede-Aerdenhout at 10:22 0 min

  1. Den Haag Centraal09:25
  2. Den Haag Mariahoeve09:31
  3. Voorschoten09:36
  4. Leiden Centraal09:43
  5. Voorhout09:55
  6. Heemstede-Aerdenhout10:08
  7. Haarlem10:13

Next service: tomorrow 09:25 from Den Haag Centraal · Tue 17 Nov

Next departure 09:25 tomorrow · Den Haag Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 12 full · 7 partial · 9 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 17 full · 10 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Thu 12 Nov Max en route +4 min · last fix heading to Heemstede-Aerdenhout +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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