Train RRReis K 31351 Amersfoort Centraal – Ede-Wageningen

Amersfoort Centraal 17:40 → Ede-Wageningen 18:16 Daily 0 h 36 min · 8 stops RRReis K

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:40 from Amersfoort Centraal · Fri 6 Nov

Next departure 17:40 today · Amersfoort Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 15 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 2 full · 14 partial · 72 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Ede-Wageningen, 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

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

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

On-time by weekday

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

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
17:40on time on time
17:45— —
17:52— —
17:56 / 17:57— —
17:59— —
18:04 / 18:05— —
18:11— —
18:16— —

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 NovEde Centrum 18:24No data—
Wed 4 NovEde Centrum 18:24No data—
Tue 3 NovEde Centrum 18:24Partial coverage0 min—
Mon 2 NovLunteren 18:19No data—
Sun 1 NovEde Centrum 18:27Partial coverage+1 min+2 min
Sat 31 OctEde Centrum 18:26Partial coverage+1 min—
Fri 30 OctEde Centrum 18:25No data—
Thu 29 OctBarneveld Zuid 18:13No data—
Wed 28 OctEde Centrum 18:25Partial coverage0 min—
Tue 27 OctLunteren 18:19No data—
Mon 26 OctLunteren 18:19Partial coverage+1 min—
Sun 25 OctEde Centrum 18:25No data—
Sat 24 OctEde Centrum 18:27Partial coverage0 min—
Fri 23 OctEde Centrum 18:25No data—
Thu 22 OctEde Centrum 18:25No data—
Wed 21 OctEde Centrum 18:25No data—
Tue 20 OctEde Centrum 18:25Partial coverage0 min—
Mon 19 OctEde Centrum 18:25Partial coverage0 min—
Sun 18 OctEde Centrum 18:260 min—
Sat 17 OctEde Centrum 18:26No data—
Fri 16 OctEde Centrum 18:24No data—
Thu 15 OctEde Centrum 18:21No data—
Wed 14 OctEde Centrum 18:22No data—
Tue 13 OctEde Centrum 18:21No data—
Mon 12 OctEde Centrum 18:210 min—
Sun 11 OctEde Centrum 18:27Partial coverage0 min+2 min
Sat 10 OctEde Centrum 18:26Partial coverage0 min—
Fri 9 OctEde Centrum 18:23Partial coverage0 min+1 min
Thu 8 OctBarneveld Zuid 18:13Partial coverage+2 min+2 min
Wed 7 OctLunteren 18:19No data—