Train NS 7031 Apeldoorn – Almelo
Running now · updated 10:52
Heading to Almelo 0 min
Estimated arrival at Almelo 11:06 · 93 km/h
- Apeldoorn10:20
- Apeldoorn Osseveld10:23
- Deventer10:34
- Deventer Colmschate10:41
- Holten10:50
- Wierden11:02
- Almelo11:06
Today it is running no worse than usual: typical arrival delay is 0 min; 80% of the last 15 runs arrived on time.
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 11 Nov Max en route +16 min · last fix heading to Wierden +15 min
- Mon 16 Nov Max en route +6 min · last fix heading to Wierden +6 min
- Tue 10 Nov Max en route +4 min · last fix heading to Wierden +4 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 17
- 3–10 min 10% · 2
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 83% T n=6
- 80% W n=5
- 100% T n=3
- 100% 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, 20 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 | Today |
|---|---|---|---|---|
| 10:20 | on time | on time | ||
| 10:23 | — | — | ||
| 10:29 | — | — | ||
| 10:34 / 10:36 | — | — | ||
| 10:41 | — | — | ||
| 10:50 | — | — | ||
| 10:56 | — | — | ||
| 11:02 | — | — | ||
| 11: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.
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 |
|---|---|---|---|
| Tue 17 Nov | Holten 10:49Partial coverage | 0 min | — |
| Mon 16 Nov | Wierden 11:19Partial coverage | +6 min | +6 min |
| Fri 13 Nov | Wierden 11:14Partial coverage | 0 min | — |
| Thu 12 Nov | Wierden 11:14Partial coverage | 0 min | — |
| Wed 11 Nov | Wierden 11:29Partial coverage | +15 min | +16 min |
| Tue 10 Nov | Wierden 11:19Partial coverage | +4 min | +4 min |
| Mon 9 Nov | Wierden 11:14Partial coverage | 0 min | — |
| Fri 6 Nov | Wierden 11:18 | No data | — |
| Thu 5 Nov | Wierden 11:14 | No data | — |
| Wed 4 Nov | Wierden 11:17Partial coverage | +1 min | +2 min |
| Tue 3 Nov | Wierden 11:17 | No data | — |
| Mon 2 Nov | Wierden 11:14 | No data | — |
| Fri 30 Oct | Wierden 11:16 | No data | — |
| Thu 29 Oct | Wierden 11:20 | No data | — |
| Wed 28 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Tue 27 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Mon 26 Oct | Wierden 11:16 | No data | — |
| Fri 23 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Thu 22 Oct | Wierden 11:21Partial coverage | 0 min | — |
| Wed 21 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Tue 20 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Mon 19 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Fri 16 Oct | Wierden 11:16 | No data | — |
| Thu 15 Oct | Wierden 11:16 | No data | — |
| Wed 14 Oct | Wierden 11:16 | No data | — |
| Tue 13 Oct | Wierden 11:16 | 0 min | — |
| Mon 12 Oct | Wierden 11:16 | No data | — |
| Fri 9 Oct | Wierden 11:16Partial coverage | 0 min | — |
| Thu 8 Oct | Wierden 11:17Partial coverage | +1 min | +4 min |
| Wed 7 Oct | Deventer 12:01Partial coverage | 0 min | — |