Train NS 4916 Utrecht Centraal – Hilversum
It has not run yet today
Last recorded run: Sunday 8 November +2 min
Next service: today 06:24 from Utrecht Centraal · Mon 9 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 7 Nov Max en route +11 min · last fix heading to Almere Muziekwijk +9 min
- Sun 11 Oct Max en route +5 min · last fix heading to Hilversum Sportpark +5 min
- Sun 1 Nov Max en route +4 min · last fix heading to Hilversum Sportpark +4 min
- Thu 22 Oct Max en route +3 min · last fix heading to Almere Muziekwijk +3 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 28
- 3–10 min 13% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=5
- 100% W n=5
- 80% T n=5
- 100% F n=4
- 80% S n=5
- 50% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 32 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 |
|---|---|---|---|
| 06:24 | on time | on time | |
| 06:28 | ≈ on time | ≈ +1 min | |
| 06:35 | ≈ on time | ≈ +2 min | |
| 06:39 | ≈ on time | ≈ +3 min | |
| 06: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 8 Nov | Hilversum Sportpark 06:54Partial coverage | +2 min | +2 min |
| Sat 7 Nov | Almere Muziekwijk 07:29 | +9 min | +11 min |
| Fri 6 Nov | Almere Muziekwijk 07:19 | No data | — |
| Thu 5 Nov | Almere Muziekwijk 07:22 | 0 min | — |
| Wed 4 Nov | Almere Muziekwijk 07:19 | +1 min | — |
| Tue 3 Nov | Almere Muziekwijk 07:19 | 0 min | — |
| Mon 2 Nov | Almere Muziekwijk 07:19 | 0 min | — |
| Sun 1 Nov | Hilversum Sportpark 06:56 | +4 min | +4 min |
| Sat 31 Oct | Almere Muziekwijk 07:22 | +3 min | +5 min |
| Fri 30 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Thu 29 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Wed 28 Oct | Almere Muziekwijk 07:20 | 0 min | — |
| Tue 27 Oct | Almere Muziekwijk 07:20 | 0 min | — |
| Mon 26 Oct | Almere Muziekwijk 07:21 | +2 min | +2 min |
| Sun 25 Oct | Hilversum Sportpark 06:54 | No data | — |
| Sat 24 Oct | Almere Muziekwijk 07:20 | 0 min | — |
| Fri 23 Oct | Almere Muziekwijk 07:20 | 0 min | — |
| Thu 22 Oct | Almere Muziekwijk 07:23 | +3 min | +3 min |
| Wed 21 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Tue 20 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Mon 19 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Sun 18 Oct | Hilversum Sportpark 06:57 | +2 min | +3 min |
| Sat 17 Oct | Hilversum Sportpark 06:56 | +1 min | +1 min |
| Fri 16 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Thu 15 Oct | Almere Muziekwijk 07:19 | 0 min | — |
| Wed 14 Oct | Almere Muziekwijk 07:19 | 0 min | +2 min |
| Tue 13 Oct | Almere Muziekwijk 07:20 | 0 min | — |
| Mon 12 Oct | Almere Muziekwijk 07:20 | 0 min | — |
| Sun 11 Oct | Hilversum Sportpark 06:58 | +5 min | +5 min |
| Sat 10 Oct | Almere Muziekwijk 07:21 | +2 min | +4 min |