Train RRReis K 31416 Barneveld Zuid – Amersfoort Centraal

Barneveld Zuid 08:54 → Amersfoort Centraal 09:15 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:24 0 min

  1. Barneveld Zuid08:54
  2. Barneveld Centrum08:56
  3. Barneveld Noord09:02
  4. Hoevelaken09:10
  5. Amersfoort Centraal09:15

Next service: tomorrow 08:54 from Barneveld Zuid · Thu 19 Nov

Next departure 08:54 tomorrow · Barneveld Zuid
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 9 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 0 full · 19 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Fri 9 Oct Max en route +3 min · last fix heading to Hoevelaken +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=3
  • 50% F n=2
  • 100% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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
08:54on time +1 min
08:56 / 08:59— —
09:02 / 09:03— —
09:10— —
09: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
Wed 18 NovHoevelaken 09:24Partial coverage0 min—
Tue 17 NovHoevelaken 09:24Partial coverage+1 min+1 min
Mon 16 NovHoevelaken 09:27Partial coverage+3 min+3 min
Sat 14 NovHoevelaken 09:24Partial coverage0 min—
Fri 13 NovHoevelaken 09:24Partial coverage0 min—
Thu 12 NovHoevelaken 09:24Partial coverage0 min—
Wed 11 NovHoevelaken 09:24Partial coverage+2 min+4 min
Tue 10 NovHoevelaken 09:24Partial coverage+2 min+2 min
Mon 9 NovHoevelaken 09:24Partial coverage+1 min+1 min
Sat 7 NovHoevelaken 09:24Partial coverage0 min—
Fri 6 NovHoevelaken 09:24No data—
Thu 5 NovHoevelaken 09:24No data—
Wed 4 NovHoevelaken 09:24No data—
Tue 3 NovHoevelaken 09:24Partial coverage0 min—
Mon 2 NovHoevelaken 09:24Partial coverage0 min—
Sat 31 OctHoevelaken 09:24No data—
Fri 30 OctHoevelaken 09:25No data—
Thu 29 OctHoevelaken 09:24Partial coverage0 min—
Wed 28 OctHoevelaken 09:24Partial coverage0 min—
Mon 26 OctHoevelaken 09:24No data—
Sat 24 OctHoevelaken 09:24No data—
Thu 22 OctHoevelaken 09:24No data—
Wed 21 OctHoevelaken 09:24No data—
Tue 20 OctHoevelaken 09:24Partial coverage0 min—
Sat 10 OctHoevelaken 09:24No data—
Fri 9 OctHoevelaken 09:28Partial coverage+3 min+3 min
Thu 8 OctHoevelaken 09:24Partial coverage+1 min+1 min
Wed 7 OctHoevelaken 09:26Partial coverage+2 min+2 min
Tue 6 OctHoevelaken 09:25Partial coverage+1 min+1 min
Mon 5 OctHoevelaken 09:25No data—