Train NS 5722 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 08:11 → Leiden Centraal 09:39 Mon, Tue, Wed, Thu, Fri 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 08:11 from Utrecht Centraal · Thu 5 Nov

Next departure 08:11 today · Utrecht Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 3 full · 11 partial · 7 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 3 full · 12 partial · 55 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
08:11on time on time
08:15— —
08:23— —
08:27— —
08:30 / 08:31— —
08:33— —
08:37— —
08:40— —
08:46 / 08:53— —
09:00— —
09:02— —
09:06— —
09:09 / 09:10— —
09:16 / 09:18— —
09:22— —
09:27— —
09:34— —
09:39— —

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 NovSassenheim 09:48Partial coverage0 min—
Tue 3 NovSassenheim 09:53Partial coverage0 min—
Mon 2 NovSassenheim 09:49Partial coverage0 min—
Fri 30 OctSassenheim 09:49No data—
Thu 29 OctBussum Zuid 11:220 min—
Wed 28 OctSassenheim 09:50Partial coverage0 min—
Tue 27 OctSassenheim 10:18Partial coverage0 min—
Mon 26 OctSassenheim 09:49No data—
Fri 23 OctSassenheim 09:480 min—
Thu 22 OctSassenheim 09:49Partial coverage0 min—
Wed 21 OctSassenheim 09:49Partial coverage0 min—
Tue 20 OctSassenheim 09:48No data—
Mon 19 OctSassenheim 09:49Partial coverage0 min—
Fri 16 OctSassenheim 09:48No data—
Thu 15 OctNieuw Vennep 10:58No data—
Wed 14 OctSassenheim 10:17No data—
Tue 13 OctSassenheim 09:49Partial coverage0 min—
Mon 12 OctSassenheim 10:07No data—
Fri 9 OctSassenheim 09:490 min—
Thu 8 OctSassenheim 10:17Partial coverage0 min—
Wed 7 OctSassenheim 09:50Partial coverage+2 min+2 min
Tue 6 OctSassenheim 09:49Partial coverage0 min—
Mon 5 OctSassenheim 09:49No data—
Fri 2 OctSassenheim 09:48No data—
Thu 1 OctSassenheim 09:49No data—
Wed 30 SeptSassenheim 09:50No data—
Tue 29 SeptSassenheim 09:49No data—
Mon 28 SeptSassenheim 09:52No data—
Sun 27 SeptAmsterdam Muiderpoort 09:12No data—
Sat 26 SeptHilversum Sportpark 08:44No data—