Train NS 7083 Apeldoorn – Almelo
It does not run today
Last recorded run: Friday 9 October 0 min
Next service: Monday 23:20 from Apeldoorn · Mon 12 Oct
Next departure 23:20 Monday · Apeldoorn
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min
Last 30 days
Arrival delay at Almelo, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 4
- 3–10 min 20% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- 0% W n=1
- 100% T n=1
- 100% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
| Stop | Sched. |
|---|---|
| 23:20 | |
| 23:23 | |
| 23:29 | |
| 23:34 / 23:36 | |
| 23:41 | |
| 23:50 | |
| 23:56 | |
| 00:02 | |
| 00:06 |
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 9 Oct | — 00:07 | 0 min | — |
| Thu 8 Oct | — 00:08 | 0 min | — |
| Wed 7 Oct | — 00:12 | +4 min | +4 min |
| Tue 6 Oct | — 00:07 | 0 min | — |
| Mon 5 Oct | — 00:07 | 0 min | — |