Train RRReis K 31321 Amersfoort Centraal – Ede-Wageningen

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

Running now · updated 10:55

Position estimated from the timetable

Heading to Ede-Wageningen 0 min

Estimated arrival at Ede-Wageningen 10:46

  1. Amersfoort Centraal10:10
  2. Hoevelaken10:15
  3. Barneveld Noord10:22
  4. Barneveld Zuid10:29
  5. Lunteren10:34
  6. Ede Centrum10:41
  7. Ede-Wageningen10:46

Today it is running no worse than usual: typical arrival delay is +1 min; 95% of the last 19 runs arrived on time.

On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 1 full · 18 partial · 11 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 2 full · 23 partial · 63 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

Worst days

  • Tue 10 Nov Max en route +7 min · last fix heading to Ede Centrum +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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:10on time on time
10:15— —
10:22— —
10:26 / 10:27— —
10:29— —
10:34 / 10:35— —
10:41— —
10:46— —

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 NovEde Centrum 10:54Partial coverage0 min+2 min
Sun 15 NovEde Centrum 10:58Partial coverage+2 min+3 min
Sat 14 NovEde Centrum 10:54Partial coverage+1 min—
Fri 13 NovEde Centrum 10:54Partial coverage0 min—
Thu 12 NovEde Centrum 10:54Partial coverage0 min—
Wed 11 NovEde Centrum 10:54Partial coverage0 min—
Tue 10 NovEde Centrum 11:03Partial coverage+6 min+7 min
Mon 9 NovEde Centrum 10:54Partial coverage+1 min—
Sun 8 NovEde Centrum 10:57Partial coverage+1 min+2 min
Sat 7 NovEde Centrum 10:54Partial coverage+1 min—
Fri 6 NovEde Centrum 10:58No data—
Thu 5 NovEde Centrum 10:54No data—
Wed 4 NovEde Centrum 10:54Partial coverage+1 min—
Tue 3 NovEde Centrum 10:59No data—
Mon 2 NovEde Centrum 10:54No data—
Sun 1 NovEde Centrum 10:57Partial coverage+1 min—
Sat 31 OctEde Centrum 10:57Partial coverage0 min+2 min
Fri 30 OctEde Centrum 10:56No data—
Thu 29 OctEde Centrum 10:56No data—
Wed 28 OctEde Centrum 10:55Partial coverage0 min—
Tue 27 OctEde Centrum 10:57Partial coverage0 min—
Mon 26 OctEde Centrum 10:58No data—
Sun 25 OctEde Centrum 10:56No data—
Sat 24 OctEde Centrum 10:56Partial coverage+1 min—
Fri 23 OctLunteren 10:49No data—
Thu 22 OctEde Centrum 11:12No data—
Wed 21 OctEde Centrum 10:55No data—
Tue 20 OctEde Centrum 10:56Partial coverage0 min—
Mon 19 OctEde Centrum 10:56Partial coverage0 min—
Sun 18 OctEde Centrum 10:57+1 min+2 min