Train NS 28766 Amersfoort Vathorst – Hilversum
Not running right now
Last recorded run: Sunday 4 October No data
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
—
Too little data (0/7 runs with data)
RT coverage: 0 full · 0 partial · 7 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)
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
Distribution · 90 days
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 19:00 | |
| 19:04 | |
| 19:08 / 19:10 | |
| 19:17 | |
| 19:22 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | Arnemuiden 21:44 | No data | — |
| Sat 3 Oct | Arnemuiden 21:44 | No data | — |
| Sun 13 Sept | Den Haag Laan v NOI 21:11 | No data | — |
| Sat 12 Sept | Den Haag Laan v NOI 21:05 | No data | — |
| Sun 16 Aug | Houten 19:15 | No data | — |
| Sat 15 Aug | Houten 19:15 | No data | — |
| Thu 13 Aug | Houten 19:10 | No data | — |