Train RRReis K 31414 Barneveld Zuid – Amersfoort Centraal

Barneveld Zuid 08:24 → Amersfoort Centraal 08:45 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 5 stops RRReis K

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 08:24 from Barneveld Zuid · Fri 20 Nov

Next departure 08:24 today · Barneveld Zuid
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 2 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 1 full · 18 partial · 23 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
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

  • Fri 9 Oct Max en route +4 min · last fix heading to Hoevelaken +4 min
  • Wed 7 Oct Max en route +3 min · last fix heading to Hoevelaken +3 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Hoevelaken +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 16
  • 3–10 min 16% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=6
  • 75% W n=4
  • 100% T n=3
  • 50% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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
08:24on time on time
08:26 / 08:29— —
08:32— —
08:39— —
08:45— —

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
Wed 18 NovHoevelaken 08:54Partial coverage0 min—
Tue 17 NovHoevelaken 08:54Partial coverage+2 min+2 min
Mon 16 NovHoevelaken 08:54Partial coverage+3 min+3 min
Fri 13 NovHoevelaken 08:54Partial coverage+1 min+1 min
Thu 12 NovHoevelaken 08:54Partial coverage+2 min+2 min
Wed 11 NovHoevelaken 08:57Partial coverage+3 min+3 min
Tue 10 NovHoevelaken 08:54Partial coverage+3 min+3 min
Mon 9 NovHoevelaken 08:54Partial coverage+1 min+1 min
Fri 6 NovHoevelaken 08:54No data—
Thu 5 NovHoevelaken 08:54No data—
Wed 4 NovHoevelaken 08:54Partial coverage+1 min—
Tue 3 NovHoevelaken 08:58Partial coverage0 min—
Mon 2 NovHoevelaken 08:54Partial coverage0 min—
Thu 29 OctHoevelaken 08:56Partial coverage0 min—
Tue 27 OctHoevelaken 08:54Partial coverage0 min—
Mon 26 OctHoevelaken 09:00Partial coverage0 min—
Wed 21 OctHoevelaken 08:54No data—
Tue 20 OctHoevelaken 08:540 min—
Fri 9 OctHoevelaken 08:55Partial coverage+4 min+4 min
Thu 8 OctHoevelaken 08:55Partial coverage+2 min+2 min
Wed 7 OctHoevelaken 08:57Partial coverage+3 min+3 min
Tue 6 OctHoevelaken 08:55Partial coverage+1 min+1 min
Mon 5 OctHoevelaken 08:54No data—
Fri 2 OctHoevelaken 08:55No data—
Thu 1 OctHoevelaken 08:56No data—
Wed 30 SeptHoevelaken 08:59No data—
Tue 29 SeptHoevelaken 08:55No data—
Mon 28 SeptHoevelaken 08:54No data—
Thu 24 SeptHoevelaken 08:54No data—
Wed 23 SeptHoevelaken 08:55No data—