Train RRReis K 31422 Barneveld Zuid – Amersfoort Centraal

Barneveld Zuid 10:24 → Amersfoort Centraal 10:45 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 +2 min

Next service: today 10:24 from Barneveld Zuid · Wed 18 Nov

Next departure 10:24 today · Barneveld Zuid
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 0 full · 12 partial · 6 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 0 full · 15 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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
  • Sat 14 Nov Max en route +4 min · last fix heading to Hoevelaken +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 13
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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