Train NS 5827 Naarden-Bussum – Amersfoort Vathorst
✓ Today’s run finished
Today, last fix heading to Amersfoort Schothorst at 09:47 0 min
- Naarden-Bussum09:05
- Bussum Zuid09:08
- Hilversum Media Park09:12
- Baarn09:21
- Amersfoort Centraal09:28
- Amersfoort Schothorst09:33
- Amersfoort Vathorst09:37
Next service: tomorrow 09:05 from Naarden-Bussum · Mon 16 Nov
Last 30 days
Arrival delay at Amersfoort Vathorst, 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 4 Nov Max en route +7 min · last fix heading to Amersfoort Schothorst +6 min
- Fri 13 Nov Max en route +4 min · last fix heading to Amersfoort Schothorst +3 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 25
- 3–10 min 7% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=3
- 80% W n=5
- 100% T n=3
- 67% F n=3
- 100% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 27 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:05 | on time | on time | |
| 09:08 | ≈ on time | ≈ on time | |
| 09:12 | ≈ on time | ≈ +1 min | |
| 09:14 / 09:15 | ≈ on time | ≈ +1 min | |
| 09:21 | ≈ on time | ≈ +1 min | |
| 09:28 / 09:29 | ≈ on time | ≈ +2 min | |
| 09:33 | ≈ on time | ≈ +2 min | |
| 09:37 | on time | +3 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 |
|---|---|---|---|
| Sun 15 Nov | Amersfoort Schothorst 09:47Partial coverage | 0 min | — |
| Sat 14 Nov | Amersfoort Schothorst 09:48 | 0 min | — |
| Fri 13 Nov | Amersfoort Schothorst 09:49 | +3 min | +4 min |
| Thu 12 Nov | Amersfoort Schothorst 09:47 | 0 min | — |
| Wed 11 Nov | Amersfoort Schothorst 09:47 | 0 min | — |
| Tue 10 Nov | Amersfoort Schothorst 09:48 | +1 min | +1 min |
| Mon 9 Nov | Amersfoort Schothorst 09:47 | 0 min | — |
| Sun 8 Nov | Amersfoort Schothorst 09:47 | 0 min | — |
| Sat 7 Nov | Amersfoort Schothorst 09:47 | 0 min | — |
| Fri 6 Nov | Amersfoort Schothorst 09:47 | No data | — |
| Thu 5 Nov | Amersfoort Schothorst 09:49 | No data | — |
| Wed 4 Nov | Amersfoort Schothorst 09:54 | +6 min | +7 min |
| Tue 3 Nov | Amersfoort Schothorst 09:49 | No data | — |
| Mon 2 Nov | Amersfoort Schothorst 09:48 | No data | — |
| Sat 31 Oct | Amersfoort Schothorst 09:48 | 0 min | +1 min |
| Fri 30 Oct | Amersfoort Schothorst 09:48 | 0 min | — |
| Thu 29 Oct | Amersfoort Schothorst 09:48 | No data | — |
| Wed 28 Oct | Amersfoort Schothorst 09:47 | 0 min | — |
| Tue 27 Oct | Amersfoort Schothorst 09:48 | 0 min | — |
| Mon 26 Oct | Amersfoort Schothorst 09:48 | No data | — |
| Sun 25 Oct | Amersfoort Schothorst 09:47 | No data | — |
| Sat 24 Oct | Amersfoort Schothorst 09:49 | 0 min | — |
| Fri 23 Oct | Amersfoort Schothorst 09:47 | No data | — |
| Thu 22 Oct | Amersfoort Schothorst 09:49 | No data | — |
| Wed 21 Oct | Amersfoort Schothorst 09:49 | No data | — |
| Tue 20 Oct | Amersfoort Centraal 10:12 | No data | — |
| Mon 19 Oct | Amersfoort Schothorst 09:48 | 0 min | — |
| Sun 18 Oct | Baarn 09:26 | +1 min | +1 min |
| Sat 17 Oct | Baarn 09:25 | +3 min | +3 min |
| Fri 16 Oct | Baarn 09:41 | No data | — |