Train NS 4260 Leiden Centraal – Haarlem

Leiden Centraal 19:20 → Haarlem 19:43 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 19:20 from Leiden Centraal · Sun 8 Nov

Next departure 19:20 today · Leiden Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 11 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 15 full · 5 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sat 31 Oct Max en route +6 min · last fix heading to Heemstede-Aerdenhout +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=1
  • 100% T n=2
  • 100% F n=6
  • 75% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 20 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
19:20on time on time
19:25≈ on time ≈ on time
19:32≈ on time ≈ +1 min
19:38≈ on time ≈ +1 min
19:43on 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
Sat 7 NovHeemstede-Aerdenhout 19:52Partial coverage0 min—
Fri 6 Nov— 20:040 min—
Thu 5 Nov— 20:12No data—
Wed 4 Nov— 20:040 min—
Mon 2 Nov— 20:040 min—
Sun 1 NovHeemstede-Aerdenhout 19:52Partial coverage0 min—
Sat 31 OctHeemstede-Aerdenhout 19:58Partial coverage+6 min+6 min
Fri 30 Oct— 19:440 min—
Thu 29 Oct— 19:440 min—
Wed 28 Oct— 19:44No data—
Tue 27 Oct— 19:53No data—
Mon 26 Oct— 19:44No data—
Sun 25 OctHeemstede-Aerdenhout 19:52No data—
Sat 24 OctHeemstede-Aerdenhout 19:53Partial coverage0 min—
Fri 23 OctVoorhout 19:47+2 min+3 min
Thu 22 Oct— 19:44No data—
Wed 21 Oct— 19:45No data—
Tue 20 Oct— 19:440 min—
Sun 18 OctHeemstede-Aerdenhout 19:52Partial coverage0 min—
Sat 17 OctHeemstede-Aerdenhout 19:52No data—
Fri 16 OctHeemstede-Aerdenhout 19:520 min—
Thu 15 Oct— 19:54No data—
Wed 14 OctHeemstede-Aerdenhout 19:52No data—
Tue 13 Oct— 19:45No data—
Mon 12 Oct— 19:440 min—
Fri 9 Oct— 19:44+1 min+1 min
Thu 8 Oct— 19:43+3 min+3 min
Tue 6 Oct— 19:440 min—
Mon 5 Oct— 19:440 min—
Sun 4 OctHeemstede-Aerdenhout 19:52No data—