Train NS 1542 Deventer – Amsterdam Centraal
Running now · updated 13:16
Heading to Amsterdam Centraal 0 min
Estimated arrival at Amsterdam Centraal 13:29 · 123 km/h
- Deventer12:18
- Apeldoorn12:28
- Amersfoort Centraal12:54
- Hilversum13:07
- Amsterdam Centraal13:29
Today it is running no worse than usual: typical arrival delay is 0 min; 79% of the last 19 runs arrived on time.
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 18 Nov Max en route +13 min · last fix heading to Hilversum +12 min
- Mon 16 Nov Max en route +12 min · last fix heading to Hilversum +12 min
- Tue 17 Nov Max en route +5 min · last fix heading to Deventer +5 min
- Thu 19 Nov Max en route +4 min · last fix heading to Hilversum +4 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 87% · 26
- 3–10 min 7% · 2
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 67% T n=3
- 83% W n=6
- 75% T n=4
- 100% F n=4
- 100% 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, 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 | Today |
|---|---|---|---|---|
| 12:18 | on time | on time | ||
| 12:28 / 12:30 | ≈ on time | ≈ on time | ||
| 12:54 / 12:56 | ≈ on time | ≈ on time | ||
| 13:07 / 13:09 | ≈ on time | ≈ +1 min | ||
| 13:29 | 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 |
|---|---|---|---|
| Fri 20 Nov | Hilversum 13:14Partial coverage | 0 min | — |
| Thu 19 Nov | Hilversum 13:34Partial coverage | +4 min | +4 min |
| Wed 18 Nov | Hilversum 13:49Partial coverage | +12 min | +13 min |
| Tue 17 Nov | Deventer 13:29Partial coverage | +5 min | +5 min |
| Mon 16 Nov | Hilversum 13:35Partial coverage | +12 min | +12 min |
| Sun 15 Nov | Hilversum 13:30 | 0 min | — |
| Sat 14 Nov | Hilversum 13:29 | 0 min | — |
| Fri 13 Nov | Hilversum 13:29Partial coverage | 0 min | — |
| Thu 12 Nov | Hilversum 13:29Partial coverage | 0 min | — |
| Wed 11 Nov | Hilversum 13:29Partial coverage | 0 min | — |
| Tue 10 Nov | Amersfoort Centraal 13:09Partial coverage | 0 min | — |
| Mon 9 Nov | Hilversum 13:29Partial coverage | 0 min | — |
| Sun 8 Nov | Hilversum 13:24 | 0 min | — |
| Sat 7 Nov | Hilversum 13:29 | 0 min | — |
| Fri 6 Nov | Hilversum 13:29 | No data | — |
| Thu 5 Nov | Hilversum 13:52 | No data | — |
| Wed 4 Nov | Hilversum 13:29Partial coverage | 0 min | — |
| Tue 3 Nov | Hilversum 13:29 | No data | — |
| Mon 2 Nov | Hilversum 13:29 | No data | — |
| Sun 1 Nov | Amersfoort Centraal 13:33 | +2 min | +2 min |
| Sat 31 Oct | Hilversum 13:33 | +1 min | +1 min |
| Fri 30 Oct | Hilversum 13:23 | No data | — |
| Thu 29 Oct | Hilversum 13:31 | 0 min | — |
| Wed 28 Oct | Hilversum 13:31 | 0 min | — |
| Tue 27 Oct | Hilversum 13:31 | No data | — |
| Mon 26 Oct | Hilversum 13:24 | No data | — |
| Mon 19 Oct | Hilversum 13:30 | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 13:06 | 0 min | — |
| Sat 17 Oct | Amersfoort Centraal 13:25 | No data | — |
| Fri 16 Oct | Hilversum 13:31 | 0 min | — |