Train RRReis K 31412 Barneveld Zuid – Amersfoort Centraal

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 07:54 from Barneveld Zuid · Mon 9 Nov

Next departure 07:54 tomorrow · Barneveld Zuid
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 7 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 31 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: 0 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

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=4
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 10 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
07:54on time +1 min
07:56 / 07:59— —
08:02— —
08:09— —
08: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
Fri 6 NovHoevelaken 08:24No data—
Thu 5 NovHoevelaken 08:24No data—
Wed 4 NovHoevelaken 08:24Partial coverage0 min—
Tue 3 NovHoevelaken 08:29Partial coverage0 min—
Mon 2 NovHoevelaken 08:27No data—
Fri 30 OctHoevelaken 08:24No data—
Thu 29 OctHoevelaken 08:24No data—
Wed 28 OctHoevelaken 08:26Partial coverage0 min—
Tue 27 OctHoevelaken 08:24Partial coverage0 min—
Mon 26 OctHoevelaken 08:24Partial coverage0 min—
Thu 22 OctHoevelaken 08:23No data—
Wed 21 OctHoevelaken 08:25No data—
Tue 20 OctHoevelaken 08:24Partial coverage0 min—
Fri 9 OctHoevelaken 08:25Partial coverage+2 min+2 min
Thu 8 OctHoevelaken 08:25Partial coverage+2 min+2 min
Wed 7 OctHoevelaken 08:24Partial coverage+1 min—
Tue 6 OctHoevelaken 08:25Partial coverage+2 min+2 min
Mon 5 OctHoevelaken 08:26No data—
Fri 2 OctHoevelaken 08:24No data—
Thu 1 OctHoevelaken 08:27No data—
Wed 30 SeptHoevelaken 08:24No data—
Tue 29 SeptHoevelaken 08:23No data—
Mon 28 SeptHoevelaken 08:23No data—
Fri 25 SeptHoevelaken 08:24No data—
Thu 24 SeptHoevelaken 08:23No data—
Wed 23 SeptHoevelaken 08:24No data—
Tue 22 SeptHoevelaken 08:25No data—
Mon 21 SeptHoevelaken 08:23No data—
Fri 18 SeptHoevelaken 08:23No data—
Wed 16 SeptHoevelaken 08:25No data—