Train NS 1543 Amsterdam Centraal – Deventer
Running now · updated 13:38
Heading to Deventer 0 min
Estimated arrival at Deventer 13:44 · 108 km/h
- Amsterdam Centraal12:31
- Hilversum12:50
- Amersfoort Centraal13:03
- Apeldoorn13:32
- Deventer13:44
Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 16 runs arrived on time.
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
- Wed 11 Nov Max en route +4 min · last fix heading to Apeldoorn +4 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 25
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 80% W n=5
- 100% T n=3
- 100% F n=3
- 100% S n=3
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 26 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 |
|---|---|---|---|---|
| 12:31 | on time | on time | ||
| 12:50 / 12:52 | ≈ on time | ≈ on time | ||
| 13:03 / 13:06 | ≈ on time | ≈ on time | ||
| 13:32 / 13:34 | ≈ on time | ≈ on time | ||
| 13:44 | 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 13 Nov | Apeldoorn 13:34Partial coverage | 0 min | — |
| Thu 12 Nov | Apeldoorn 13:48Partial coverage | 0 min | — |
| Wed 11 Nov | Apeldoorn 13:48Partial coverage | +4 min | +4 min |
| Tue 10 Nov | Apeldoorn 13:48Partial coverage | 0 min | — |
| Mon 9 Nov | Apeldoorn 13:48Partial coverage | 0 min | — |
| Sun 8 Nov | Hilversum 13:04 | 0 min | — |
| Sat 7 Nov | Hilversum 13:04 | 0 min | — |
| Fri 6 Nov | Apeldoorn 13:48 | No data | — |
| Thu 5 Nov | Apeldoorn 13:48 | No data | — |
| Wed 4 Nov | Apeldoorn 13:48Partial coverage | 0 min | — |
| Tue 3 Nov | Apeldoorn 13:48 | No data | — |
| Mon 2 Nov | Apeldoorn 13:48 | No data | — |
| Sun 1 Nov | Hilversum 13:07 | 0 min | — |
| Sat 31 Oct | Hilversum 13:06 | 0 min | — |
| Fri 30 Oct | Apeldoorn 13:49Partial coverage | 0 min | — |
| Thu 29 Oct | Dieren 14:28 | 0 min | — |
| Wed 28 Oct | Dieren 14:23 | 0 min | — |
| Tue 27 Oct | Dieren 14:23 | 0 min | — |
| Mon 26 Oct | Dieren 14:24 | No data | — |
| Mon 19 Oct | Apeldoorn 13:48Partial coverage | 0 min | — |
| Sun 18 Oct | Hilversum 13:05 | 0 min | — |
| Sat 17 Oct | Hilversum 13:09 | No data | — |
| Fri 16 Oct | Hilversum 13:10 | No data | — |
| Thu 15 Oct | Hilversum 13:09 | No data | — |
| Wed 14 Oct | Hilversum 13:10 | 0 min | — |
| Tue 13 Oct | Hilversum 13:09 | 0 min | — |
| Mon 12 Oct | Hilversum 13:10 | 0 min | — |
| Sun 11 Oct | Hilversum 13:06 | 0 min | — |
| Sat 10 Oct | Hilversum 13:08 | +2 min | +3 min |
| Fri 9 Oct | Apeldoorn 13:48Partial coverage | 0 min | — |