Train NS 5718 Utrecht Centraal – Leiden Centraal
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 07:11 from Utrecht Centraal · Mon 9 Nov
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
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 21
- 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=5
- 100% T n=5
- 100% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (18 stops).
Last 90 days, 21 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 07:11 | on time | on time | |
| 07:15 | ≈ on time | ≈ on time | |
| 07:23 | ≈ on time | ≈ on time | |
| 07:27 | ≈ on time | ≈ on time | |
| 07:30 / 07:31 | ≈ on time | ≈ on time | |
| 07:33 | ≈ on time | ≈ on time | |
| 07:37 | ≈ on time | ≈ on time | |
| 07:40 | ≈ on time | ≈ on time | |
| 07:46 / 07:53 | ≈ on time | ≈ on time | |
| 08:00 | ≈ on time | ≈ on time | |
| 08:02 | ≈ on time | ≈ on time | |
| 08:06 | ≈ on time | ≈ on time | |
| 08:09 / 08:10 | ≈ on time | ≈ on time | |
| 08:16 / 08:19 | ≈ on time | ≈ on time | |
| 08:23 | ≈ on time | ≈ on time | |
| 08:28 | ≈ on time | ≈ on time | |
| 08:35 | ≈ on time | ≈ on time | |
| 08:40 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Sassenheim 08:48 | No data | — |
| Thu 5 Nov | Sassenheim 08:49Partial coverage | 0 min | — |
| Wed 4 Nov | Sassenheim 08:49Partial coverage | 0 min | — |
| Tue 3 Nov | Sassenheim 08:49Partial coverage | 0 min | — |
| Mon 2 Nov | Sassenheim 08:49 | No data | — |
| Fri 30 Oct | Sassenheim 08:56 | 0 min | — |
| Thu 29 Oct | Sassenheim 08:49 | 0 min | — |
| Wed 28 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Tue 27 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Mon 26 Oct | Sassenheim 08:50Partial coverage | 0 min | +2 min |
| Fri 23 Oct | Sassenheim 08:50 | 0 min | — |
| Thu 22 Oct | Sassenheim 09:17Partial coverage | 0 min | — |
| Wed 21 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Tue 20 Oct | Sassenheim 08:49 | No data | — |
| Mon 19 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Fri 16 Oct | Sassenheim 08:48 | 0 min | — |
| Thu 15 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Wed 14 Oct | Sassenheim 08:49 | 0 min | — |
| Tue 13 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Mon 12 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Fri 9 Oct | Sassenheim 08:48 | 0 min | — |
| Thu 8 Oct | Sassenheim 08:50Partial coverage | 0 min | — |
| Wed 7 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Tue 6 Oct | Sassenheim 08:49Partial coverage | 0 min | — |
| Mon 5 Oct | Sassenheim 08:49 | No data | — |
| Fri 2 Oct | Sassenheim 08:49 | No data | — |
| Thu 1 Oct | Sassenheim 08:51 | No data | — |
| Wed 30 Sept | Sassenheim 08:49 | No data | — |
| Tue 29 Sept | Sassenheim 08:50 | No data | — |
| Mon 28 Sept | Sassenheim 08:53 | No data | — |