Train NS 4241 Haarlem – Leiden Centraal

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 13:17 from Haarlem · Mon 9 Nov

Next departure 13:17 today · Haarlem
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 8 full · 7 partial · 13 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 27 full · 7 partial · 48 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 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

  • Mon 24 Aug Max en route +15 min · last fix heading to Haarlem +14 min
  • Sun 18 Oct Max en route +12 min · last fix heading to Hillegom +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 32
  • 3–10 min 0% · 0
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 83% S n=6

Stops and timetable

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

Last 90 days, 34 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
13:17on time on time
13:22≈ on time ≈ on time
13:27≈ on time ≈ on time
13:34≈ on time ≈ on time
13:40on time on time

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
Sun 8 NovVoorhout 13:49Partial coverage0 min—
Sat 7 NovVoorhout 13:49Partial coverage0 min—
Fri 6 NovDen Haag Laan v NOI 14:14No data—
Thu 5 NovDen Haag Laan v NOI 14:18No data—
Wed 4 NovDen Haag Laan v NOI 14:140 min—
Tue 3 NovDen Haag Laan v NOI 14:14No data—
Mon 2 NovDen Haag Laan v NOI 14:140 min—
Sun 1 NovVoorhout 13:49Partial coverage0 min—
Sat 31 OctVoorhout 13:50Partial coverage0 min—
Fri 30 OctDen Haag Laan v NOI 14:160 min—
Thu 29 OctDen Haag Laan v NOI 14:16No data—
Wed 28 OctDen Haag Laan v NOI 14:150 min—
Tue 27 OctDen Haag Laan v NOI 14:160 min—
Mon 26 OctDen Haag Laan v NOI 14:15No data—
Sun 25 OctVoorhout 13:50No data—
Sat 24 OctVoorhout 13:50Partial coverage+1 min+1 min
Fri 23 OctDen Haag Laan v NOI 14:16No data—
Thu 22 OctDen Haag Laan v NOI 14:180 min—
Wed 21 OctDen Haag Laan v NOI 14:15No data—
Tue 20 OctLeiden Centraal 16:220 min—
Mon 19 OctDen Haag Laan v NOI 14:15No data—
Sun 18 OctHillegom 14:04Partial coverage+12 min+12 min
Sat 17 OctVoorhout 13:50Partial coverage0 min—
Fri 16 OctDen Haag Laan v NOI 14:230 min—
Thu 15 OctDen Haag Laan v NOI 14:15No data—
Wed 14 OctDen Haag Laan v NOI 14:15No data—
Tue 13 OctDen Haag Laan v NOI 14:16No data—
Mon 12 OctDen Haag Laan v NOI 14:15No data—
Fri 9 OctDen Haag Laan v NOI 14:160 min—
Thu 8 OctDen Haag Laan v NOI 14:150 min—