Train NS 5760 Utrecht Centraal – Leiden Centraal
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 17:41 from Utrecht Centraal · Fri 6 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
23 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 23
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=3
- 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 (18 stops).
Last 90 days, 23 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 |
|---|---|---|---|
| 17:41 | on time | on time | |
| 17:45 | ≈ on time | ≈ on time | |
| 17:53 | ≈ on time | ≈ on time | |
| 17:57 | ≈ on time | ≈ on time | |
| 18:00 / 18:01 | ≈ on time | ≈ on time | |
| 18:03 | ≈ on time | ≈ on time | |
| 18:07 | ≈ on time | ≈ on time | |
| 18:10 | ≈ on time | ≈ on time | |
| 18:16 / 18:23 | ≈ on time | ≈ on time | |
| 18:30 | ≈ on time | ≈ on time | |
| 18:32 | ≈ on time | ≈ on time | |
| 18:36 | ≈ on time | ≈ on time | |
| 18:39 / 18:40 | ≈ on time | ≈ on time | |
| 18:46 / 18:48 | ≈ on time | ≈ on time | |
| 18:53 | ≈ on time | ≈ on time | |
| 18:57 | ≈ on time | ≈ on time | |
| 19:04 | ≈ on time | ≈ on time | |
| 19:09 | 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 |
|---|---|---|---|
| Thu 5 Nov | Utrecht Centraal 19:09 | No data | — |
| Wed 4 Nov | Utrecht Centraal 19:09 | No data | — |
| Tue 3 Nov | Utrecht Centraal 19:09 | No data | — |
| Mon 2 Nov | Utrecht Centraal 19:09Partial coverage | 0 min | — |
| Sun 1 Nov | Schiphol Airport 19:02 | 0 min | — |
| Sat 31 Oct | Schiphol Airport 19:02 | 0 min | +2 min |
| Fri 30 Oct | Hoofddorp 19:10 | No data | — |
| Thu 29 Oct | Utrecht Centraal 19:10Partial coverage | 0 min | — |
| Wed 28 Oct | Naarden-Bussum 19:54 | 0 min | — |
| Tue 27 Oct | Utrecht Centraal 01:25Partial coverage | 0 min | — |
| Mon 26 Oct | Utrecht Centraal 19:10Partial coverage | 0 min | — |
| Sun 25 Oct | Schiphol Airport 19:03 | No data | — |
| Sat 24 Oct | Schiphol Airport 19:02 | 0 min | — |
| Fri 23 Oct | Sassenheim 19:15 | +3 min | +3 min |
| Thu 22 Oct | Amsterdam Zuid 18:54Partial coverage | 0 min | — |
| Wed 21 Oct | Amsterdam Zuid 19:11 | No data | — |
| Tue 20 Oct | Amsterdam Zuid 19:10Partial coverage | 0 min | — |
| Mon 19 Oct | Amsterdam Zuid 19:11Partial coverage | 0 min | — |
| Fri 16 Oct | Sassenheim 19:18 | No data | — |
| Thu 15 Oct | Diemen Zuid 19:13 | 0 min | — |
| Wed 14 Oct | Sassenheim 19:18Partial coverage | 0 min | — |
| Tue 13 Oct | Amsterdam Zuid 19:10 | 0 min | — |
| Mon 12 Oct | Amsterdam Zuid 19:10Partial coverage | 0 min | — |
| Sun 11 Oct | Schiphol Airport 19:02 | 0 min | +3 min |
| Sat 10 Oct | Schiphol Airport 19:02 | 0 min | — |
| Fri 9 Oct | Amsterdam RAI 18:57 | 0 min | — |
| Thu 8 Oct | Utrecht Centraal 19:11Partial coverage | 0 min | +1 min |
| Wed 7 Oct | Utrecht Centraal 19:10Partial coverage | 0 min | — |
| Tue 6 Oct | Utrecht Centraal 19:10Partial coverage | 0 min | — |
| Mon 5 Oct | Utrecht Centraal 19:10Partial coverage | 0 min | — |