Train RRReis K 31356 Ede-Wageningen – Amersfoort Centraal

Ede-Wageningen 19:23 → Amersfoort Centraal 20:00 Daily 0 h 37 min · 8 stops RRReis K

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 19:23 from Ede-Wageningen · Fri 6 Nov

Next departure 19:23 today · Ede-Wageningen
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 1 full · 5 partial · 5 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 1 full · 5 partial · 31 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 6
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=1
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 6 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
19:23on time +2 min
19:27— —
19:33 / 19:34— —
19:39— —
19:42 / 19:44— —
19:47— —
19:54— —
20:00— —

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
Sun 1 NovHoevelaken 20:08Partial coverage0 min—
Sat 31 OctHoevelaken 20:09Partial coverage+1 min—
Sun 25 OctHoevelaken 20:08No data—
Sat 24 OctHoevelaken 20:12No data—
Fri 23 OctEde Centrum 19:41Partial coverage+2 min+2 min
Sun 18 OctBarneveld Zuid 19:56+2 min+3 min
Sat 17 OctBarneveld Zuid 19:55No data—
Fri 16 OctEde Centrum 19:38No data—
Wed 14 OctBarneveld Centrum 20:00No data—
Sun 11 OctHoevelaken 20:11Partial coverage+2 min+3 min
Sat 10 OctHoevelaken 20:09Partial coverage+2 min+2 min
Sun 4 OctHoevelaken 20:08No data—
Sat 3 OctHoevelaken 20:09No data—
Sun 27 SeptHoevelaken 20:08No data—
Sat 26 SeptHoevelaken 20:08No data—
Sun 20 SeptHoevelaken 20:08No data—
Sat 19 SeptHoevelaken 20:09No data—
Sun 13 SeptBarneveld Zuid 19:35No data—
Sat 12 SeptBarneveld Zuid 19:35No data—
Sun 6 SeptHoevelaken 20:10No data—
Sat 5 SeptHoevelaken 20:09No data—
Sun 30 AugHoevelaken 20:10No data—
Sat 29 AugHoevelaken 20:10No data—
Fri 28 AugEde Centrum 19:41No data—
Sun 23 AugHoevelaken 20:08No data—
Sat 22 AugHoevelaken 20:08No data—
Fri 21 AugHoevelaken 20:04No data—
Wed 19 AugEde Centrum 19:41No data—
Mon 17 AugBarneveld Centrum 19:58No data—
Sun 16 AugHoevelaken 20:08No data—