Train NS 1556 Deventer – Amsterdam Centraal
✓ Today’s run finished
Today, last fix heading to Hilversum at 17:03 +1 min
- Deventer15:48
- Apeldoorn15:58
- Amersfoort Centraal16:24
- Hilversum16:37
- Amsterdam Centraal16:59
Next service: tomorrow 15:48 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
- Mon 16 Nov Max en route +15 min · last fix heading to Hilversum +15 min
- Thu 12 Nov Max en route +10 min · last fix heading to Hilversum +10 min
- Fri 13 Nov Max en route +10 min · last fix heading to Hilversum +10 min
- Mon 5 Oct Max en route +6 min · last fix heading to Hilversum +6 min
- Mon 9 Nov Max en route +5 min · last fix heading to Hilversum +5 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 81% · 26
- 3–10 min 13% · 4
- 10–30 min 6% · 2
- 30+ min 0% · 0
On-time by weekday
- 50% M n=6
- 100% T n=5
- 100% W n=3
- 75% T n=4
- 80% F n=5
- 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, 32 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:48 | on time | on time | |
| 15:58 / 16:00 | ≈ on time | ≈ +1 min | |
| 16:24 / 16:26 | ≈ on time | ≈ +2 min | |
| 16:37 / 16:39 | ≈ on time | ≈ +3 min | |
| 16:59 | on time | +4 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 17:03Partial coverage | +1 min | +1 min |
| Mon 16 Nov | Hilversum 17:29Partial coverage | +15 min | +15 min |
| Sun 15 Nov | Hilversum 16:59 | 0 min | — |
| Sat 14 Nov | Hilversum 17:02 | +1 min | +1 min |
| Fri 13 Nov | Hilversum 17:09 | +10 min | +10 min |
| Thu 12 Nov | Hilversum 17:13Partial coverage | +10 min | +10 min |
| Wed 11 Nov | Hilversum 16:59Partial coverage | 0 min | — |
| Tue 10 Nov | Amersfoort Centraal 16:39Partial coverage | 0 min | — |
| Mon 9 Nov | Hilversum 16:54Partial coverage | +5 min | +5 min |
| Sun 8 Nov | Hilversum 17:00 | 0 min | — |
| Sat 7 Nov | Hilversum 16:59 | 0 min | — |
| Fri 6 Nov | Hilversum 16:59 | 0 min | — |
| Thu 5 Nov | Hilversum 16:59Partial coverage | 0 min | — |
| Wed 4 Nov | Hilversum 17:04Partial coverage | 0 min | — |
| Tue 3 Nov | Hilversum 16:59Partial coverage | 0 min | — |
| Mon 2 Nov | Hilversum 16:53 | No data | — |
| Sun 1 Nov | Amersfoort Centraal 17:01 | 0 min | — |
| Sat 31 Oct | Hilversum 17:03 | +1 min | +2 min |
| Fri 30 Oct | Hilversum 17:00 | 0 min | — |
| Thu 29 Oct | Hilversum 17:00 | 0 min | — |
| Wed 28 Oct | Hilversum 17:00 | No data | — |
| Tue 27 Oct | Hilversum 17:06 | 0 min | — |
| Mon 26 Oct | Hilversum 17:00 | 0 min | — |
| Mon 19 Oct | Deventer 17:14Partial coverage | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 16:35 | 0 min | — |
| Sat 17 Oct | Amersfoort Centraal 16:50 | No data | — |
| Fri 16 Oct | Hilversum 17:00 | 0 min | — |
| Thu 15 Oct | Hilversum 17:00 | No data | — |
| Wed 14 Oct | Hilversum 17:06 | No data | — |
| Tue 13 Oct | Hilversum 17:05 | No data | — |