Train NS 4793 Leiden Centraal – Alphen a/d Rijn

Leiden Centraal 00:22 → Alphen a/d Rijn 00:36 Daily 0 h 14 min · 3 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:37 0 min

  1. Leiden Centraal00:22
  2. Leiden Lammenschans00:27
  3. Alphen a/d Rijn00:36

Next service: tomorrow 00:22 from Leiden Centraal · Sun 8 Nov

Next departure 00:22 tomorrow · Leiden Centraal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 18 full · 4 partial · 4 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 18 full · 4 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Alphen a/d Rijn, 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=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=2
  • 100% S n=3
  • 100% S n=2

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:22on time on time
00:27≈ on time ≈ on time
00:36on 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— 00:370 min—
Fri 6 Nov— 00:38No data—
Thu 5 Nov— 00:380 min—
Wed 4 Nov— 00:380 min—
Tue 3 Nov— 00:37+1 min+1 min
Mon 2 NovLeiden Lammenschans 00:39Partial coverage0 min—
Sun 1 Nov— 00:420 min—
Sat 31 Oct— 00:37No data—
Fri 30 Oct— 00:370 min—
Thu 29 Oct— 00:370 min—
Wed 28 Oct— 00:370 min—
Tue 27 Oct— 00:370 min—
Mon 26 OctLeiden Lammenschans 00:42Partial coverage0 min—
Sun 25 Oct— 00:38No data—
Sat 24 Oct— 00:380 min—
Fri 23 Oct— 00:42No data—
Thu 22 Oct— 00:370 min—
Wed 21 Oct— 00:420 min—
Tue 20 Oct— 00:380 min—
Mon 19 OctLeiden Lammenschans 00:41Partial coverage0 min—
Sun 18 OctLeiden Lammenschans 00:41Partial coverage0 min—
Sat 17 Oct— 00:39+1 min+1 min
Fri 16 Oct— 00:370 min—
Thu 15 Oct— 00:370 min—
Wed 14 Oct— 00:380 min—
Tue 13 Oct— 00:40+1 min+1 min