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