Train NS 7072 Almelo – Apeldoorn
✓ Today’s run finished
Today, last fix heading to — at 20:18 No data
- Almelo19:23
- Wierden19:28
- Holten19:39
- Deventer Colmschate19:49
- Deventer19:54
- Apeldoorn Osseveld20:06
- Apeldoorn20:10
Next service: tomorrow 19:23 from Almelo · Fri 6 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
- Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
- Wed 7 Oct Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 11
- 3–10 min 15% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 75% W n=4
- 100% T n=2
- 67% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 19:23 | on time | on time | |
| 19:28 | ≈ on time | ≈ on time | |
| 19:34 | ≈ on time | ≈ +1 min | |
| 19:39 | ≈ on time | ≈ +1 min | |
| 19:49 | ≈ on time | ≈ +2 min | |
| 19:54 / 19:55 | ≈ on time | ≈ +2 min | |
| 20:00 | ≈ on time | ≈ +2 min | |
| 20:06 | ≈ on time | ≈ +3 min | |
| 20:10 | on time | +3 min |
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 |
|---|---|---|---|
| Thu 5 Nov | — 20:18 | No data | — |
| Wed 4 Nov | — 20:09 | 0 min | — |
| Tue 3 Nov | — 20:09 | No data | — |
| Mon 2 Nov | — 20:09 | No data | — |
| Thu 29 Oct | — 20:12 | +1 min | +2 min |
| Wed 28 Oct | — 20:11 | 0 min | — |
| Tue 27 Oct | — 20:16 | 0 min | — |
| Mon 26 Oct | — 20:11 | No data | — |
| Fri 23 Oct | Wierden 20:12Partial coverage | 0 min | — |
| Thu 22 Oct | — 20:12 | No data | — |
| Wed 21 Oct | — 20:12 | 0 min | — |
| Tue 20 Oct | — 20:11 | No data | — |
| Fri 16 Oct | Deventer Colmschate 20:03 | 0 min | — |
| Thu 15 Oct | — 19:57 | No data | — |
| Wed 14 Oct | Holten 19:56 | No data | — |
| Tue 13 Oct | — 19:55 | No data | — |
| Mon 12 Oct | — 19:56 | 0 min | — |
| Fri 9 Oct | — 20:22 | +8 min | +8 min |
| Thu 8 Oct | — 20:12 | +1 min | +2 min |
| Wed 7 Oct | — 20:17 | +3 min | +3 min |
| Tue 6 Oct | — 20:11 | 0 min | — |
| Mon 5 Oct | — 20:12 | 0 min | — |
| Fri 28 Aug | Wierden 19:42 | No data | — |
| Fri 21 Aug | Apeldoorn Osseveld 20:20 | No data | — |
| Wed 19 Aug | Almelo 19:37 | No data | — |
| Mon 17 Aug | Holten 19:53 | No data | — |
| Fri 14 Aug | Apeldoorn Osseveld 20:20 | No data | — |
| Thu 13 Aug | Apeldoorn Osseveld 20:20 | No data | — |
| Wed 12 Aug | Apeldoorn Osseveld 20:20 | No data | — |
| Tue 11 Aug | Apeldoorn Osseveld 20:20 | No data | — |