Train NS 7066 Almelo – Apeldoorn
✓ Today’s run finished
Today, last fix heading to Apeldoorn Osseveld at 18:49 0 min
- Almelo17:53
- Wierden17:58
- Holten18:09
- Deventer Colmschate18:19
- Deventer18:24
- Apeldoorn Osseveld18:35
- Apeldoorn18:40
Next service: tomorrow 17:53 from Almelo · Sun 8 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
- Sat 31 Oct Max en route +5 min · last fix heading to Apeldoorn Osseveld +4 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 18
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=2
- 100% W n=2
- 100% T n=1
- 100% F n=4
- 67% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 17:53 | on time | on time | |
| 17:58 | ≈ on time | ≈ on time | |
| 18:04 | ≈ on time | ≈ on time | |
| 18:09 | ≈ on time | ≈ on time | |
| 18:19 | ≈ on time | ≈ on time | |
| 18:24 / 18:25 | ≈ on time | ≈ on time | |
| 18:30 | ≈ on time | ≈ +1 min | |
| 18:35 | ≈ on time | ≈ +1 min | |
| 18:40 | on time | +1 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 |
|---|---|---|---|
| Sat 7 Nov | Apeldoorn Osseveld 18:49Partial coverage | 0 min | — |
| Fri 6 Nov | Apeldoorn Osseveld 18:44 | 0 min | — |
| Thu 5 Nov | Holten 18:39 | No data | — |
| Wed 4 Nov | Holten 18:39 | No data | — |
| Tue 3 Nov | Holten 18:39 | No data | — |
| Mon 2 Nov | Holten 18:39 | 0 min | — |
| Sun 1 Nov | Apeldoorn Osseveld 18:49Partial coverage | 0 min | +2 min |
| Sat 31 Oct | Apeldoorn Osseveld 18:54Partial coverage | +4 min | +5 min |
| Fri 30 Oct | Apeldoorn Osseveld 18:49 | No data | — |
| Thu 29 Oct | Wierden 18:41 | No data | — |
| Wed 28 Oct | Holten 18:42 | 0 min | — |
| Tue 27 Oct | Rijssen 18:48 | No data | — |
| Mon 26 Oct | Holten 18:42 | 0 min | — |
| Sun 25 Oct | Apeldoorn Osseveld 18:50 | No data | — |
| Sat 24 Oct | Apeldoorn Osseveld 18:51 | No data | — |
| Fri 23 Oct | Apeldoorn Osseveld 18:49 | 0 min | — |
| Thu 22 Oct | Apeldoorn Osseveld 18:49 | No data | — |
| Wed 21 Oct | Apeldoorn Osseveld 18:49 | No data | — |
| Tue 20 Oct | Apeldoorn Osseveld 18:49 | 0 min | — |
| Mon 19 Oct | Apeldoorn Osseveld 18:49 | No data | — |
| Sun 18 Oct | Deventer Colmschate 18:33 | 0 min | — |
| Sat 17 Oct | Deventer Colmschate 18:33 | No data | — |
| Fri 16 Oct | Deventer Colmschate 18:30 | 0 min | — |
| Thu 15 Oct | Deventer Colmschate 18:33 | No data | — |
| Wed 14 Oct | Deventer Colmschate 18:33 | No data | — |
| Tue 13 Oct | Deventer Colmschate 18:33 | No data | — |
| Mon 12 Oct | Deventer Colmschate 18:32 | 0 min | — |
| Sun 11 Oct | Apeldoorn Osseveld 18:50Partial coverage | 0 min | — |
| Sat 10 Oct | Apeldoorn Osseveld 18:51Partial coverage | 0 min | +2 min |
| Fri 9 Oct | Apeldoorn Osseveld 18:49 | +1 min | — |