Train RRReis K 31342 Ede-Wageningen – Amersfoort Centraal

Ede-Wageningen 15:53 → Amersfoort Centraal 16:30 Daily 0 h 37 min · 8 stops RRReis K

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:53 from Ede-Wageningen · Fri 6 Nov

Next departure 15:53 today · Ede-Wageningen
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 16 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 1 full · 15 partial · 72 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 12 Oct Max en route +5 min · last fix heading to Barneveld Noord +5 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Hoevelaken +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 100% S n=3
  • 100% S n=1

Stops and timetable

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

Last 90 days, 16 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
15:53on time on time
15:57— —
16:03 / 16:04— —
16:09— —
16:12 / 16:14— —
16:17— —
16:24— —
16:30— —

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 5 NovHoevelaken 16:39No data—
Wed 4 NovHoevelaken 16:39Partial coverage0 min—
Tue 3 NovHoevelaken 16:38Partial coverage0 min—
Mon 2 NovHoevelaken 16:39Partial coverage0 min—
Sun 1 NovHoevelaken 16:38No data—
Sat 31 OctHoevelaken 16:40Partial coverage+1 min+3 min
Fri 30 OctHoevelaken 16:39No data—
Thu 29 OctHoevelaken 16:38Partial coverage0 min—
Wed 28 OctHoevelaken 16:38Partial coverage0 min—
Tue 27 OctHoevelaken 16:48No data—
Mon 26 OctHoevelaken 16:41No data—
Sun 25 OctHoevelaken 16:39No data—
Sat 24 OctHoevelaken 16:38Partial coverage0 min—
Fri 23 OctHoevelaken 16:42No data—
Thu 22 OctHoevelaken 16:39No data—
Wed 21 OctHoevelaken 16:44No data—
Tue 20 OctHoevelaken 16:38No data—
Mon 19 OctHoevelaken 16:40Partial coverage0 min—
Sun 18 OctBarneveld Zuid 16:23No data—
Sat 17 OctBarneveld Zuid 16:24No data—
Fri 16 OctBarneveld Noord 16:38No data—
Thu 15 OctBarneveld Noord 16:35No data—
Wed 14 OctBarneveld Noord 16:34No data—
Tue 13 OctBarneveld Noord 16:37No data—
Mon 12 OctBarneveld Noord 16:38+5 min+5 min
Sun 11 OctHoevelaken 16:39Partial coverage+1 min—
Sat 10 OctHoevelaken 16:41Partial coverage+3 min+3 min
Fri 9 OctHoevelaken 16:39Partial coverage+1 min+1 min
Thu 8 OctHoevelaken 16:41Partial coverage+2 min+3 min
Wed 7 OctHoevelaken 16:39Partial coverage0 min—