Train NS 1591 Amersfoort Centraal → Deventer
NS 1591 Amersfoort Centraal–Deventer: final delay under 3 min on 7 of its 7 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Deventer: 01:44. TrainsRadar data as of 22 Nov 2026, 01:31 (GMT+1).
An alert on this phone or computer when the 1591 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 01:31
Heading to Deventer 0 min
Estimated arrival at Deventer 01:44 · 0 km/h
- Amersfoort Centraal01:06
- Apeldoorn01:32
- Deventer01:44
Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 7 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
- Sat 17 Oct Max en route +10 min · last fix heading to — +10 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 9
- 3–10 min 10% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 83% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 10 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 |
|---|---|---|---|---|
| 01:06 | on time | on time | ||
| 01:32 / 01:34 | ≈ on time | ≈ +1 min | ||
| 01:44 | 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 |
|---|---|---|---|
| Sun 22 Nov | — 01:29 | 0 min | — |
| Sat 21 Nov | — 01:49 | 0 min | — |
| Sun 15 Nov | — 01:44 | 0 min | — |
| Sat 14 Nov | — 01:48 | 0 min | +2 min |
| Sun 8 Nov | — 01:44 | 0 min | — |
| Sat 7 Nov | — 01:44 | 0 min | — |
| Sun 1 Nov | — 01:46 | No data | — |
| Sat 31 Oct | — 01:45 | 0 min | — |
| Sun 18 Oct | Hilversum 01:09 | No data | — |
| Sat 17 Oct | — 01:27 | +10 min | +10 min |
| Sun 11 Oct | — 01:46 | 0 min | — |
| Sat 10 Oct | — 01:45 | 0 min | — |