Train NS 4218 Leiden Centraal → Haarlem

Leiden Centraal 08:50 → Haarlem 09:13 Mon, Tue, Wed, Thu, Fri, Sat 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

NS 4218 Leiden Centraal–Haarlem: final delay under 3 min on 19 of its 19 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:28 (GMT+1).

It does not run today

Last recorded run: Saturday 21 November 0 min

Next service: tomorrow 08:50 from Leiden Centraal · Mon 23 Nov

Next departure 08:50 tomorrow · Leiden Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 15 full · 4 partial · 5 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 23 full · 5 partial · 46 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=5
  • — S n=0

Stops and timetable

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

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