Train NS 7081 Apeldoorn – Almelo
Running now · updated 23:28
Heading to Almelo +5 min
Estimated arrival at Almelo 23:42 23:37 · 89 km/h
- Apeldoorn22:50
- Apeldoorn Osseveld22:53
- Deventer23:04
- Deventer Colmschate23:11
- Holten23:20
- Wierden23:32
- Almelo23:37
Today it is running worse than usual: typical arrival delay is 0 min; 91% of the last 22 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
- Sun 18 Oct Max en route +7 min · last fix heading to Wierden +7 min
- Mon 12 Oct Max en route +6 min · last fix heading to — +6 min
- Fri 13 Nov Max en route +5 min · last fix heading to — +5 min
- Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 28
- 3–10 min 13% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=6
- 100% W n=5
- 100% T n=6
- 60% F n=5
- 100% S n=2
- 75% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 32 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 |
|---|---|---|---|---|
| 22:50 | on time | on time | ||
| 22:53 | ≈ on time | ≈ on time | ||
| 22:59 | ≈ on time | ≈ +1 min | ||
| 23:04 / 23:06 | ≈ on time | ≈ +2 min | ||
| 23:11 | ≈ on time | ≈ +2 min | ||
| 23:20 | ≈ on time | ≈ +3 min | ||
| 23:27 | ≈ on time | ≈ +4 min | ||
| 23:32 | ≈ on time | ≈ +4 min | ||
| 23:37 | on time | +5 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 |
|---|---|---|---|
| Fri 13 Nov | — 23:24 | +5 min | +5 min |
| Thu 12 Nov | — 23:39 | +2 min | +2 min |
| Wed 11 Nov | — 23:38 | 0 min | — |
| Tue 10 Nov | — 23:52 | 0 min | +28 min |
| Mon 9 Nov | — 23:39 | +1 min | — |
| Sun 8 Nov | Wierden 23:44Partial coverage | 0 min | — |
| Sat 7 Nov | Holten 23:38Partial coverage | 0 min | — |
| Fri 6 Nov | — 23:39 | +1 min | +1 min |
| Thu 5 Nov | — 23:39 | 0 min | — |
| Wed 4 Nov | — 23:38 | 0 min | — |
| Tue 3 Nov | — 23:39 | 0 min | — |
| Sun 1 Nov | Wierden 23:49Partial coverage | +2 min | +3 min |
| Sat 31 Oct | Holten 23:34 | No data | — |
| Fri 30 Oct | — 23:51 | No data | — |
| Thu 29 Oct | — 23:40 | +1 min | +1 min |
| Wed 28 Oct | — 23:38 | 0 min | — |
| Tue 27 Oct | — 23:39 | 0 min | — |
| Mon 26 Oct | — 23:41 | No data | — |
| Sun 25 Oct | Wierden 23:46 | No data | — |
| Sat 24 Oct | — 23:39 | No data | — |
| Fri 23 Oct | — 23:39 | 0 min | — |
| Thu 22 Oct | — 23:39 | 0 min | — |
| Wed 21 Oct | — 23:39 | No data | — |
| Tue 20 Oct | — 23:12 | 0 min | — |
| Mon 19 Oct | — 23:39 | 0 min | — |
| Sun 18 Oct | Wierden 23:50 | +7 min | +7 min |
| Sat 17 Oct | Wierden 23:47 | No data | — |
| Fri 16 Oct | — 23:38 | +1 min | +1 min |
| Thu 15 Oct | — 23:38 | 0 min | — |
| Wed 14 Oct | — 23:38 | 0 min | — |