Train NS 4266 Leiden Centraal – Haarlem

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

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: Monday 20:50 from Leiden Centraal · Mon 16 Nov

Next departure 20:50 Monday · Leiden Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 12 full · 5 partial · 11 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 18 full · 5 partial · 25 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 8 Oct Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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