Train NS 5812 Amersfoort Centraal – Naarden-Bussum

Amersfoort Centraal 05:31 → Naarden-Bussum 05:54 Daily 0 h 23 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Bussum Zuid at 06:05 +1 min

  1. Amersfoort Centraal05:31
  2. Baarn05:38
  3. Hilversum05:44
  4. Hilversum Media Park05:47
  5. Bussum Zuid05:51
  6. Naarden-Bussum05:54

Next service: tomorrow 05:31 from Amersfoort Centraal · Mon 16 Nov

Next departure 05:31 tomorrow · Amersfoort Centraal
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 2 no data
On-time · 90 days
92%
36/39 runs under 3 min
RT coverage: 38 full · 1 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Fri 23 Oct Max en route +15 min · last fix heading to Diemen +15 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Amsterdam Muiderpoort +4 min
  • Thu 5 Nov Max en route +3 min · last fix heading to Amsterdam Muiderpoort +3 min

Distribution · 90 days

39 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 92% · 36
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=6
  • 83% T n=6
  • 80% F n=5
  • 83% S n=6
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 stops).

Last 90 days, 39 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.

StopSched.Usually 9 days in 10
05:31on time on time
05:38≈ on time ≈ +1 min
05:44 / 05:45≈ on time ≈ +1 min
05:47≈ on time ≈ +1 min
05:51≈ on time ≈ +2 min
05:54on 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

DateLast stopFinalMax
Sun 15 NovBussum Zuid 06:05Partial coverage+1 min—
Sat 14 NovAmsterdam Muiderpoort 06:270 min—
Fri 13 NovAmsterdam Muiderpoort 06:270 min—
Thu 12 NovAmsterdam Muiderpoort 06:270 min—
Wed 11 NovAmsterdam Muiderpoort 06:270 min—
Tue 10 NovAmsterdam Muiderpoort 06:29+3 min+4 min
Mon 9 NovAmsterdam Muiderpoort 06:27+1 min—
Sun 8 NovAmsterdam Muiderpoort 06:270 min—
Sat 7 NovAmsterdam Muiderpoort 06:270 min—
Fri 6 NovAmsterdam Muiderpoort 06:27No data—
Thu 5 NovAmsterdam Muiderpoort 06:29+3 min+3 min
Wed 4 NovAmsterdam Muiderpoort 06:27+1 min—
Tue 3 NovAmsterdam Muiderpoort 06:28+1 min—
Mon 2 NovAmsterdam Muiderpoort 06:270 min—
Sun 1 NovAmsterdam Muiderpoort 06:270 min—
Sat 31 OctAmsterdam Muiderpoort 06:28+1 min—
Fri 30 OctAmsterdam Muiderpoort 06:270 min—
Thu 29 OctAmsterdam Muiderpoort 06:270 min—
Wed 28 OctAmsterdam Muiderpoort 06:280 min—
Tue 27 OctAmsterdam Muiderpoort 06:270 min—
Mon 26 OctAmsterdam Muiderpoort 06:28+1 min—
Sun 25 OctAmsterdam Muiderpoort 06:30No data—
Sat 24 OctAmsterdam Muiderpoort 06:270 min—
Fri 23 OctDiemen 06:51+15 min+15 min
Thu 22 OctAmsterdam Muiderpoort 06:270 min—
Wed 21 OctAmsterdam Muiderpoort 06:270 min—
Tue 20 OctAmsterdam Muiderpoort 06:270 min—
Mon 19 OctAmsterdam Muiderpoort 06:270 min—
Sun 18 OctNaarden-Bussum 06:180 min—
Sat 17 OctNaarden-Bussum 06:180 min—