Train NS 1520 Deventer – Amsterdam Centraal
✓ Today’s run finished
Today, last fix heading to Hilversum at 07:59 No data
- Deventer06:48
- Apeldoorn06:58
- Amersfoort Centraal07:24
- Hilversum07:37
- Amsterdam Centraal07:59
Next service: tomorrow 06:48 from Deventer · Fri 6 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
- Fri 30 Oct Max en route +5 min · last fix heading to Hilversum +5 min
- Sat 17 Oct Max en route +3 min · last fix heading to Amersfoort Centraal +3 min
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 15
- 3–10 min 12% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 100% W n=4
- 100% T n=2
- 50% F n=2
- 0% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 17 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 |
|---|---|---|---|
| 06:48 | on time | on time | |
| 06:58 / 07:00 | ≈ on time | ≈ on time | |
| 07:24 / 07:26 | ≈ on time | ≈ on time | |
| 07:37 / 07:39 | ≈ on time | ≈ +1 min | |
| 07:59 | 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 |
|---|---|---|---|
| Thu 5 Nov | Hilversum 07:59 | No data | — |
| Wed 4 Nov | Hilversum 07:59Partial coverage | 0 min | — |
| Tue 3 Nov | Hilversum 08:04Partial coverage | 0 min | — |
| Mon 2 Nov | Hilversum 07:59Partial coverage | 0 min | — |
| Fri 30 Oct | Hilversum 08:05Partial coverage | +5 min | +5 min |
| Thu 29 Oct | Hilversum 08:00 | 0 min | — |
| Wed 28 Oct | Hilversum 08:00 | 0 min | — |
| Tue 27 Oct | Hilversum 08:01 | 0 min | — |
| Mon 26 Oct | Hilversum 08:03 | 0 min | — |
| Mon 19 Oct | Hilversum 08:00Partial coverage | 0 min | — |
| Sat 17 Oct | Amersfoort Centraal 07:38 | +3 min | +3 min |
| Fri 16 Oct | Hilversum 08:06 | No data | — |
| Thu 15 Oct | Amersfoort Centraal 08:05 | No data | — |
| Wed 14 Oct | Hilversum 08:00 | 0 min | — |
| Tue 13 Oct | Hilversum 08:00 | 0 min | — |
| Mon 12 Oct | Hilversum 08:01 | 0 min | — |
| Fri 9 Oct | Hilversum 08:02Partial coverage | 0 min | — |
| Thu 8 Oct | Hilversum 08:01Partial coverage | 0 min | — |
| Wed 7 Oct | Hilversum 08:00Partial coverage | 0 min | — |
| Tue 6 Oct | Hilversum 08:00Partial coverage | 0 min | — |
| Mon 5 Oct | Hilversum 07:54 | No data | — |
| Fri 2 Oct | Hilversum 07:53 | No data | — |
| Thu 1 Oct | Hilversum 07:53 | No data | — |
| Wed 30 Sept | Hilversum 07:53 | No data | — |
| Tue 29 Sept | Hilversum 07:53 | No data | — |
| Mon 28 Sept | Hilversum 07:54 | No data | — |
| Fri 25 Sept | Hilversum 07:53 | No data | — |
| Thu 24 Sept | Hilversum 07:53 | No data | — |
| Wed 23 Sept | Hilversum 07:54 | No data | — |
| Tue 22 Sept | Hilversum 07:55 | No data | — |