Train NS 7022 Almelo – Apeldoorn
It has not run yet today
Last recorded run: Wednesday 4 November +5 min
Next service: today 06:53 from Almelo · Thu 5 Nov
Last 30 days
Arrival delay at Apeldoorn, 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 4 Nov Max en route +5 min · last fix heading to Apeldoorn Osseveld +5 min
- Mon 26 Oct Max en route +4 min · last fix heading to Apeldoorn Osseveld +4 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 24
- 3–10 min 8% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=5
- 80% W n=5
- 100% T n=4
- 100% F n=4
- 100% S n=4
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 26 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 |
|---|---|---|---|
| 06:53 | on time | on time | |
| 06:58 | ≈ on time | ≈ on time | |
| 07:04 | ≈ on time | ≈ on time | |
| 07:09 | ≈ on time | ≈ on time | |
| 07:19 | ≈ on time | ≈ on time | |
| 07:24 / 07:25 | ≈ on time | ≈ on time | |
| 07:30 | ≈ on time | ≈ on time | |
| 07:35 | ≈ on time | ≈ on time | |
| 07:40 | on time | on time |
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 |
|---|---|---|---|
| Wed 4 Nov | Apeldoorn Osseveld 07:54Partial coverage | +5 min | +5 min |
| Tue 3 Nov | Apeldoorn Osseveld 07:53Partial coverage | 0 min | — |
| Mon 2 Nov | Apeldoorn Osseveld 07:49 | No data | — |
| Sun 1 Nov | Apeldoorn Osseveld 07:49 | No data | — |
| Sat 31 Oct | Apeldoorn Osseveld 07:50 | +1 min | — |
| Fri 30 Oct | Apeldoorn Osseveld 07:52Partial coverage | +1 min | +2 min |
| Thu 29 Oct | Apeldoorn Osseveld 07:50Partial coverage | 0 min | — |
| Wed 28 Oct | Apeldoorn Osseveld 07:50Partial coverage | 0 min | — |
| Tue 27 Oct | Apeldoorn Osseveld 07:49Partial coverage | 0 min | — |
| Mon 26 Oct | Apeldoorn Osseveld 07:54Partial coverage | +4 min | +4 min |
| Sun 25 Oct | Apeldoorn Osseveld 07:50 | No data | — |
| Sat 24 Oct | Apeldoorn Osseveld 07:50Partial coverage | +1 min | — |
| Fri 23 Oct | Apeldoorn Osseveld 07:51Partial coverage | +1 min | +2 min |
| Thu 22 Oct | Apeldoorn Osseveld 07:53Partial coverage | 0 min | — |
| Wed 21 Oct | Apeldoorn Osseveld 07:55Partial coverage | 0 min | — |
| Tue 20 Oct | Apeldoorn Osseveld 07:50Partial coverage | 0 min | — |
| Mon 19 Oct | Apeldoorn Osseveld 07:50Partial coverage | 0 min | — |
| Sat 17 Oct | Deventer Colmschate 07:34 | 0 min | — |
| Fri 16 Oct | Deventer Colmschate 07:33 | 0 min | — |
| Thu 15 Oct | Deventer Colmschate 07:33 | 0 min | — |
| Wed 14 Oct | Deventer Colmschate 07:33 | 0 min | — |
| Tue 13 Oct | Deventer Colmschate 07:33 | 0 min | — |
| Mon 12 Oct | Deventer Colmschate 07:33 | 0 min | — |
| Sun 11 Oct | Apeldoorn Osseveld 07:50 | 0 min | — |
| Sat 10 Oct | Apeldoorn Osseveld 07:50 | 0 min | — |
| Fri 9 Oct | Apeldoorn Osseveld 07:50Partial coverage | 0 min | +1 min |
| Thu 8 Oct | Apeldoorn Osseveld 07:52Partial coverage | +1 min | +2 min |
| Wed 7 Oct | Apeldoorn Osseveld 07:50Partial coverage | 0 min | — |
| Tue 6 Oct | Apeldoorn Osseveld 07:51Partial coverage | 0 min | +1 min |
| Mon 5 Oct | Apeldoorn Osseveld 07:51 | No data | — |