Train NS 5830 Amersfoort Vathorst – Amsterdam Centraal
It has not run yet today
Last recorded run: Saturday 14 November +5 min
Next service: today 09:52 from Amersfoort Vathorst · Sun 15 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 14 Nov Max en route +5 min · last fix heading to Amsterdam Muiderpoort +5 min
Distribution · 90 days
29 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 97% · 28
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=5
- 100% W n=4
- 100% T n=3
- 100% F n=4
- 83% S n=6
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 29 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 |
|---|---|---|---|
| 09:52 | on time | on time | |
| 09:56 | ≈ on time | ≈ on time | |
| 10:00 / 10:01 | ≈ on time | ≈ on time | |
| 10:08 | ≈ on time | ≈ on time | |
| 10:14 / 10:15 | ≈ on time | ≈ on time | |
| 10:17 | ≈ on time | ≈ on time | |
| 10:21 | ≈ on time | ≈ on time | |
| 10:24 | ≈ on time | ≈ on time | |
| 10:30 / 10:32 | ≈ on time | ≈ +1 min | |
| 10:37 | ≈ on time | ≈ +1 min | |
| 10:40 | ≈ on time | ≈ +1 min | |
| 10:43 | ≈ on time | ≈ +1 min | |
| 10:48 | 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 |
|---|---|---|---|
| Sat 14 Nov | Amsterdam Muiderpoort 10:59Partial coverage | +5 min | +5 min |
| Fri 13 Nov | Amsterdam Muiderpoort 10:57 | 0 min | +2 min |
| Thu 12 Nov | Amsterdam Muiderpoort 10:58 | +1 min | +1 min |
| Wed 11 Nov | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Tue 10 Nov | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Mon 9 Nov | Amsterdam Muiderpoort 10:57 | +2 min | +2 min |
| Sun 8 Nov | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Sat 7 Nov | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Fri 6 Nov | Amsterdam Muiderpoort 10:59 | No data | — |
| Thu 5 Nov | Amsterdam Muiderpoort 10:57 | No data | — |
| Wed 4 Nov | Amsterdam Muiderpoort 10:59 | +2 min | +3 min |
| Tue 3 Nov | Amsterdam Muiderpoort 10:57 | No data | — |
| Mon 2 Nov | Amsterdam Muiderpoort 11:02 | 0 min | — |
| Sat 31 Oct | Amsterdam Muiderpoort 10:57 | 0 min | +2 min |
| Fri 30 Oct | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Thu 29 Oct | Amsterdam Muiderpoort 11:12 | No data | — |
| Wed 28 Oct | Amsterdam Muiderpoort 10:57 | No data | — |
| Tue 27 Oct | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Mon 26 Oct | Amsterdam Muiderpoort 10:57 | No data | — |
| Sun 25 Oct | Amsterdam Muiderpoort 10:57 | No data | — |
| Sat 24 Oct | Amsterdam Muiderpoort 10:57 | 0 min | +2 min |
| Fri 23 Oct | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Thu 22 Oct | Amsterdam Muiderpoort 10:58 | No data | — |
| Wed 21 Oct | Amsterdam Muiderpoort 10:57 | No data | — |
| Tue 20 Oct | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Mon 19 Oct | Amsterdam Muiderpoort 10:57 | 0 min | — |
| Sun 18 Oct | Naarden-Bussum 10:49 | +1 min | +1 min |
| Sat 17 Oct | Naarden-Bussum 10:50 | 0 min | — |
| Fri 16 Oct | Amsterdam Muiderpoort 10:57 | No data | — |
| Thu 15 Oct | Amsterdam Muiderpoort 10:57 | 0 min | — |