Train NS 4224 Den Haag Centraal – Haarlem

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

Running now · updated 10:18

Position estimated from the timetable

Heading to Haarlem No data

Estimated arrival at Haarlem 10:43 · 15 km/h

  1. Den Haag Centraal09:55
  2. Den Haag Mariahoeve10:01
  3. Voorschoten10:06
  4. Leiden Centraal10:13
  5. Voorhout10:25
  6. Heemstede-Aerdenhout10:38
  7. Haarlem10:43
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 9 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 13 full · 11 partial · 57 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

Worst days

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

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 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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 10Today
09:55on time on time
09:58≈ on time ≈ on time
10:01≈ on time ≈ on time
10:06≈ on time ≈ on time
10:09≈ on time ≈ on time
10:13 / 10:20≈ on time ≈ on time
10:25≈ on time ≈ on time
10:32≈ on time ≈ on time
10:38≈ on time ≈ on time
10:43on 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 NovLeiden Centraal 10:14Partial coverageNo data—
Mon 16 NovHeemstede-Aerdenhout 10:52Partial coverage0 min—
Fri 13 NovHeemstede-Aerdenhout 10:520 min—
Thu 12 NovHeemstede-Aerdenhout 10:54Partial coverage+3 min+3 min
Wed 11 NovHeemstede-Aerdenhout 10:52Partial coverage+1 min—
Tue 10 NovHeemstede-Aerdenhout 10:54Partial coverage+2 min+3 min
Mon 9 NovHeemstede-Aerdenhout 10:54Partial coverage+1 min+2 min
Sun 8 NovHeemstede-Aerdenhout 10:520 min—
Sat 7 NovHeemstede-Aerdenhout 10:520 min—
Fri 6 NovAmsterdam Sloterdijk 11:14No data—
Thu 5 NovAmsterdam Sloterdijk 11:140 min—
Wed 4 NovAmsterdam Sloterdijk 11:140 min—
Tue 3 NovAmsterdam Sloterdijk 11:14No data—
Mon 2 NovAmsterdam Sloterdijk 11:14No data—
Sun 1 NovHeemstede-Aerdenhout 10:530 min—
Sat 31 OctHeemstede-Aerdenhout 10:52No data—
Fri 30 OctHeemstede-Aerdenhout 10:520 min—
Thu 29 OctHeemstede-Aerdenhout 10:52Partial coverage0 min—
Wed 28 OctHeemstede-Aerdenhout 10:52Partial coverage0 min—
Tue 27 OctHeemstede-Aerdenhout 10:52Partial coverage0 min—
Mon 26 OctHeemstede-Aerdenhout 10:52No data—
Sun 25 OctHeemstede-Aerdenhout 10:52No data—
Sat 24 OctHeemstede-Aerdenhout 10:520 min—
Fri 23 OctHeemstede-Aerdenhout 10:520 min—
Thu 22 OctHeemstede-Aerdenhout 10:53Partial coverage0 min—
Wed 21 OctHeemstede-Aerdenhout 10:54No data—
Tue 20 OctHeemstede-Aerdenhout 10:530 min—
Mon 19 OctHeemstede-Aerdenhout 10:52No data—
Sun 18 OctHeemstede-Aerdenhout 10:520 min—
Sat 17 OctHeemstede-Aerdenhout 10:520 min—