Train NS 4267 Amsterdam Centraal – Leiden Centraal

Amsterdam Centraal 19:26 → Leiden Centraal 20:10 Daily 0 h 44 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +6 min

Next service: today 19:26 from Amsterdam Centraal · Thu 5 Nov

Next departure 19:26 today · Amsterdam Centraal
On-time · 30 days
70%
7/10 runs under 3 min
RT coverage: 10 full · 0 partial · 14 no data
On-time · 90 days
75%
9/12 runs under 3 min
RT coverage: 12 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 +6 min · last fix heading to — +6 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Voorhout +5 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 9
  • 3–10 min 25% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 0% W n=1
  • 50% T n=2
  • 100% F n=2
  • 0% S n=1
  • 100% S n=2

Stops and timetable

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

Last 90 days, 12 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
19:26on time on time
19:31≈ on time ≈ +1 min
19:36≈ on time ≈ +1 min
19:40≈ on time ≈ +2 min
19:44 / 19:47≈ on time ≈ +2 min
19:52≈ on time ≈ +3 min
19:57≈ on time ≈ +4 min
20:04≈ on time ≈ +4 min
20:10on time +5 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 4 Nov— 20:19+6 min+6 min
Sun 1 NovVoorhout 20:190 min—
Sat 31 OctVoorhout 20:24+5 min+5 min
Fri 30 Oct— 20:11No data—
Thu 29 Oct— 20:110 min—
Wed 28 Oct— 20:14No data—
Tue 27 Oct— 20:18No data—
Mon 26 OctHaarlem 20:11No data—
Sun 25 OctVoorhout 20:20No data—
Sat 24 OctVoorhout 20:19No data—
Fri 23 Oct— 20:120 min—
Thu 22 Oct— 20:12No data—
Wed 21 Oct— 20:16No data—
Tue 20 Oct— 20:120 min—
Mon 19 Oct— 20:11No data—
Sun 18 OctVoorhout 20:200 min—
Sat 17 OctVoorhout 20:20No data—
Fri 16 OctHeemstede-Aerdenhout 20:06No data—
Thu 15 Oct— 20:26No data—
Wed 14 OctHaarlem 20:14No data—
Tue 13 Oct— 20:12No data—
Mon 12 Oct— 20:130 min—
Fri 9 Oct— 20:11+1 min+1 min
Thu 8 Oct— 20:17+4 min+4 min
Tue 6 Oct— 20:110 min—
Mon 5 Oct— 20:110 min—
Sun 4 OctVoorhout 20:19No data—
Sat 3 OctVoorhout 20:22No data—
Sun 27 SeptDen Haag Laan v NOI 20:51No data—
Sat 26 SeptVoorhout 20:20No data—