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