Train NS 5728 Utrecht Centraal – Hoofddorp
✓ Today’s run finished
Today, last fix heading to Schiphol Airport at 11:02 0 min
- Utrecht Centraal09:41
- Hollandsche Rading09:53
- Hilversum Media Park10:03
- Naarden-Bussum10:10
- Diemen Zuid10:30
- Schiphol Airport10:46
- Hoofddorp10:52
Next service: tomorrow 09:41 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
Distribution · 90 days
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 21
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=3
- 100% W n=3
- 100% T n=3
- 100% F n=2
- 100% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 21 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:41 | on time | on time | |
| 09:45 | ≈ on time | ≈ on time | |
| 09:53 | ≈ on time | ≈ on time | |
| 09:57 | ≈ on time | ≈ on time | |
| 10:00 / 10:01 | ≈ on time | ≈ on time | |
| 10:03 | ≈ on time | ≈ on time | |
| 10:07 | ≈ on time | ≈ on time | |
| 10:10 | ≈ on time | ≈ on time | |
| 10:16 / 10:23 | ≈ on time | ≈ on time | |
| 10:30 | ≈ on time | ≈ on time | |
| 10:32 | ≈ on time | ≈ on time | |
| 10:36 | ≈ on time | ≈ on time | |
| 10:39 / 10:40 | ≈ on time | ≈ on time | |
| 10:46 / 10:48 | ≈ on time | ≈ on time | |
| 10: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 |
|---|---|---|---|
| Sun 8 Nov | Schiphol Airport 11:02Partial coverage | 0 min | — |
| Sat 7 Nov | Schiphol Airport 11:02 | 0 min | — |
| Fri 6 Nov | Sassenheim 11:18 | No data | — |
| Thu 5 Nov | Sassenheim 11:19 | No data | — |
| Wed 4 Nov | Sassenheim 11:19 | +3 min | +3 min |
| Tue 3 Nov | Sassenheim 11:19 | No data | — |
| Mon 2 Nov | Sassenheim 11:19 | 0 min | — |
| Sun 1 Nov | Hilversum Sportpark 10:09 | +1 min | — |
| Sat 31 Oct | Schiphol Airport 11:02 | 0 min | — |
| Fri 30 Oct | Utrecht Centraal 12:52 | 0 min | — |
| Thu 29 Oct | Sassenheim 11:19 | 0 min | — |
| Wed 28 Oct | Sassenheim 11:19 | No data | — |
| Tue 27 Oct | Sassenheim 11:19 | 0 min | — |
| Mon 26 Oct | Sassenheim 11:32 | No data | — |
| Sun 25 Oct | Schiphol Airport 11:02 | No data | — |
| Sat 24 Oct | Schiphol Airport 11:02 | 0 min | — |
| Fri 23 Oct | Sassenheim 11:20 | No data | — |
| Thu 22 Oct | Sassenheim 11:20 | 0 min | — |
| Wed 21 Oct | Nieuw Vennep 11:12 | No data | — |
| Tue 20 Oct | Sassenheim 11:19 | 0 min | — |
| Mon 19 Oct | Sassenheim 11:20 | 0 min | — |
| Fri 16 Oct | Sassenheim 11:18 | No data | — |
| Thu 15 Oct | Sassenheim 11:19 | No data | — |
| Wed 14 Oct | Sassenheim 11:20 | 0 min | — |
| Tue 13 Oct | Sassenheim 11:19 | No data | — |
| Mon 12 Oct | Sassenheim 11:19 | 0 min | — |
| Sun 11 Oct | Schiphol Airport 11:02Partial coverage | 0 min | — |
| Sat 10 Oct | Schiphol Airport 11:03 | 0 min | — |
| Fri 9 Oct | Sassenheim 11:18 | 0 min | — |
| Thu 8 Oct | Sassenheim 11:19 | 0 min | — |