Train RRReis K 31444 Barneveld Zuid – Amersfoort Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:54 from Barneveld Zuid · Fri 6 Nov

Next departure 15:54 today · Barneveld Zuid
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 7 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 34 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: +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=2
  • 100% T n=4
  • 100% W n=1
  • 100% T n=2
  • 100% F n=1
  • 100% S n=1
  • — 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
15:54on time +1 min
15:56 / 15:59— —
16:02— —
16:09— —
16: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
Thu 5 NovHoevelaken 16:25No data—
Wed 4 NovHoevelaken 16:23No data—
Tue 3 NovHoevelaken 16:24Partial coverage0 min—
Mon 2 NovHoevelaken 16:24Partial coverage0 min—
Sat 31 OctHoevelaken 16:25Partial coverage+2 min+2 min
Fri 30 OctHoevelaken 16:24No data—
Thu 29 OctHoevelaken 16:23Partial coverage0 min—
Wed 28 OctHoevelaken 16:24Partial coverage0 min—
Tue 27 OctHoevelaken 16:27Partial coverage0 min—
Mon 26 OctHoevelaken 16:24No data—
Sat 24 OctHoevelaken 16:23No data—
Wed 21 OctHoevelaken 16:28No data—
Tue 20 OctHoevelaken 16:23Partial coverage0 min—
Sat 10 OctHoevelaken 16:23No data—
Fri 9 OctHoevelaken 16:24Partial coverage+1 min—
Thu 8 OctHoevelaken 16:25Partial coverage+1 min+1 min
Wed 7 OctHoevelaken 16:23No data—
Tue 6 OctHoevelaken 16:25Partial coverage+2 min+2 min
Mon 5 OctHoevelaken 16:24Partial coverage+1 min—
Sat 3 OctHoevelaken 16:23No data—
Fri 2 OctHoevelaken 16:23No data—
Thu 1 OctHoevelaken 16:23No data—
Wed 30 SeptHoevelaken 16:23No data—
Tue 29 SeptHoevelaken 16:24No data—
Mon 28 SeptHoevelaken 16:23No data—
Sat 26 SeptHoevelaken 16:25No data—
Fri 25 SeptHoevelaken 16:23No data—
Thu 24 SeptHoevelaken 16:23No data—
Wed 23 SeptHoevelaken 16:23No data—
Tue 22 SeptHoevelaken 16:23No data—