Train RRReis K 31404 Barneveld Zuid – Amersfoort Centraal

Barneveld Zuid 05:54 → Amersfoort Centraal 06: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 06:24 +2 min

  1. Barneveld Zuid05:54
  2. Barneveld Centrum05:56
  3. Barneveld Noord06:02
  4. Hoevelaken06:09
  5. Amersfoort Centraal06:15

Next service: tomorrow 05:54 from Barneveld Zuid · Fri 20 Nov

Next departure 05:54 tomorrow · Barneveld Zuid
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 10 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 36 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: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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