Train RRReis K 31408 Barneveld Zuid – Amersfoort Centraal

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

✓ Today’s run finished

Today, last fix heading to Hoevelaken at 07:24 No data

  1. Barneveld Zuid06:54
  2. Barneveld Centrum06:56
  3. Barneveld Noord07:02
  4. Hoevelaken07:09
  5. Amersfoort Centraal07:15

Next service: tomorrow 06:54 from Barneveld Zuid · Fri 6 Nov

Next departure 06:54 tomorrow · Barneveld Zuid
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 0 full · 9 partial · 5 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 0 full · 10 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Thu 8 Oct Max en route +4 min · last fix heading to Hoevelaken +4 min
  • Fri 30 Oct Max en route +3 min · last fix heading to Hoevelaken +3 min

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 80% · 8
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=2
  • 100% W n=3
  • 67% T n=3
  • 50% F n=2
  • — 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
06:54on time +1 min
06:56 / 06:59— —
07:02— —
07:09— —
07: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 07:24No data—
Wed 4 NovHoevelaken 07:24Partial coverage+2 min+2 min
Tue 3 NovHoevelaken 07:24No data—
Mon 2 NovHoevelaken 07:27No data—
Fri 30 OctHoevelaken 07:26Partial coverage+3 min+3 min
Thu 29 OctHoevelaken 07:24Partial coverage0 min—
Wed 28 OctHoevelaken 07:25Partial coverage+1 min+1 min
Mon 26 OctBarneveld Centrum 07:13Partial coverageNo data—
Thu 22 OctHoevelaken 07:24Partial coverage+1 min+1 min
Wed 21 OctHoevelaken 07:24Partial coverage+1 min—
Tue 20 OctHoevelaken 07:24Partial coverage0 min—
Fri 9 OctHoevelaken 07:24Partial coverage0 min—
Thu 8 OctHoevelaken 07:26Partial coverage+4 min+4 min
Wed 7 OctHoevelaken 07:23No data—
Tue 6 OctHoevelaken 07:25Partial coverage+2 min+2 min
Mon 5 OctHoevelaken 07:25No data—
Fri 2 OctHoevelaken 07:23No data—
Thu 1 OctHoevelaken 07:26No data—
Wed 30 SeptHoevelaken 07:23No data—
Tue 29 SeptHoevelaken 07:23No data—
Mon 28 SeptHoevelaken 07:24No data—
Fri 25 SeptHoevelaken 07:23No data—
Thu 24 SeptHoevelaken 07:25No data—
Wed 23 SeptHoevelaken 07:25No data—
Tue 22 SeptHoevelaken 07:24No data—
Mon 21 SeptHoevelaken 07:24No data—
Fri 18 SeptHoevelaken 07:24No data—
Wed 16 SeptHoevelaken 07:24No data—
Tue 15 SeptHoevelaken 07:23No data—
Mon 14 SeptHoevelaken 07:25No data—