Train NS 4786 Alphen a/d Rijn – Leiden Centraal

Alphen a/d Rijn 00:54 → Leiden Centraal 01:07 Daily 0 h 13 min · 3 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:08 0 min

  1. Alphen a/d Rijn00:54
  2. Leiden Lammenschans01:02
  3. Leiden Centraal01:07

Next service: tomorrow 00:54 from Alphen a/d Rijn · Sun 8 Nov

Next departure 00:54 tomorrow · Alphen a/d Rijn
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 2 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
00:54on time on time
01:02≈ on time ≈ on time
01:07on 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
Sat 7 Nov— 01:080 min—
Fri 6 Nov— 01:13No data—
Thu 5 Nov— 01:09+1 min+1 min
Wed 4 Nov— 01:090 min—
Mon 2 NovLeiden Lammenschans 01:170 min—
Sun 1 Nov— 01:080 min—
Fri 30 Oct— 01:08+1 min—
Thu 29 Oct— 01:080 min—
Wed 28 Oct— 01:090 min—
Tue 27 Oct— 01:080 min—
Mon 26 OctLeiden Lammenschans 01:180 min—
Sun 25 Oct— 01:110 min—
Sat 24 Oct— 01:110 min—
Fri 23 Oct— 01:08No data—
Thu 22 Oct— 01:080 min—
Wed 21 Oct— 01:110 min—
Tue 20 Oct— 01:090 min—
Mon 19 OctLeiden Lammenschans 01:170 min—
Sun 18 OctLeiden Lammenschans 01:16Partial coverage0 min—
Sat 17 Oct— 01:100 min+1 min
Fri 16 Oct— 01:080 min—
Thu 15 Oct— 01:080 min—
Wed 14 Oct— 01:090 min—
Tue 13 Oct— 01:08+1 min—