Train NS 5750 Utrecht Centraal → Hilversum
NS 5750 Utrecht Centraal–Hilversum: final delay under 3 min on 18 of its 22 runs with data in the last 30 days (82%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:06 (GMT+1).
An alert on this phone or computer when the 5750 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Hilversum Sportpark at 15:54 0 min
- Utrecht Centraal15:25
- Utrecht Overvecht15:29
- Hilversum Sportpark15:39
- Hilversum15:41
Next service: tomorrow 15:25 from Utrecht Centraal · Mon 23 Nov
Last 30 days
Arrival delay at Hilversum, 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 +18 min · last fix heading to Schiphol Airport +17 min
- Fri 20 Nov Max en route +14 min · last fix heading to Sassenheim +14 min
- Mon 16 Nov Max en route +4 min · last fix heading to Sassenheim +4 min
- Sun 15 Nov Max en route +3 min · last fix heading to Schiphol Airport +3 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 32
- 3–10 min 6% · 2
- 10–30 min 6% · 2
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 100% T n=4
- 100% W n=5
- 100% T n=5
- 80% F n=5
- 83% S n=6
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 36 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 |
|---|---|---|---|
| 15:25 | on time | on time | |
| 15:29 | ≈ on time | ≈ +1 min | |
| 15:39 | ≈ on time | ≈ +2 min | |
| 15:41 | on time | +3 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 22 Nov | Hilversum Sportpark 15:54Partial coverage | 0 min | — |
| Sat 21 Nov | Hilversum Sportpark 15:53Partial coverage | 0 min | — |
| Fri 20 Nov | Sassenheim 16:59 | +14 min | +14 min |
| Thu 19 Nov | Sassenheim 16:50 | +1 min | +1 min |
| Wed 18 Nov | Sassenheim 16:49 | 0 min | +1 min |
| Tue 17 Nov | Sassenheim 16:49 | 0 min | — |
| Mon 16 Nov | Sassenheim 16:54 | +4 min | +4 min |
| Sun 15 Nov | Schiphol Airport 16:33 | +3 min | +3 min |
| Sat 14 Nov | Schiphol Airport 16:49 | +17 min | +18 min |
| Fri 13 Nov | Sassenheim 16:48 | 0 min | — |
| Thu 12 Nov | Sassenheim 16:49 | 0 min | — |
| Wed 11 Nov | Sassenheim 16:49 | 0 min | — |
| Tue 10 Nov | Sassenheim 16:49 | 0 min | — |
| Mon 9 Nov | Sassenheim 16:49 | 0 min | — |
| Sun 8 Nov | Schiphol Airport 16:33 | 0 min | — |
| Sat 7 Nov | Schiphol Airport 16:32 | 0 min | — |
| Fri 6 Nov | Sassenheim 16:49 | No data | — |
| Thu 5 Nov | Sassenheim 16:49 | No data | — |
| Wed 4 Nov | Sassenheim 16:49 | 0 min | — |
| Tue 3 Nov | Sassenheim 16:49 | No data | — |
| Mon 2 Nov | Sassenheim 16:49 | 0 min | — |
| Sun 1 Nov | Schiphol Airport 16:33 | 0 min | — |
| Sat 31 Oct | Schiphol Airport 16:32 | 0 min | — |
| Fri 30 Oct | Sassenheim 16:48 | No data | — |
| Thu 29 Oct | Sassenheim 16:49 | 0 min | — |
| Wed 28 Oct | Sassenheim 16:48 | No data | — |
| Tue 27 Oct | Sassenheim 16:49 | No data | — |
| Mon 26 Oct | Sassenheim 16:49 | No data | — |
| Sun 25 Oct | Schiphol Airport 16:32 | No data | — |
| Sat 24 Oct | Schiphol Airport 16:32 | 0 min | — |