Train NS 4271 Haarlem – Leiden Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 21:13 +1 min

  1. Haarlem20:47
  2. Heemstede-Aerdenhout20:52
  3. Hillegom20:57
  4. Voorhout21:04
  5. Leiden Centraal21:10

Next service: tomorrow 20:47 from Haarlem · Thu 12 Nov

Next departure 20:47 tomorrow · Haarlem
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 8 full · 4 partial · 15 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 14 full · 4 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 6 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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