Train NS 5726 Utrecht Centraal – Hoofddorp
✓ Today’s run finished
Today, last fix heading to Schiphol Airport at 10:32 0 min
- Utrecht Centraal09:11
- Hollandsche Rading09:23
- Hilversum Media Park09:33
- Naarden-Bussum09:40
- Diemen Zuid10:00
- Schiphol Airport10:16
- Hoofddorp10:22
Next service: Monday 09:11 from Utrecht Centraal · Mon 9 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
- Sat 10 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 17
- 3–10 min 6% · 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=4
- 100% T n=3
- 100% F n=2
- 75% S n=4
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 09:11 | on time | on time | |
| 09:15 | ≈ on time | ≈ on time | |
| 09:23 | ≈ on time | ≈ on time | |
| 09:27 | ≈ on time | ≈ on time | |
| 09:30 / 09:31 | ≈ on time | ≈ on time | |
| 09:33 | ≈ on time | ≈ on time | |
| 09:37 | ≈ on time | ≈ on time | |
| 09:40 | ≈ on time | ≈ on time | |
| 09:46 / 09:53 | ≈ on time | ≈ on time | |
| 10:00 | ≈ on time | ≈ on time | |
| 10:02 | ≈ on time | ≈ on time | |
| 10:06 | ≈ on time | ≈ on time | |
| 10:09 / 10:10 | ≈ on time | ≈ on time | |
| 10:16 / 10:18 | ≈ on time | ≈ on time | |
| 10:22 | 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 |
|---|---|---|---|
| Sat 7 Nov | Schiphol Airport 10:32Partial coverage | 0 min | — |
| Fri 6 Nov | Sassenheim 10:48 | No data | — |
| Thu 5 Nov | Sassenheim 10:49 | No data | — |
| Wed 4 Nov | Sassenheim 10:48 | 0 min | — |
| Tue 3 Nov | Sassenheim 10:49 | No data | — |
| Mon 2 Nov | Sassenheim 11:03 | 0 min | — |
| Sat 31 Oct | Schiphol Airport 10:32Partial coverage | 0 min | — |
| Fri 30 Oct | Sassenheim 10:48 | 0 min | — |
| Thu 29 Oct | Sassenheim 10:49 | 0 min | — |
| Wed 28 Oct | Sassenheim 10:49 | 0 min | — |
| Tue 27 Oct | Sassenheim 10:50 | No data | — |
| Mon 26 Oct | Sassenheim 10:49 | 0 min | — |
| Sat 24 Oct | Schiphol Airport 10:32 | 0 min | — |
| Fri 23 Oct | Sassenheim 10:48 | No data | — |
| Thu 22 Oct | Sassenheim 10:49 | 0 min | — |
| Wed 21 Oct | Sassenheim 10:48 | No data | — |
| Tue 20 Oct | Sassenheim 10:49 | 0 min | — |
| Mon 19 Oct | Sassenheim 10:53 | No data | — |
| Fri 16 Oct | Sassenheim 10:48 | No data | — |
| Thu 15 Oct | Hilversum 10:58 | No data | — |
| Wed 14 Oct | Sassenheim 10:49 | 0 min | — |
| Tue 13 Oct | Sassenheim 10:49 | No data | — |
| Mon 12 Oct | Sassenheim 10:49 | 0 min | — |
| Sat 10 Oct | Schiphol Airport 10:38Partial coverage | +5 min | +5 min |
| Fri 9 Oct | Sassenheim 10:48 | 0 min | — |
| Thu 8 Oct | Sassenheim 10:49 | 0 min | +1 min |
| Wed 7 Oct | Hoofddorp 12:01 | 0 min | — |
| Tue 6 Oct | Sassenheim 10:49 | 0 min | — |
| Mon 5 Oct | Sassenheim 10:49 | No data | — |
| Sat 3 Oct | Almere Buiten 10:17 | No data | — |