Train NS 5817 Naarden-Bussum – Amersfoort Centraal

Naarden-Bussum 06:34 → Amersfoort Centraal 06:56 Daily 0 h 22 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Baarn at 07:04 +1 min

  1. Naarden-Bussum06:34
  2. Bussum Zuid06:37
  3. Hilversum Media Park06:41
  4. Hilversum06:43
  5. Baarn06:50
  6. Amersfoort Centraal06:56

Next service: tomorrow 06:34 from Naarden-Bussum · Mon 16 Nov

Next departure 06:34 tomorrow · Naarden-Bussum
On-time · 30 days
92%
24/26 runs under 3 min
RT coverage: 25 full · 1 partial · 4 no data
On-time · 90 days
92%
34/37 runs under 3 min
RT coverage: 36 full · 1 partial · 52 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Amersfoort 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 24 Oct Max en route +9 min · last fix heading to Baarn +9 min
  • Sat 7 Nov Max en route +8 min · last fix heading to Baarn +8 min
  • Mon 12 Oct Max en route +4 min · last fix heading to Baarn +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 34
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • 67% 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, 37 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
06:34on time on time
06:37≈ on time ≈ on time
06:41≈ on time ≈ +1 min
06:43≈ on time ≈ +1 min
06:50≈ on time ≈ +2 min
06:56on 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

DateLast stopFinalMax
Sun 15 NovBaarn 07:04Partial coverage+1 min+1 min
Sat 14 NovBaarn 07:04+1 min+1 min
Fri 13 NovAmersfoort Schothorst 07:170 min—
Thu 12 NovAmersfoort Schothorst 07:170 min—
Wed 11 NovAmersfoort Schothorst 07:170 min—
Tue 10 NovAmersfoort Schothorst 07:18+1 min—
Mon 9 NovAmersfoort Schothorst 07:290 min+17 min
Sun 8 NovBaarn 07:07+3 min+3 min
Sat 7 NovBaarn 07:09+8 min+8 min
Fri 6 NovAmersfoort Schothorst 07:17No data—
Thu 5 NovAmersfoort Schothorst 07:19No data—
Wed 4 NovAmersfoort Schothorst 07:19+2 min+2 min
Tue 3 NovAmersfoort Centraal 07:270 min+9 min
Mon 2 NovAmersfoort Schothorst 07:18No data—
Sun 1 NovBaarn 07:01+1 min—
Sat 31 OctBaarn 07:04+1 min+1 min
Fri 30 OctAmersfoort Schothorst 07:170 min—
Thu 29 OctAmersfoort Schothorst 07:170 min—
Wed 28 OctAmersfoort Schothorst 07:170 min—
Tue 27 OctAmersfoort Schothorst 07:170 min—
Mon 26 OctAmersfoort Schothorst 07:190 min—
Sun 25 OctBaarn 07:06No data—
Sat 24 OctBaarn 07:11+9 min+9 min
Fri 23 OctAmersfoort Schothorst 07:180 min—
Thu 22 OctAmersfoort Schothorst 07:20+2 min+3 min
Wed 21 OctAmersfoort Schothorst 07:170 min—
Tue 20 OctAmersfoort Schothorst 07:170 min—
Mon 19 OctAmersfoort Schothorst 07:170 min—
Sun 18 OctBaarn 06:550 min—
Sat 17 OctBaarn 06:55+1 min+1 min