Train RRReis K 31428 Barneveld Zuid – Amersfoort Centraal

Barneveld Zuid 11:54 → Amersfoort Centraal 12: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 12:23 0 min

  1. Barneveld Zuid11:54
  2. Barneveld Centrum11:56
  3. Barneveld Noord12:02
  4. Hoevelaken12:09
  5. Amersfoort Centraal12:15

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

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

  • Mon 16 Nov Max en route +6 min · last fix heading to Hoevelaken +6 min

Distribution · 90 days

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

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

On-time by weekday

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