Train NS 4234 Leiden Centraal – Haarlem

Leiden Centraal 12:50 → Haarlem 13:13 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 12:50 from Leiden Centraal · Mon 9 Nov

Next departure 12:50 today · Leiden Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 8 full · 7 partial · 13 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 14 full · 7 partial · 61 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: 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

Worst days

  • Sat 3 Oct Max en route +14 min · last fix heading to Halfweg-Zwanenburg +13 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Heemstede-Aerdenhout +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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