Train NS 4283 Haarlem – Leiden Centraal

Haarlem 23:47 → Leiden Centraal 00:10 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 23:47 from Haarlem · Fri 13 Nov

Next departure 23:47 today · Haarlem
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 partial · 6 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 23 full · 4 partial · 14 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: +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

  • Thu 29 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=6
  • 67% T n=3
  • 100% F n=4
  • 100% S n=1
  • 100% S n=4

Stops and timetable

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

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