Train NS 5820 Amersfoort Centraal – Naarden-Bussum
✓ Today’s run finished
Today, last fix heading to Bussum Zuid at 08:08 +2 min
- Amersfoort Centraal07:31
- Baarn07:38
- Hilversum07:44
- Hilversum Media Park07:47
- Bussum Zuid07:51
- Naarden-Bussum07:54
Next service: tomorrow 07:31 from Amersfoort Centraal · Mon 16 Nov
Last 30 days
Arrival delay at Naarden-Bussum, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 11 Oct Max en route +30 min · last fix heading to Bussum Zuid +30 min
- Tue 10 Nov Max en route +12 min · last fix heading to Amsterdam Muiderpoort +11 min
- Thu 8 Oct Max en route +8 min · last fix heading to Amsterdam Muiderpoort +7 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 90% · 26
- 3–10 min 3% · 1
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 75% T n=4
- 100% W n=3
- 75% T n=4
- 100% F n=4
- 100% S n=6
- 75% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 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 |
|---|---|---|---|
| 07:31 | on time | on time | |
| 07:38 | ≈ on time | ≈ +1 min | |
| 07:44 / 07:45 | ≈ on time | ≈ +2 min | |
| 07:47 | ≈ on time | ≈ +2 min | |
| 07:51 | ≈ on time | ≈ +3 min | |
| 07:54 | 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 | Bussum Zuid 08:08Partial coverage | +2 min | +2 min |
| Sat 14 Nov | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Fri 13 Nov | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Thu 12 Nov | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Wed 11 Nov | Amsterdam Muiderpoort 08:28 | +1 min | — |
| Tue 10 Nov | Amsterdam Muiderpoort 08:39 | +11 min | +12 min |
| Mon 9 Nov | Amsterdam Muiderpoort 08:28 | +1 min | +1 min |
| Sun 8 Nov | Amsterdam Muiderpoort 08:28 | 0 min | — |
| Sat 7 Nov | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Fri 6 Nov | Amsterdam Muiderpoort 08:27 | No data | — |
| Thu 5 Nov | Amsterdam Muiderpoort 08:29 | No data | — |
| Wed 4 Nov | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Tue 3 Nov | Amsterdam Muiderpoort 08:29 | 0 min | — |
| Mon 2 Nov | Amsterdam Muiderpoort 08:27 | No data | — |
| Sat 31 Oct | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Fri 30 Oct | Amsterdam Muiderpoort 08:28 | +2 min | +2 min |
| Thu 29 Oct | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Wed 28 Oct | Amsterdam Muiderpoort 08:28 | No data | — |
| Tue 27 Oct | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Mon 26 Oct | Amsterdam Muiderpoort 08:28 | +2 min | +2 min |
| Sun 25 Oct | Amsterdam Muiderpoort 08:27 | No data | — |
| Sat 24 Oct | Amsterdam Muiderpoort 08:28 | +2 min | +2 min |
| Fri 23 Oct | Amsterdam Muiderpoort 08:28 | 0 min | — |
| Thu 22 Oct | Amsterdam Muiderpoort 08:28 | 0 min | — |
| Wed 21 Oct | Amsterdam Muiderpoort 08:27 | No data | — |
| Tue 20 Oct | Amsterdam Muiderpoort 08:27 | No data | — |
| Mon 19 Oct | Amsterdam Muiderpoort 08:27 | 0 min | — |
| Sun 18 Oct | Naarden-Bussum 08:19 | 0 min | +1 min |
| Sat 17 Oct | Naarden-Bussum 08:19 | 0 min | +1 min |
| Fri 16 Oct | Amsterdam Muiderpoort 08:27 | No data | — |