Train RRReis K 31319 Amersfoort Centraal – Ede-Wageningen

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

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 09:40 from Amersfoort Centraal · Thu 5 Nov

Next departure 09: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%
15/15 runs under 3 min
RT coverage: 2 full · 13 partial · 73 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
09:40on time on time
09:45— —
09:52— —
09:56 / 09:57— —
09:59— —
10:04 / 10:05— —
10:11— —
10: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
Wed 4 NovEde Centrum 10:28Partial coverage+2 min+3 min
Tue 3 NovEde Centrum 10:24No data—
Mon 2 NovEde Centrum 10:49No data—
Sun 1 NovEde Centrum 10:26Partial coverage0 min—
Sat 31 OctEde Centrum 10:26Partial coverage+1 min—
Fri 30 OctEde Centrum 10:26No data—
Thu 29 OctEde Centrum 10:29No data—
Wed 28 OctEde Centrum 10:27Partial coverage0 min—
Tue 27 OctEde Centrum 10:25Partial coverage0 min—
Mon 26 OctEde Centrum 10:26No data—
Sun 25 OctEde Centrum 10:27No data—
Sat 24 OctEde Centrum 10:26Partial coverage0 min+1 min
Fri 23 OctEde Centrum 10:26No data—
Thu 22 OctEde Centrum 10:28No data—
Wed 21 OctEde Centrum 10:28No data—
Tue 20 OctEde Centrum 10:27Partial coverage0 min—
Mon 19 OctEde Centrum 10:26Partial coverage0 min—
Sun 18 OctEde Centrum 10:26+1 min—
Sat 17 OctEde Centrum 10:27+1 min+2 min
Fri 16 OctEde Centrum 10:22No data—
Thu 15 OctEde Centrum 10:23No data—
Wed 14 OctEde Centrum 10:22No data—
Tue 13 OctEde Centrum 10:22No data—
Mon 12 OctEde Centrum 10:22No data—
Sun 11 OctEde Centrum 10:25No data—
Sat 10 OctEde Centrum 10:28Partial coverage+2 min+3 min
Fri 9 OctEde Centrum 10:26Partial coverage0 min+1 min
Thu 8 OctEde Centrum 10:27Partial coverage+1 min+2 min
Wed 7 OctEde Centrum 10:25Partial coverage0 min—
Tue 6 OctEde Centrum 10:26Partial coverage+1 min—