Train NS 4277 Amsterdam Centraal – Leiden Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 21: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 · 22 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

Worst days

  • Fri 9 Oct Max en route +9 min · last fix heading to — +9 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 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 67% 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
21:56on time on time
22:01≈ on time ≈ on time
22:06≈ on time ≈ on time
22:11≈ on time ≈ on time
22:14 / 22:17≈ on time ≈ on time
22:22≈ on time ≈ on time
22:27≈ on time ≈ on time
22:34≈ on time ≈ on time
22:40on time on time

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— 22:390 min—
Tue 3 Nov— 22:42No data—
Mon 2 Nov— 22:390 min—
Sun 1 NovVoorhout 22:490 min—
Sat 31 OctVoorhout 22:480 min—
Fri 30 Oct— 22:44No data—
Wed 28 Oct— 22:41No data—
Tue 27 Oct— 22:48No data—
Mon 26 Oct— 22:470 min—
Sun 25 OctVoorhout 22:49No data—
Sat 24 OctVoorhout 22:480 min—
Fri 23 Oct— 22:420 min—
Thu 22 Oct— 22:42No data—
Wed 21 Oct— 22:40No data—
Tue 20 Oct— 22:410 min—
Mon 19 Oct— 22:420 min—
Sun 18 OctVoorhout 22:490 min—
Sat 17 OctVoorhout 22:490 min—
Fri 16 Oct— 22:410 min—
Thu 15 Oct— 22:47No data—
Wed 14 Oct— 22:43No data—
Tue 13 Oct— 22:42No data—
Mon 12 Oct— 22:410 min—
Fri 9 Oct— 22:48+9 min+9 min
Thu 8 Oct— 22:420 min—
Wed 7 Oct— 22:410 min—
Tue 6 Oct— 22:410 min—
Mon 5 Oct— 22:410 min—
Sun 4 OctVoorhout 22:51No data—
Sat 3 OctVoorhout 22:50No data—