Train NS 5767 Hoofddorp – Utrecht Centraal
✓ Today’s run finished
Today, last fix heading to Utrecht Overvecht at 19:28 0 min
- Hoofddorp18:07
- Amsterdam Zuid18:19
- Diemen Zuid18:29
- Naarden-Bussum18:49
- Hilversum Media Park18:56
- Utrecht Overvecht19:14
- Utrecht Centraal19:18
Next service: tomorrow 18:07 from Hoofddorp · Mon 9 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
- Thu 29 Oct Max en route +3 min · last fix heading to Nieuw Vennep +3 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 18
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=2
- 100% W n=3
- 50% T n=2
- 100% F n=3
- 100% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 18:07 | on time | on time | |
| 18:11 / 18:13 | ≈ on time | ≈ on time | |
| 18:19 / 18:20 | ≈ on time | ≈ on time | |
| 18:22 | ≈ on time | ≈ on time | |
| 18:25 / 18:26 | ≈ on time | ≈ on time | |
| 18:29 | ≈ on time | ≈ on time | |
| 18:35 / 18:43 | ≈ on time | ≈ on time | |
| 18:49 | ≈ on time | ≈ +1 min | |
| 18:52 | ≈ on time | ≈ +1 min | |
| 18:56 | ≈ on time | ≈ +1 min | |
| 18:58 / 18:59 | ≈ on time | ≈ +1 min | |
| 19:02 | ≈ on time | ≈ +1 min | |
| 19:06 | ≈ on time | ≈ +1 min | |
| 19:14 | ≈ on time | ≈ +1 min | |
| 19: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 |
|---|---|---|---|
| Sun 8 Nov | Utrecht Overvecht 19:28Partial coverage | 0 min | — |
| Sat 7 Nov | Utrecht Overvecht 19:28Partial coverage | 0 min | — |
| Fri 6 Nov | Weesp 19:19 | 0 min | — |
| Thu 5 Nov | Schiphol Airport 19:19 | No data | — |
| Wed 4 Nov | Schiphol Airport 19:19 | No data | — |
| Tue 3 Nov | Hoofddorp 19:19 | 0 min | — |
| Mon 2 Nov | Hoofddorp 19:19 | 0 min | — |
| Sun 1 Nov | Utrecht Overvecht 19:28Partial coverage | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 19:28Partial coverage | 0 min | — |
| Fri 30 Oct | Bussum Zuid 19:21 | No data | — |
| Thu 29 Oct | Nieuw Vennep 19:21 | +3 min | +3 min |
| Wed 28 Oct | Schiphol Airport 19:20 | 0 min | — |
| Tue 27 Oct | Nieuw Vennep 19:20 | No data | — |
| Mon 26 Oct | Hoofddorp 19:21 | 0 min | — |
| Sun 25 Oct | Utrecht Overvecht 19:28 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 19:35 | No data | — |
| Fri 23 Oct | Utrecht Overvecht 19:28 | 0 min | — |
| Thu 22 Oct | Weesp 19:20 | No data | — |
| Wed 21 Oct | Duivendrecht 19:20 | No data | — |
| Tue 20 Oct | Weesp 19:22 | No data | — |
| Mon 19 Oct | Weesp 19:22 | No data | — |
| Fri 16 Oct | Utrecht Overvecht 19:31 | No data | — |
| Thu 15 Oct | Duivendrecht 19:24 | No data | — |
| Wed 14 Oct | Utrecht Overvecht 19:28 | 0 min | — |
| Tue 13 Oct | Duivendrecht 19:20 | No data | — |
| Mon 12 Oct | Weesp 19:19 | No data | — |
| Sun 11 Oct | Utrecht Overvecht 19:28 | 0 min | — |
| Sat 10 Oct | Utrecht Overvecht 19:29Partial coverage | 0 min | — |
| Fri 9 Oct | Diemen Zuid 20:08 | 0 min | +34 min |
| Thu 8 Oct | Nieuw Vennep 19:00 | 0 min | — |