Train RRReis K 31418 Barneveld Zuid – Amersfoort Centraal

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

✓ Today’s run finished

Today, last fix heading to Hoevelaken at 09:54 +3 min

  1. Barneveld Zuid09:24
  2. Barneveld Centrum09:26
  3. Barneveld Noord09:32
  4. Hoevelaken09:39
  5. Amersfoort Centraal09:45

Next service: tomorrow 09:24 from Barneveld Zuid · Thu 19 Nov

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

  • Mon 16 Nov Max en route +10 min · last fix heading to Hoevelaken +10 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Hoevelaken +6 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Hoevelaken +3 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Hoevelaken +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 13
  • 3–10 min 18% · 3
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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