Train RRReis K 31406 Barneveld Zuid – Amersfoort Centraal

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

✓ Today’s run finished

Today, last fix heading to Hoevelaken at 06:54 +1 min

  1. Barneveld Zuid06:24
  2. Barneveld Centrum06:26
  3. Barneveld Noord06:32
  4. Hoevelaken06:39
  5. Amersfoort Centraal06:45

Next service: tomorrow 06:24 from Barneveld Zuid · Wed 18 Nov

Next departure 06:24 tomorrow · Barneveld Zuid
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 0 full · 14 partial · 4 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 0 full · 18 partial · 24 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +8 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 +13 min · last fix heading to Hoevelaken +13 min
  • Wed 4 Nov Max en route +9 min · last fix heading to Hoevelaken +9 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Hoevelaken +4 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Hoevelaken +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 17% · 3
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 83% T n=6
  • 80% W n=5
  • 100% 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, 18 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:24on time +1 min
06:26 / 06:29— —
06:32— —
06:39— —
06: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 06:54Partial coverage+1 min+1 min
Mon 16 NovHoevelaken 06:54Partial coverage0 min—
Fri 13 NovHoevelaken 06:54Partial coverage+3 min+3 min
Thu 12 NovHoevelaken 06:54Partial coverage+1 min+1 min
Wed 11 NovHoevelaken 06:54Partial coverage0 min—
Tue 10 NovHoevelaken 06:59Partial coverage+13 min+13 min
Mon 9 NovHoevelaken 06:53No data—
Fri 6 NovHoevelaken 06:54No data—
Thu 5 NovHoevelaken 06:59No data—
Wed 4 NovHoevelaken 06:59Partial coverage+9 min+9 min
Tue 3 NovHoevelaken 06:54Partial coverage+2 min+2 min
Mon 2 NovHoevelaken 06:54No data—
Thu 29 OctHoevelaken 06:54Partial coverage+1 min—
Wed 28 OctHoevelaken 06:53Partial coverage0 min—
Tue 27 OctHoevelaken 06:54Partial coverage0 min+1 min
Mon 26 OctHoevelaken 06:57Partial coverage+4 min+4 min
Wed 21 OctHoevelaken 06:55Partial coverage+1 min+1 min
Tue 20 OctHoevelaken 06:54Partial coverage0 min—
Fri 9 OctHoevelaken 06:54Partial coverage+1 min+1 min
Thu 8 OctHoevelaken 06:54Partial coverage+1 min—
Wed 7 OctHoevelaken 06:55Partial coverage+1 min+1 min
Tue 6 OctHoevelaken 06:55Partial coverage+1 min+1 min
Mon 5 OctHoevelaken 06:55No data—
Fri 2 OctHoevelaken 06:53No data—
Thu 1 OctHoevelaken 06:53No data—
Wed 30 SeptHoevelaken 06:56No data—
Tue 29 SeptHoevelaken 06:53No data—
Mon 28 SeptHoevelaken 06:54No data—
Fri 25 SeptHoevelaken 06:53No data—
Thu 24 SeptHoevelaken 06:53No data—