Train NS 7020 Almelo – Apeldoorn
✓ Today’s run finished
Today, last fix heading to Apeldoorn Osseveld at 07:19 No data
- Almelo06:23
- Wierden06:28
- Holten06:39
- Deventer Colmschate06:49
- Deventer06:54
- Apeldoorn Osseveld07:06
- Apeldoorn07:10
Next service: Monday 06:23 from Almelo · Mon 9 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
Distribution · 90 days
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 21
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=5
- 100% W n=5
- 100% T n=4
- 100% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 21 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:23 | on time | on time | |
| 06:28 | ≈ on time | ≈ on time | |
| 06:34 | ≈ on time | ≈ on time | |
| 06:39 | ≈ on time | ≈ on time | |
| 06:49 | ≈ on time | ≈ on time | |
| 06:54 / 06:55 | ≈ on time | ≈ on time | |
| 07:00 | ≈ on time | ≈ on time | |
| 07:06 | ≈ on time | ≈ on time | |
| 07:10 | 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 |
|---|---|---|---|
| Fri 6 Nov | Apeldoorn Osseveld 07:19 | No data | — |
| Thu 5 Nov | Apeldoorn Osseveld 07:19 | No data | — |
| Wed 4 Nov | Apeldoorn Osseveld 07:23Partial coverage | +3 min | +3 min |
| Tue 3 Nov | Apeldoorn Osseveld 07:19Partial coverage | +1 min | +1 min |
| Mon 2 Nov | Apeldoorn Osseveld 07:22 | No data | — |
| Fri 30 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Thu 29 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Wed 28 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Tue 27 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Mon 26 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Fri 23 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Thu 22 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Wed 21 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Tue 20 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Mon 19 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Fri 16 Oct | Deventer Colmschate 07:03 | 0 min | — |
| Thu 15 Oct | Deventer Colmschate 07:03 | 0 min | — |
| Wed 14 Oct | Deventer Colmschate 07:03 | 0 min | — |
| Tue 13 Oct | Deventer Colmschate 07:03 | 0 min | — |
| Mon 12 Oct | Deventer Colmschate 07:04 | 0 min | — |
| Fri 9 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Thu 8 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Wed 7 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Tue 6 Oct | Apeldoorn Osseveld 07:20Partial coverage | 0 min | — |
| Mon 5 Oct | Apeldoorn Osseveld 07:21 | No data | — |
| Fri 2 Oct | Apeldoorn Osseveld 07:20 | No data | — |
| Thu 1 Oct | Apeldoorn Osseveld 07:21 | No data | — |
| Wed 30 Sept | Apeldoorn Osseveld 07:20 | No data | — |
| Tue 29 Sept | Apeldoorn Osseveld 07:20 | No data | — |
| Mon 28 Sept | Apeldoorn Osseveld 07:20 | No data | — |