Train RRReis K 31347 Amersfoort Centraal – Ede-Wageningen

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

✓ Today’s run finished

Today, last fix heading to Ede Centrum at 17:24 +1 min

  1. Amersfoort Centraal16:40
  2. Hoevelaken16:45
  3. Barneveld Noord16:52
  4. Barneveld Zuid16:59
  5. Lunteren17:04
  6. Ede Centrum17:11
  7. Ede-Wageningen17:16

Next service: tomorrow 16:40 from Amersfoort Centraal · Sun 8 Nov

Next departure 16:40 tomorrow · Amersfoort Centraal
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 2 full · 11 partial · 17 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 2 full · 14 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

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=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=4
  • 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
16:40on time +1 min
16:45— —
16:52— —
16:56 / 16:57— —
16:59— —
17:04 / 17:05— —
17:11— —
17: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
Sat 7 NovEde Centrum 17:24Partial coverage+1 min—
Fri 6 NovEde Centrum 17:24No data—
Thu 5 NovEde Centrum 17:24No data—
Wed 4 NovEde Centrum 17:24No data—
Tue 3 NovEde Centrum 17:24No data—
Mon 2 NovEde Centrum 17:24No data—
Sun 1 NovEde Centrum 17:27Partial coverage0 min+1 min
Sat 31 OctEde Centrum 17:26Partial coverage0 min+1 min
Fri 30 OctEde Centrum 17:26No data—
Thu 29 OctEde Centrum 17:25No data—
Wed 28 OctEde Centrum 17:25Partial coverage0 min—
Tue 27 OctEde Centrum 17:25Partial coverage0 min—
Mon 26 OctEde Centrum 17:25No data—
Sun 25 OctEde Centrum 17:31No data—
Sat 24 OctEde Centrum 17:26Partial coverage+1 min—
Fri 23 OctEde Centrum 17:27No data—
Thu 22 OctEde Centrum 17:26No data—
Wed 21 OctEde Centrum 17:28No data—
Tue 20 OctEde Centrum 17:29Partial coverage0 min—
Mon 19 OctEde Centrum 17:26Partial coverage0 min—
Sun 18 OctEde Centrum 17:270 min—
Sat 17 OctEde Centrum 17:27No data—
Fri 16 OctEde Centrum 17:25No data—
Thu 15 OctEde Centrum 17:17No data—
Wed 14 OctEde Centrum 17:22No data—
Tue 13 OctEde Centrum 17:23No data—
Mon 12 OctEde Centrum 17:220 min—
Sun 11 OctEde Centrum 17:26Partial coverage+1 min—
Sat 10 OctEde Centrum 17:27Partial coverage+1 min+2 min
Fri 9 OctEde Centrum 17:26Partial coverage0 min+1 min