Train RRReis K 31448 Barneveld Zuid – Amersfoort Centraal

Barneveld Zuid 16:54 → Amersfoort Centraal 17:15 Mon, Tue, Wed, Thu, Fri, Sat 0 h 21 min · 5 stops RRReis K

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 16:54 from Barneveld Zuid · Wed 18 Nov

Next departure 16:54 today · Barneveld Zuid
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 10 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
16:54on time on time
16:56 / 16:59— —
17:02— —
17:09— —
17:15— —

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
Tue 17 NovHoevelaken 17:23Partial coverage+1 min+1 min
Mon 16 NovHoevelaken 17:24Partial coverage+1 min+1 min
Sat 14 NovHoevelaken 17:23Partial coverage0 min—
Fri 13 NovHoevelaken 17:23Partial coverage0 min—
Thu 12 NovHoevelaken 17:23Partial coverage0 min—
Wed 11 NovHoevelaken 17:23No data—
Tue 10 NovHoevelaken 17:23Partial coverage0 min—
Mon 9 NovHoevelaken 17:23Partial coverage+2 min+2 min
Sat 7 NovHoevelaken 17:23No data—
Fri 6 NovHoevelaken 17:24Partial coverage+1 min—
Thu 5 NovHoevelaken 17:23No data—
Wed 4 NovHoevelaken 17:23Partial coverage0 min—
Tue 3 NovHoevelaken 17:23No data—
Mon 2 NovHoevelaken 17:23No data—
Sat 31 OctHoevelaken 17:24Partial coverage0 min—
Fri 30 OctHoevelaken 17:25No data—
Thu 29 OctHoevelaken 17:23No data—
Wed 28 OctHoevelaken 17:23Partial coverage0 min—
Tue 27 OctHoevelaken 17:23Partial coverage0 min—
Mon 26 OctHoevelaken 17:23No data—
Sat 24 OctHoevelaken 17:24No data—
Wed 21 OctHoevelaken 17:25No data—
Tue 20 OctHoevelaken 17:24Partial coverage0 min—
Sat 10 OctHoevelaken 17:23No data—
Fri 9 OctHoevelaken 17:24Partial coverage0 min—
Thu 8 OctHoevelaken 17:23Partial coverage0 min—
Wed 7 OctHoevelaken 17:23Partial coverage+1 min—
Tue 6 OctHoevelaken 17:23No data—
Mon 5 OctHoevelaken 17:22Partial coverage0 min—
Sat 3 OctHoevelaken 17:23No data—