Train NS 5742 Utrecht Centraal – Hoofddorp
Running now · updated 13:57
Heading to Hoofddorp No data
Estimated arrival at Hoofddorp 14:22 · 20 km/h
- Utrecht Centraal13:11
- Hollandsche Rading13:23
- Hilversum Media Park13:33
- Naarden-Bussum13:40
- Diemen Zuid14:00
- Amsterdam Zuid14:09
- Hoofddorp14:22
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 14 Nov Max en route +14 min · last fix heading to Utrecht Centraal +14 min
- Fri 13 Nov Max en route +10 min · last fix heading to Sassenheim +10 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 24
- 3–10 min 0% · 0
- 10–30 min 8% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=3
- 100% T n=4
- 67% F n=3
- 80% S n=5
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 26 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 | Today |
|---|---|---|---|---|
| 13:11 | on time | on time | ||
| 13:15 | ≈ on time | ≈ on time | ||
| 13:23 | ≈ on time | ≈ on time | ||
| 13:27 | ≈ on time | ≈ on time | ||
| 13:30 / 13:31 | ≈ on time | ≈ on time | ||
| 13:33 | ≈ on time | ≈ on time | ||
| 13:37 | ≈ on time | ≈ on time | ||
| 13:40 | ≈ on time | ≈ on time | ||
| 13:46 / 13:53 | ≈ on time | ≈ +1 min | ||
| 14:00 | ≈ on time | ≈ +1 min | ||
| 14:02 | ≈ on time | ≈ +1 min | ||
| 14:06 | ≈ on time | ≈ +1 min | ||
| 14:09 / 14:10 | ≈ on time | ≈ +1 min | ||
| 14:16 / 14:18 | ≈ on time | ≈ +1 min | ||
| 14:22 | 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 14 Nov | Utrecht Centraal 13:54Partial coverage | +14 min | +14 min |
| Fri 13 Nov | Sassenheim 14:54 | +10 min | +10 min |
| Thu 12 Nov | Sassenheim 14:49 | 0 min | — |
| Wed 11 Nov | Sassenheim 14:49 | 0 min | — |
| Tue 10 Nov | Sassenheim 14:54 | 0 min | — |
| Mon 9 Nov | Sassenheim 14:49 | +1 min | +1 min |
| Sun 8 Nov | Schiphol Airport 14:33Partial coverage | +2 min | +2 min |
| Sat 7 Nov | Schiphol Airport 14:32Partial coverage | 0 min | — |
| Fri 6 Nov | Sassenheim 14:48 | No data | — |
| Thu 5 Nov | Sassenheim 14:49 | No data | — |
| Wed 4 Nov | Sassenheim 14:49 | 0 min | — |
| Tue 3 Nov | Sassenheim 14:48 | No data | — |
| Mon 2 Nov | Sassenheim 14:48 | 0 min | — |
| Sat 31 Oct | Schiphol Airport 14:33Partial coverage | +1 min | — |
| Fri 30 Oct | Sassenheim 14:48 | No data | — |
| Thu 29 Oct | Sassenheim 14:50 | 0 min | — |
| Wed 28 Oct | Sassenheim 14:50 | No data | — |
| Tue 27 Oct | Sassenheim 14:49 | 0 min | — |
| Mon 26 Oct | Sassenheim 14:49 | No data | — |
| Sun 25 Oct | Schiphol Airport 14:32 | No data | — |
| Sat 24 Oct | Schiphol Airport 14:34 | +2 min | +3 min |
| Fri 23 Oct | Sassenheim 14:48 | 0 min | — |
| Thu 22 Oct | Sassenheim 14:49 | 0 min | — |
| Wed 21 Oct | Sassenheim 14:49 | No data | — |
| Tue 20 Oct | Sassenheim 14:49 | 0 min | — |
| Mon 19 Oct | Sassenheim 14:49 | 0 min | — |
| Fri 16 Oct | Sassenheim 14:49 | No data | — |
| Thu 15 Oct | Sassenheim 14:49 | No data | — |
| Wed 14 Oct | Sassenheim 14:54 | No data | — |
| Tue 13 Oct | Sassenheim 14:49 | No data | — |