Train RRReis K 31430 Barneveld Zuid – Amersfoort Centraal

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

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 12:24 from Barneveld Zuid · Mon 9 Nov

Next departure 12:24 tomorrow · Barneveld Zuid
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 4 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 24 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 11
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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
12:24on time +1 min
12:26 / 12:29— —
12:32— —
12:39— —
12: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
Sat 7 NovHoevelaken 12:54Partial coverage0 min—
Fri 6 NovHoevelaken 12:53No data—
Thu 5 NovHoevelaken 12:53No data—
Wed 4 NovHoevelaken 12:54Partial coverage+1 min+1 min
Sat 31 OctHoevelaken 12:54Partial coverage+1 min—
Tue 27 OctHoevelaken 12:53Partial coverage0 min—
Mon 26 OctHoevelaken 12:55No data—
Wed 21 OctHoevelaken 12:55No data—
Tue 20 OctHoevelaken 12:54Partial coverage0 min—
Sat 10 OctHoevelaken 12:54Partial coverage+1 min+1 min
Fri 9 OctHoevelaken 12:55Partial coverage+1 min+1 min
Thu 8 OctHoevelaken 12:55Partial coverage+2 min+2 min
Wed 7 OctHoevelaken 12:54Partial coverage0 min—
Tue 6 OctHoevelaken 12:55Partial coverage+1 min+1 min
Mon 5 OctHoevelaken 12:54Partial coverage+2 min+2 min
Sat 3 OctHoevelaken 12:54No data—
Fri 2 OctHoevelaken 12:54No data—
Thu 1 OctHoevelaken 12:54No data—
Wed 30 SeptHoevelaken 12:55No data—
Tue 29 SeptHoevelaken 12:55No data—
Mon 28 SeptHoevelaken 12:54No data—
Sat 26 SeptHoevelaken 12:53No data—
Wed 23 SeptHoevelaken 12:54No data—
Tue 22 SeptHoevelaken 12:53No data—
Sat 19 SeptHoevelaken 12:53No data—
Fri 11 SeptHoevelaken 12:55No data—
Thu 10 SeptHoevelaken 12:53No data—
Tue 8 SeptHoevelaken 12:54No data—
Mon 7 SeptHoevelaken 12:55No data—
Sat 5 SeptHoevelaken 12:54No data—