Train RRReis K 31320 Ede-Wageningen – Amersfoort Centraal

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

Running now · updated 10:55

Position estimated from the timetable

Heading to Amersfoort Centraal +1 min

Estimated arrival at Amersfoort Centraal 11:01 · 85 km/h

  1. Ede-Wageningen10:23
  2. Ede Centrum10:27
  3. Lunteren10:33
  4. Barneveld Centrum10:42
  5. Barneveld Noord10:47
  6. Hoevelaken10:54
  7. Amersfoort Centraal11:00

Today it is running worse than usual: typical arrival delay is 0 min; 84% of the last 19 runs arrived on time.

On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 1 full · 18 partial · 11 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 2 full · 22 partial · 65 no data
Typical delay
0min
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

  • Tue 10 Nov Max en route +7 min · last fix heading to Hoevelaken +7 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Hoevelaken +5 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Hoevelaken +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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 10Today
10:23on time on time
10:27— —
10:33 / 10:34— —
10:39— —
10:42 / 10:44— —
10:47— —
10:54— —
11: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
Mon 16 NovHoevelaken 10:54Partial coverage+1 min+10 min
Sun 15 NovHoevelaken 11:09Partial coverage+1 min+1 min
Sat 14 NovHoevelaken 11:09Partial coverage+1 min+1 min
Fri 13 NovHoevelaken 11:08Partial coverage0 min—
Thu 12 NovHoevelaken 11:09Partial coverage+3 min+3 min
Wed 11 NovHoevelaken 11:09Partial coverage+1 min+1 min
Tue 10 NovHoevelaken 11:14Partial coverage+7 min+7 min
Mon 9 NovHoevelaken 11:09Partial coverage0 min—
Sun 8 NovHoevelaken 11:08Partial coverage0 min—
Sat 7 NovHoevelaken 11:08Partial coverage0 min—
Fri 6 NovHoevelaken 11:09No data—
Thu 5 NovHoevelaken 11:08No data—
Wed 4 NovHoevelaken 11:13Partial coverage+5 min+5 min
Tue 3 NovHoevelaken 11:14No data—
Mon 2 NovHoevelaken 11:24No data—
Sun 1 NovHoevelaken 11:09Partial coverage0 min—
Sat 31 OctHoevelaken 11:09Partial coverage0 min—
Fri 30 OctHoevelaken 11:09No data—
Thu 29 OctHoevelaken 11:10No data—
Wed 28 OctHoevelaken 11:09Partial coverage0 min—
Tue 27 OctHoevelaken 11:08Partial coverage0 min—
Mon 26 OctHoevelaken 11:09No data—
Sun 25 OctHoevelaken 11:09No data—
Sat 24 OctHoevelaken 11:11Partial coverage+3 min+3 min
Fri 23 OctHoevelaken 11:09No data—
Thu 22 OctHoevelaken 11:12No data—
Wed 21 OctHoevelaken 11:09No data—
Tue 20 OctHoevelaken 11:11Partial coverage0 min—
Mon 19 OctHoevelaken 11:08Partial coverage0 min—
Sun 18 OctBarneveld Zuid 10:55+1 min+1 min