Train NS 5768 Utrecht Centraal – Hoofddorp
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 19:41 from Utrecht Centraal · Fri 6 Nov
Last 30 days
Arrival delay at Hoofddorp, 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 16 Oct Max en route +8 min · last fix heading to Utrecht Overvecht +8 min
- Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 15
- 3–10 min 12% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 67% W n=3
- 100% T n=2
- 75% F n=4
- 100% S n=2
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 17 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:41 | on time | on time | |
| 19:45 | ≈ on time | ≈ on time | |
| 19:53 | ≈ on time | ≈ on time | |
| 19:57 | ≈ on time | ≈ on time | |
| 20:00 / 20:01 | ≈ on time | ≈ on time | |
| 20:03 | ≈ on time | ≈ on time | |
| 20:07 | ≈ on time | ≈ on time | |
| 20:10 | ≈ on time | ≈ on time | |
| 20:16 / 20:23 | ≈ on time | ≈ on time | |
| 20:30 | ≈ on time | ≈ on time | |
| 20:32 | ≈ on time | ≈ on time | |
| 20:36 | ≈ on time | ≈ on time | |
| 20:39 / 20:40 | ≈ on time | ≈ on time | |
| 20:46 / 20:48 | ≈ on time | ≈ on time | |
| 20:52 | 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 | — 20:58 | No data | — |
| Wed 4 Nov | — 20:59 | +4 min | +4 min |
| Mon 2 Nov | — 20:53 | No data | — |
| Sun 1 Nov | Schiphol Airport 21:02Partial coverage | 0 min | — |
| Sat 31 Oct | Schiphol Airport 21:02Partial coverage | 0 min | — |
| Fri 30 Oct | — 20:56 | 0 min | — |
| Thu 29 Oct | — 20:53 | 0 min | — |
| Wed 28 Oct | — 21:04 | 0 min | — |
| Tue 27 Oct | — 20:54 | 0 min | — |
| Mon 26 Oct | Utrecht Overvecht 20:53 | No data | — |
| Sun 25 Oct | Schiphol Airport 21:02 | No data | — |
| Sat 24 Oct | Schiphol Airport 21:02 | No data | — |
| Fri 23 Oct | — 20:53 | 0 min | — |
| Thu 22 Oct | — 03:25 | No data | — |
| Wed 21 Oct | — 20:56 | No data | — |
| Tue 20 Oct | — 20:54 | No data | — |
| Mon 19 Oct | — 20:58 | 0 min | — |
| Fri 16 Oct | Utrecht Overvecht 21:08Partial coverage | +8 min | +8 min |
| Thu 15 Oct | — 20:56 | No data | — |
| Wed 14 Oct | Utrecht Overvecht 20:53 | No data | — |
| Tue 13 Oct | — 20:54 | No data | — |
| Mon 12 Oct | — 20:53 | No data | — |
| Sun 11 Oct | Schiphol Airport 21:02 | 0 min | — |
| Sat 10 Oct | Schiphol Airport 21:03Partial coverage | 0 min | — |
| Fri 9 Oct | — 20:53 | 0 min | — |
| Thu 8 Oct | — 03:25 | 0 min | — |
| Wed 7 Oct | — 20:53 | 0 min | — |
| Tue 6 Oct | — 20:53 | 0 min | — |
| Mon 5 Oct | — 20:54 | 0 min | +2 min |
| Sun 4 Oct | Almere Buiten 20:47 | No data | — |