Train NS 5747 Hilversum → Utrecht Centraal
NS 5747 Hilversum–Utrecht Centraal: final delay under 3 min on 20 of its 22 runs with data in the last 30 days (91%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 09:38 (GMT+1).
An alert on this phone or computer when the 5747 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November 0 min
Next service: today 14:18 from Hilversum · Sun 22 Nov
Last 30 days
Arrival delay at Utrecht Centraal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 19 Nov Max en route +6 min · last fix heading to Utrecht Overvecht +6 min
- Fri 13 Nov Max en route +6 min · last fix heading to Utrecht Overvecht +6 min
- Fri 9 Oct Max en route +4 min · last fix heading to Utrecht Overvecht +4 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 31
- 3–10 min 9% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 100% W n=6
- 80% T n=5
- 33% F n=3
- 100% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 34 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 |
|---|---|---|---|
| 14:18 | on time | on time | |
| 14:21 | ≈ on time | ≈ on time | |
| 14:31 | ≈ on time | ≈ +2 min | |
| 14:35 | on time | +2 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 21 Nov | Utrecht Overvecht 14:44Partial coverage | 0 min | — |
| Fri 20 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Thu 19 Nov | Utrecht Overvecht 14:33 | +6 min | +6 min |
| Wed 18 Nov | Utrecht Overvecht 14:28 | +1 min | +1 min |
| Tue 17 Nov | Utrecht Overvecht 14:29 | +2 min | +2 min |
| Mon 16 Nov | Utrecht Overvecht 14:30 | +2 min | +2 min |
| Sun 15 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Sat 14 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Fri 13 Nov | Utrecht Overvecht 14:33 | +6 min | +6 min |
| Thu 12 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Wed 11 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Tue 10 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Mon 9 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Sun 8 Nov | Utrecht Overvecht 14:29 | +1 min | — |
| Sat 7 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Fri 6 Nov | Utrecht Overvecht 14:29 | No data | — |
| Thu 5 Nov | Utrecht Overvecht 14:28 | No data | — |
| Wed 4 Nov | Utrecht Overvecht 14:28 | 0 min | — |
| Tue 3 Nov | Utrecht Overvecht 14:28 | No data | — |
| Mon 2 Nov | Utrecht Overvecht 14:28 | No data | — |
| Sun 1 Nov | Utrecht Overvecht 14:29 | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 14:28 | 0 min | — |
| Fri 30 Oct | Utrecht Overvecht 14:28 | No data | — |
| Thu 29 Oct | Utrecht Overvecht 14:28 | 0 min | — |
| Wed 28 Oct | Utrecht Overvecht 14:28 | 0 min | — |
| Tue 27 Oct | Utrecht Overvecht 14:28 | 0 min | — |
| Mon 26 Oct | Utrecht Overvecht 14:33 | No data | — |
| Sun 25 Oct | Utrecht Overvecht 14:30 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 14:30 | +1 min | — |
| Fri 23 Oct | Utrecht Overvecht 14:32 | No data | — |