Train NS 4272 Leiden Centraal – Amsterdam Centraal

Leiden Centraal 22:21 → Amsterdam Centraal 23:05 Daily 0 h 44 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 22:21 from Leiden Centraal · Thu 5 Nov

Next departure 22:21 today · Leiden Centraal
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 14 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 26 no data
Typical delay
+1min
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 Amsterdam 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 7 Oct Max en route +6 min · last fix heading to — +5 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 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 50% W n=2
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • 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
22:21on time on time
22:26≈ on time ≈ on time
22:34≈ on time ≈ +1 min
22:39≈ on time ≈ +1 min
22:45 / 22:47≈ on time ≈ +1 min
22:50≈ on time ≈ +2 min
22:55≈ on time ≈ +2 min
23:00≈ on time ≈ +2 min
23:05+1 min +2 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— 23:07+2 min+2 min
Sun 1 NovHeemstede-Aerdenhout 22:520 min—
Sat 31 OctHeemstede-Aerdenhout 22:52No data—
Fri 30 Oct— 22:44No data—
Thu 29 Oct— 22:440 min—
Wed 28 Oct— 22:44No data—
Tue 27 Oct— 22:57No data—
Mon 26 Oct— 22:44No data—
Sun 25 OctHeemstede-Aerdenhout 22:52No data—
Sat 24 OctHeemstede-Aerdenhout 22:48No data—
Fri 23 Oct— 22:440 min—
Thu 22 Oct— 22:45No data—
Wed 21 Oct— 22:44No data—
Mon 19 Oct— 22:45No data—
Sun 18 OctHeemstede-Aerdenhout 22:52+1 min—
Sat 17 OctHeemstede-Aerdenhout 22:52No data—
Fri 16 Oct— 22:440 min—
Thu 15 Oct— 22:44No data—
Wed 14 Oct— 22:47No data—
Tue 13 Oct— 22:45No data—
Mon 12 Oct— 22:44+2 min+2 min
Fri 9 Oct— 22:440 min—
Thu 8 Oct— 22:45+1 min+2 min
Wed 7 Oct— 22:55+5 min+6 min
Tue 6 Oct— 22:440 min—
Mon 5 Oct— 22:44+1 min+1 min
Sun 4 OctHeemstede-Aerdenhout 22:52No data—
Sat 3 OctHalfweg-Zwanenburg 23:07No data—
Sun 27 SeptHeemstede-Aerdenhout 22:52No data—
Sat 26 SeptHeemstede-Aerdenhout 22:52No data—