Train NS 1561 Amsterdam Centraal – Deventer
It has not run yet today
Last recorded run: Thursday 19 November +4 min
Next service: today 17:00 from Amsterdam Centraal · Fri 20 Nov
Last 30 days
Arrival delay at Deventer, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 12 Nov Max en route +16 min · last fix heading to Apeldoorn +16 min
- Sat 14 Nov Max en route +10 min · last fix heading to Hilversum +10 min
- Sun 15 Nov Max en route +8 min · last fix heading to Hilversum +7 min
- Tue 17 Nov Max en route +9 min · last fix heading to Apeldoorn +7 min
- Sun 8 Nov Max en route +6 min · last fix heading to Hilversum +6 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 76% · 26
- 3–10 min 18% · 6
- 10–30 min 6% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 80% T n=5
- 83% W n=6
- 50% T n=4
- 100% F n=4
- 75% S n=4
- 40% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 34 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:00 | on time | on time | |
| 17:20 / 17:22 | ≈ on time | ≈ +2 min | |
| 17:33 / 17:36 | ≈ on time | ≈ +3 min | |
| 18:00 / 18:02 | ≈ on time | ≈ +5 min | |
| 18:12 | on time | +6 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 19 Nov | Apeldoorn 18:19Partial coverage | +4 min | +6 min |
| Wed 18 Nov | Apeldoorn 18:18 | +5 min | +6 min |
| Tue 17 Nov | Apeldoorn 18:19Partial coverage | +7 min | +9 min |
| Mon 16 Nov | Apeldoorn 18:15Partial coverage | 0 min | — |
| Sun 15 Nov | Hilversum 17:49 | +7 min | +8 min |
| Sat 14 Nov | Hilversum 17:49 | +10 min | +10 min |
| Fri 13 Nov | Apeldoorn 18:18Partial coverage | +2 min | +3 min |
| Thu 12 Nov | Apeldoorn 18:44Partial coverage | +16 min | +16 min |
| Wed 11 Nov | Apeldoorn 18:14Partial coverage | 0 min | — |
| Tue 10 Nov | Apeldoorn 18:14 | +1 min | +1 min |
| Mon 9 Nov | Apeldoorn 18:14Partial coverage | 0 min | — |
| Sun 8 Nov | Hilversum 17:45 | +6 min | +6 min |
| Sat 7 Nov | Hilversum 17:34 | 0 min | — |
| Fri 6 Nov | Apeldoorn 18:14Partial coverage | 0 min | — |
| Thu 5 Nov | Apeldoorn 18:14 | No data | — |
| Wed 4 Nov | Apeldoorn 18:14Partial coverage | 0 min | — |
| Tue 3 Nov | Apeldoorn 18:14 | No data | — |
| Mon 2 Nov | Apeldoorn 18:14 | No data | — |
| Sun 1 Nov | Hilversum 17:36 | 0 min | — |
| Sat 31 Oct | Hilversum 17:36 | 0 min | — |
| Fri 30 Oct | Apeldoorn 18:16Partial coverage | 0 min | — |
| Thu 29 Oct | Apeldoorn 18:53 | 0 min | — |
| Wed 28 Oct | Apeldoorn 18:51 | 0 min | — |
| Tue 27 Oct | Apeldoorn 18:52 | 0 min | — |
| Mon 26 Oct | Apeldoorn 18:59 | 0 min | — |
| Mon 19 Oct | Apeldoorn 18:21 | 0 min | — |
| Sun 18 Oct | Hilversum 17:35 | 0 min | — |
| Sat 17 Oct | Hilversum 17:35 | No data | — |
| Fri 16 Oct | Hilversum 17:41 | No data | — |
| Thu 15 Oct | Hilversum 17:39 | No data | — |