Train NS 28712
It does not run today
Last recorded run: Friday 30 October 0 min
The mini-map returns when the train runs
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/6 runs with data)
RT coverage: 1 full · 0 partial · 5 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
Delay at the end of each run, 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
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 30 Oct | Blerick 06:52 | 0 min | — |
| Sun 4 Oct | Arnemuiden 08:14 | No data | — |
| Sat 3 Oct | Arnemuiden 08:14 | No data | — |
| Fri 2 Oct | Arnemuiden 08:15 | No data | — |
| Sun 13 Sept | Den Haag Laan v NOI 07:35 | No data | — |
| Sat 12 Sept | Den Haag Laan v NOI 07:23 | No data | — |
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.