Train RRReis K 31420 Barneveld Zuid – Amersfoort Centraal

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

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 09:54 from Barneveld Zuid · Thu 19 Nov

Next departure 09:54 today · Barneveld Zuid
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 9 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 0 full · 19 partial · 35 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

Worst days

  • Tue 10 Nov Max en route +6 min · last fix heading to Hoevelaken +6 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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 80% T n=5
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • — 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
09:54on time on time
09:56 / 09:59— —
10:02— —
10:09— —
10: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
Wed 18 NovHoevelaken 10:24Partial coverage+1 min—
Tue 17 NovHoevelaken 10:24Partial coverage0 min—
Mon 16 NovHoevelaken 10:23No data—
Sat 14 NovHoevelaken 10:23Partial coverage0 min—
Fri 13 NovHoevelaken 10:24Partial coverage+1 min—
Thu 12 NovHoevelaken 10:24Partial coverage0 min—
Wed 11 NovHoevelaken 10:24Partial coverage0 min—
Tue 10 NovHoevelaken 10:29Partial coverage+6 min+6 min
Mon 9 NovHoevelaken 10:24No data—
Sat 7 NovHoevelaken 10:24Partial coverage+1 min—
Fri 6 NovHoevelaken 10:27No data—
Thu 5 NovHoevelaken 10:24No data—
Wed 4 NovHoevelaken 10:23No data—
Tue 3 NovHoevelaken 10:24Partial coverage0 min—
Mon 2 NovHoevelaken 10:34Partial coverage0 min—
Sat 31 OctHoevelaken 10:23Partial coverage0 min—
Fri 30 OctHoevelaken 10:23No data—
Thu 29 OctHoevelaken 10:23Partial coverage0 min—
Wed 28 OctHoevelaken 10:23Partial coverage0 min—
Sat 24 OctHoevelaken 10:24No data—
Thu 22 OctHoevelaken 10:24No data—
Wed 21 OctHoevelaken 10:25No data—
Tue 20 OctHoevelaken 10:23Partial coverage0 min—
Sat 10 OctHoevelaken 10:24Partial coverage0 min—
Fri 9 OctHoevelaken 10:25Partial coverage+1 min+1 min
Thu 8 OctHoevelaken 10:24Partial coverage0 min—
Wed 7 OctHoevelaken 10:24Partial coverage0 min—
Tue 6 OctHoevelaken 10:24Partial coverage+1 min—
Mon 5 OctHoevelaken 10:25No data—
Sat 3 OctHoevelaken 10:23No data—