Train NS 4257 Haarlem – Leiden Centraal

Haarlem 17:17 → Leiden Centraal 17:40 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 17:17 from Haarlem · Sun 8 Nov

Next departure 17:17 today · Haarlem
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 10 full · 5 partial · 12 no data
On-time · 90 days
95%
40/42 runs under 3 min
RT coverage: 37 full · 5 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sun 4 Oct Max en route +8 min · last fix heading to Voorhout +6 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Den Haag Laan v NOI +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 40
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 42 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
17:17on time on time
17:22≈ on time ≈ on time
17:27≈ on time ≈ on time
17:34≈ on time ≈ on time
17: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
Sat 7 NovVoorhout 17:49Partial coverage0 min—
Fri 6 NovDen Haag Laan v NOI 18:14+1 min+1 min
Thu 5 NovDen Haag Laan v NOI 18:09No data—
Wed 4 NovDen Haag Laan v NOI 18:140 min—
Tue 3 NovDen Haag Laan v NOI 18:14No data—
Mon 2 NovDen Haag Laan v NOI 18:140 min—
Sun 1 NovVoorhout 17:49Partial coverage0 min—
Sat 31 OctVoorhout 17:50Partial coverage0 min—
Fri 30 OctDen Haag Laan v NOI 18:160 min—
Thu 29 OctDen Haag Laan v NOI 18:15No data—
Wed 28 OctDen Haag Laan v NOI 18:110 min—
Tue 27 OctDen Haag Laan v NOI 18:15No data—
Mon 26 OctDen Haag Laan v NOI 18:150 min—
Sun 25 OctVoorhout 17:50No data—
Sat 24 OctVoorhout 17:50Partial coverage0 min—
Fri 23 OctDen Haag Laan v NOI 18:17No data—
Thu 22 OctDen Haag Laan v NOI 18:120 min—
Wed 21 OctDen Haag Laan v NOI 18:15No data—
Tue 20 OctDen Haag Laan v NOI 18:150 min—
Mon 19 OctDen Haag Laan v NOI 18:15No data—
Sun 18 OctVoorhout 17:50No data—
Sat 17 OctVoorhout 17:50Partial coverage0 min—
Fri 16 OctDen Haag Laan v NOI 18:160 min—
Thu 15 OctDen Haag Laan v NOI 18:15No data—
Wed 14 OctDen Haag Laan v NOI 18:16No data—
Tue 13 OctDen Haag Laan v NOI 18:15No data—
Mon 12 OctDen Haag Laan v NOI 18:150 min—
Fri 9 OctDen Haag Laan v NOI 18:210 min+10 min
Thu 8 OctDen Haag Laan v NOI 18:17+6 min+6 min
Wed 7 OctDen Haag Laan v NOI 18:150 min—