Train NS 5771 Hoofddorp – Utrecht Centraal
It has not run yet today
Last recorded run: Saturday 7 November 0 min
Next service: today 19:07 from Hoofddorp · Sun 8 Nov
Last 30 days
Arrival delay at Utrecht 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
- Wed 4 Nov Max en route +5 min · last fix heading to — +5 min
- Sat 10 Oct Max en route +5 min · last fix heading to Utrecht Overvecht +5 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 18
- 3–10 min 10% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=2
- 50% W n=2
- 100% T n=2
- 100% F n=4
- 75% S n=4
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 20 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 |
|---|---|---|---|
| 19:07 | on time | on time | |
| 19:11 / 19:13 | ≈ on time | ≈ on time | |
| 19:19 / 19:20 | ≈ on time | ≈ on time | |
| 19:22 | ≈ on time | ≈ on time | |
| 19:25 / 19:26 | ≈ on time | ≈ on time | |
| 19:29 | ≈ on time | ≈ on time | |
| 19:35 / 19:43 | ≈ on time | ≈ on time | |
| 19:49 | ≈ on time | ≈ +1 min | |
| 19:52 | ≈ on time | ≈ +1 min | |
| 19:56 | ≈ on time | ≈ +1 min | |
| 19:58 / 19:59 | ≈ on time | ≈ +1 min | |
| 20:02 | ≈ on time | ≈ +1 min | |
| 20:06 | ≈ on time | ≈ +1 min | |
| 20:14 | ≈ on time | ≈ +1 min | |
| 20:18 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Utrecht Overvecht 20:28Partial coverage | 0 min | — |
| Fri 6 Nov | — 20:19 | 0 min | — |
| Thu 5 Nov | — 20:20 | No data | — |
| Wed 4 Nov | — 20:24 | +5 min | +5 min |
| Tue 3 Nov | — 20:19 | No data | — |
| Mon 2 Nov | — 20:19 | 0 min | — |
| Sun 1 Nov | Utrecht Overvecht 20:28 | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 20:28Partial coverage | 0 min | — |
| Fri 30 Oct | Leiden Centraal 20:20 | No data | — |
| Thu 29 Oct | — 20:19 | 0 min | — |
| Wed 28 Oct | — 20:27 | No data | — |
| Tue 27 Oct | — 20:20 | No data | — |
| Mon 26 Oct | Naarden-Bussum 20:19 | No data | — |
| Sun 25 Oct | Utrecht Overvecht 20:28 | No data | — |
| Sat 24 Oct | Hollandsche Rading 20:47 | 0 min | — |
| Fri 23 Oct | Duivendrecht 20:19 | 0 min | — |
| Thu 22 Oct | — 20:22 | No data | — |
| Wed 21 Oct | — 20:33 | No data | — |
| Tue 20 Oct | — 20:22 | No data | — |
| Mon 19 Oct | — 21:34 | 0 min | — |
| Fri 16 Oct | Bussum Zuid 20:21 | 0 min | — |
| Thu 15 Oct | — 20:24 | No data | — |
| Wed 14 Oct | Weesp 20:19 | No data | — |
| Tue 13 Oct | — 20:20 | 0 min | — |
| Mon 12 Oct | — 20:20 | 0 min | — |
| Sun 11 Oct | Utrecht Overvecht 20:28 | 0 min | — |
| Sat 10 Oct | Utrecht Overvecht 20:32Partial coverage | +5 min | +5 min |
| Fri 9 Oct | — 20:20 | +1 min | +2 min |
| Thu 8 Oct | — 20:19 | 0 min | +1 min |
| Wed 7 Oct | — 20:18 | 0 min | — |