Train NS 1554 Deventer – Amsterdam Centraal
It has not run yet today
Last recorded run: Monday 16 November +12 min
Next service: today 15:19 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
- Sat 10 Oct Max en route +29 min · last fix heading to Hilversum +29 min
- Mon 16 Nov Max en route +12 min · last fix heading to Amersfoort Centraal +12 min
- Mon 9 Nov Max en route +11 min · last fix heading to Hilversum +10 min
- Thu 12 Nov Max en route +7 min · last fix heading to Hilversum +7 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 85% · 23
- 3–10 min 7% · 2
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 60% M n=5
- 100% T n=2
- 100% W n=4
- 67% T n=3
- 100% F n=4
- 75% 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 |
|---|---|---|---|
| 15:19 | on time | on time | |
| 15:29 / 15:30 | ≈ on time | ≈ on time | |
| 15:54 / 15:56 | ≈ on time | ≈ +1 min | |
| 16:07 / 16:09 | ≈ on time | ≈ +2 min | |
| 16:29 | 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 16:39Partial coverage | +12 min | +12 min |
| Sun 15 Nov | Hilversum 16:29 | +1 min | +1 min |
| Sat 14 Nov | Hilversum 16:34 | +3 min | +3 min |
| Fri 13 Nov | Hilversum 16:32Partial coverage | +1 min | +1 min |
| Thu 12 Nov | Hilversum 16:34Partial coverage | +7 min | +7 min |
| Wed 11 Nov | Hilversum 16:29Partial coverage | 0 min | — |
| Tue 10 Nov | Amersfoort Centraal 16:09Partial coverage | 0 min | — |
| Mon 9 Nov | Hilversum 16:49Partial coverage | +10 min | +11 min |
| Sun 8 Nov | Hilversum 16:30 | 0 min | — |
| Sat 7 Nov | Hilversum 16:29 | +1 min | — |
| Fri 6 Nov | Hilversum 16:34 | No data | — |
| Thu 5 Nov | Hilversum 16:30 | No data | — |
| Wed 4 Nov | Hilversum 16:29Partial coverage | 0 min | +1 min |
| Tue 3 Nov | Hilversum 16:29 | No data | — |
| Mon 2 Nov | Hilversum 16:29 | No data | — |
| Sun 1 Nov | Hilversum 16:31 | 0 min | — |
| Sat 31 Oct | Hilversum 16:30 | 0 min | — |
| Fri 30 Oct | Hilversum 16:30Partial coverage | 0 min | — |
| Thu 29 Oct | Hilversum 16:31 | 0 min | — |
| Wed 28 Oct | Hilversum 16:30 | 0 min | — |
| Tue 27 Oct | Hilversum 16:31 | No data | — |
| Mon 26 Oct | Hilversum 16:31 | No data | — |
| Mon 19 Oct | Hilversum 16:24Partial coverage | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 16:05 | 0 min | — |
| Sat 17 Oct | Amersfoort Centraal 16:06 | No data | — |
| Fri 16 Oct | Hilversum 16:30 | 0 min | — |
| Thu 15 Oct | Amersfoort Centraal 16:30 | No data | — |
| Wed 14 Oct | Hilversum 16:31 | No data | — |
| Tue 13 Oct | Hilversum 16:31 | No data | — |
| Mon 12 Oct | Hilversum 16:31 | +1 min | +2 min |