Train NS 4232 Den Haag Centraal – Haarlem

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

It has not run yet today

Last recorded run: Tuesday 17 November No data

Next service: today 11:55 from Den Haag Centraal · Wed 18 Nov

Next departure 11:55 today · Den Haag Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 9 full · 9 partial · 9 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 13 full · 13 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 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, 26 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
11:55on time on time
11:58≈ on time ≈ on time
12:01≈ on time ≈ on time
12:06≈ on time ≈ on time
12:09≈ on time ≈ on time
12:13 / 12:20≈ on time ≈ on time
12:25≈ on time ≈ on time
12:32≈ on time ≈ on time
12:38≈ on time ≈ on time
12: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 NovHeemstede-Aerdenhout 12:52Partial coverageNo data—
Mon 16 NovHeemstede-Aerdenhout 12:53Partial coverage0 min—
Fri 13 NovHeemstede-Aerdenhout 12:520 min—
Thu 12 NovHeemstede-Aerdenhout 12:53Partial coverage+1 min+2 min
Wed 11 NovHeemstede-Aerdenhout 12:52Partial coverage0 min—
Tue 10 NovHeemstede-Aerdenhout 12:52Partial coverage0 min—
Mon 9 NovHeemstede-Aerdenhout 12:52Partial coverage0 min—
Sun 8 NovHeemstede-Aerdenhout 12:520 min—
Sat 7 NovHeemstede-Aerdenhout 12:520 min—
Fri 6 NovAmsterdam Sloterdijk 13:17No data—
Thu 5 NovAmsterdam Sloterdijk 13:14No data—
Wed 4 NovAmsterdam Sloterdijk 13:140 min—
Tue 3 NovAmsterdam Sloterdijk 13:14No data—
Mon 2 NovAmsterdam Sloterdijk 13:14No data—
Sun 1 NovHeemstede-Aerdenhout 12:530 min—
Sat 31 OctHeemstede-Aerdenhout 12:520 min—
Fri 30 OctHeemstede-Aerdenhout 12:520 min—
Thu 29 OctHeemstede-Aerdenhout 12:52Partial coverage0 min—
Wed 28 OctHeemstede-Aerdenhout 12:52Partial coverage0 min—
Tue 27 OctHeemstede-Aerdenhout 12:52Partial coverage0 min—
Mon 26 OctHeemstede-Aerdenhout 12:52No data—
Sun 25 OctHeemstede-Aerdenhout 12:52No data—
Sat 24 OctHeemstede-Aerdenhout 12:520 min—
Fri 23 OctHeemstede-Aerdenhout 12:530 min—
Thu 22 OctHeemstede-Aerdenhout 12:52Partial coverage0 min—
Wed 21 OctHeemstede-Aerdenhout 12:53No data—
Tue 20 OctHeemstede-Aerdenhout 12:52No data—
Mon 19 OctHeemstede-Aerdenhout 12:52No data—
Sun 18 OctHeemstede-Aerdenhout 12:520 min—
Sat 17 OctHeemstede-Aerdenhout 12:520 min—