Train NS 1534 Deventer – Amsterdam Centraal
✓ Today’s run finished
Today, last fix heading to Hilversum at 11:33 +2 min
- Deventer10:18
- Apeldoorn10:28
- Amersfoort Centraal10:54
- Hilversum11:07
- Amsterdam Centraal11:29
Next service: tomorrow 10:18 from Deventer · Wed 18 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
- Wed 11 Nov Max en route +18 min · last fix heading to Hilversum +17 min
- Thu 8 Oct Max en route +12 min · last fix heading to Hilversum +11 min
- Wed 4 Nov Max en route +7 min · last fix heading to Hilversum +7 min
- Sun 11 Oct Max en route +5 min · last fix heading to Hilversum +5 min
- Thu 12 Nov Max en route +5 min · last fix heading to Hilversum +5 min
Distribution · 90 days
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 24
- 3–10 min 13% · 4
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 60% W n=5
- 33% T n=3
- 100% F n=2
- 80% S n=5
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 30 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 |
|---|---|---|---|
| 10:18 | on time | on time | |
| 10:28 / 10:30 | ≈ on time | ≈ on time | |
| 10:54 / 10:56 | ≈ on time | ≈ +2 min | |
| 11:07 / 11:09 | ≈ on time | ≈ +2 min | |
| 11:29 | on time | +3 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 |
|---|---|---|---|
| Tue 17 Nov | Hilversum 11:33Partial coverage | +2 min | +5 min |
| Mon 16 Nov | Hilversum 11:29 | 0 min | — |
| Sun 15 Nov | Hilversum 11:34 | +2 min | +3 min |
| Sat 14 Nov | Hilversum 11:29 | 0 min | — |
| Fri 13 Nov | Hilversum 11:29Partial coverage | +1 min | +1 min |
| Thu 12 Nov | Hilversum 11:34Partial coverage | +5 min | +5 min |
| Wed 11 Nov | Hilversum 12:04Partial coverage | +17 min | +18 min |
| Tue 10 Nov | Amersfoort Centraal 11:09Partial coverage | 0 min | — |
| Mon 9 Nov | Hilversum 11:29Partial coverage | 0 min | — |
| Sun 8 Nov | Hilversum 11:29 | +1 min | +1 min |
| Sat 7 Nov | Hilversum 11:34 | +5 min | +5 min |
| Fri 6 Nov | Hilversum 11:24 | No data | — |
| Thu 5 Nov | Hilversum 11:29 | No data | — |
| Wed 4 Nov | Hilversum 11:29Partial coverage | +7 min | +7 min |
| Tue 3 Nov | Hilversum 11:24 | No data | — |
| Mon 2 Nov | Hilversum 11:48 | No data | — |
| Sun 1 Nov | Hilversum 11:31 | 0 min | — |
| Sat 31 Oct | Amersfoort Centraal 11:30 | 0 min | — |
| Fri 30 Oct | Apeldoorn 11:35 | No data | — |
| Thu 29 Oct | Hilversum 11:37 | 0 min | — |
| Wed 28 Oct | Hilversum 11:36 | 0 min | — |
| Tue 27 Oct | Hilversum 11:31 | 0 min | — |
| Mon 26 Oct | Hilversum 11:30 | 0 min | — |
| Mon 19 Oct | Hilversum 11:30Partial coverage | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 11:06 | +1 min | +1 min |
| Sat 17 Oct | Amersfoort Centraal 11:05 | 0 min | — |
| Fri 16 Oct | Hilversum 11:31 | No data | — |
| Thu 15 Oct | Hilversum 11:32 | No data | — |
| Wed 14 Oct | Hilversum 11:23 | 0 min | — |
| Tue 13 Oct | Hilversum 11:33 | 0 min | — |