Train NS 4269 Haarlem → Leiden Centraal

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 20:17 from Haarlem · Sat 21 Nov

Next departure 20:17 today · Haarlem
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 16 full · 5 partial · 6 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 24 full · 7 partial · 21 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 Leiden Centraal, 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 +12 min · last fix heading to — +12 min
  • Mon 16 Nov Max en route +12 min · last fix heading to — +12 min
  • Thu 19 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 3% · 1
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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:17on time +1 min
20:22≈ on time ≈ +2 min
20:27≈ on time ≈ +2 min
20:34≈ on time ≈ +4 min
20:40on time +4 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 20 Nov— 20:390 min—
Thu 19 Nov— 20:44+6 min+6 min
Wed 18 Nov— 20:390 min—
Tue 17 Nov— 20:400 min—
Mon 16 Nov— 20:59+12 min+12 min
Fri 13 Nov— 20:390 min—
Thu 12 Nov— 20:390 min—
Wed 11 Nov— 20:390 min—
Tue 10 Nov— 20:390 min—
Mon 9 Nov— 20:44+1 min+1 min
Sun 8 NovVoorhout 20:49Partial coverage0 min—
Sat 7 NovVoorhout 20:49Partial coverage0 min—
Fri 6 Nov— 20:420 min—
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:42+1 min+1 min
Tue 3 Nov— 20:480 min—
Mon 2 Nov— 20:39No data—
Sun 1 NovVoorhout 20:49Partial coverage0 min—
Sat 31 OctVoorhout 20:49Partial coverage0 min—
Fri 30 Oct— 20:41No data—
Thu 29 Oct— 20:410 min—
Wed 28 Oct— 20:41No data—
Tue 27 Oct— 21:000 min—
Mon 26 Oct— 20:53No data—
Sun 25 OctVoorhout 20:50No data—
Sat 24 OctVoorhout 20:56Partial coverage0 min—
Fri 23 Oct— 20:410 min—
Thu 22 Oct— 20:41No data—
Wed 21 Oct— 20:56No data—
Tue 20 Oct— 20:410 min—