Train NS 4269 Amsterdam Centraal – Leiden Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

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

Next departure 19:56 today · Amsterdam Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 10 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 8 Oct Max en route +12 min · last fix heading to — +12 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 94% · 17
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=2
  • 50% T n=2
  • 100% F n=3
  • 100% S n=3
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
19:56on time +1 min
20:01≈ on time ≈ +1 min
20:06≈ on time ≈ +1 min
20:11≈ on time ≈ +1 min
20:14 / 20:17≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:27≈ on time ≈ +1 min
20:34≈ on time ≈ +2 min
20:40on time +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— 20:42+1 min+1 min
Tue 3 Nov— 20:480 min—
Mon 2 Nov— 20:39No data—
Sun 1 NovVoorhout 20:490 min—
Sat 31 OctVoorhout 20:490 min—
Fri 30 Oct— 20:41No data—
Thu 29 Oct— 20:410 min—
Wed 28 Oct— 20:41No data—
Tue 27 Oct— 21:000 min—
Mon 26 Oct— 20:53No data—
Sun 25 OctVoorhout 20:50No data—
Sat 24 OctVoorhout 20:560 min—
Fri 23 Oct— 20:410 min—
Thu 22 Oct— 20:41No data—
Wed 21 Oct— 20:56No data—
Tue 20 Oct— 20:410 min—
Sun 18 OctVoorhout 20:490 min—
Sat 17 OctVoorhout 20:490 min—
Fri 16 Oct— 20:42+2 min+2 min
Thu 15 Oct— 20:47No data—
Wed 14 Oct— 20:41No data—
Tue 13 Oct— 20:42No data—
Mon 12 Oct— 20:410 min—
Fri 9 Oct— 20:42+2 min+2 min
Thu 8 Oct— 20:58+12 min+12 min
Wed 7 Oct— 20:41+2 min+2 min
Tue 6 Oct— 20:410 min—
Mon 5 Oct— 20:410 min—
Sun 4 OctVoorhout 20:50No data—
Sat 3 OctVoorhout 20:51No data—