Train NS 28764 Amersfoort Vathorst – Hilversum
Not running right now
Last recorded run: Friday 30 October 0 min
On-time · 30 days
—
Too little data (1/1 runs with data)
RT coverage: 1 full · 0 partial · 0 no data
On-time · 90 days
—
Too little data (1/8 runs with data)
RT coverage: 1 full · 0 partial · 7 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 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
1 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 1
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=1
- — 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. |
|---|---|
| 18:30 | |
| 18:34 | |
| 18:38 / 18:40 | |
| 18:47 | |
| 18:52 |
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 |
|---|---|---|---|
| Fri 30 Oct | — 19:44 | 0 min | — |
| Sun 4 Oct | Arnemuiden 21:16 | No data | — |
| Sat 3 Oct | Arnemuiden 21:14 | No data | — |
| Sun 13 Sept | Den Haag Laan v NOI 20:36 | No data | — |
| Sat 12 Sept | Den Haag Laan v NOI 20:35 | No data | — |
| Sun 16 Aug | Houten 18:45 | No data | — |
| Sat 15 Aug | Houten 18:47 | No data | — |
| Thu 13 Aug | Houten 18:45 | No data | — |