Train NS 4279 Haarlem – Leiden Centraal

Haarlem 22:47 → Leiden Centraal 23:10 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 22:47 from Haarlem · Mon 16 Nov

Next departure 22:47 Monday · Haarlem
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 11 full · 4 partial · 13 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 18 full · 4 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 7 Oct Max en route +10 min · last fix heading to — +10 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
22:47on time +1 min
22:52≈ on time ≈ +1 min
22:57≈ on time ≈ +2 min
23:04≈ on time ≈ +3 min
23:10on 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 13 Nov— 23:090 min—
Thu 12 Nov— 23:090 min—
Wed 11 Nov— 23:090 min—
Tue 10 Nov— 23:090 min—
Mon 9 Nov— 23:14+1 min+1 min
Sun 8 NovVoorhout 23:19Partial coverage+2 min+2 min
Sat 7 NovVoorhout 23:18Partial coverage0 min—
Fri 6 Nov— 23:090 min—
Thu 5 Nov— 23:09No data—
Wed 4 Nov— 23:090 min—
Mon 2 Nov— 23:090 min—
Sun 1 NovVoorhout 23:19Partial coverage0 min—
Sat 31 OctVoorhout 23:18No data—
Fri 30 Oct— 23:11No data—
Thu 29 Oct— 23:110 min—
Wed 28 Oct— 23:11No data—
Tue 27 Oct— 23:18No data—
Mon 26 Oct— 23:11No data—
Sun 25 OctVoorhout 23:20No data—
Sat 24 Oct— 23:12No data—
Fri 23 Oct— 23:110 min—
Thu 22 Oct— 23:12No data—
Wed 21 Oct— 23:11No data—
Tue 20 Oct— 23:12No data—
Mon 19 Oct— 23:11No data—
Sun 18 OctVoorhout 23:21Partial coverage+3 min+3 min
Sat 17 OctVoorhout 23:20No data—
Fri 16 Oct— 23:110 min—
Thu 15 Oct— 23:19No data—
Wed 14 Oct— 23:17+2 min+2 min