Train RRReis K 31325 Amersfoort Centraal – Ede-Wageningen

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

✓ Today’s run finished

Today, last fix heading to Ede Centrum at 11:54 No data

  1. Amersfoort Centraal11:10
  2. Hoevelaken11:15
  3. Barneveld Noord11:22
  4. Barneveld Zuid11:29
  5. Lunteren11:34
  6. Ede Centrum11:41
  7. Ede-Wageningen11:46

Next service: tomorrow 11:10 from Amersfoort Centraal · Fri 6 Nov

Next departure 11:10 tomorrow · Amersfoort Centraal
On-time · 30 days
77%
10/13 runs under 3 min
RT coverage: 1 full · 12 partial · 17 no data
On-time · 90 days
79%
11/14 runs under 3 min
RT coverage: 1 full · 13 partial · 75 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Wed 7 Oct Max en route +12 min · last fix heading to Amersfoort Centraal +12 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Ede Centrum +5 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Ede Centrum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 11
  • 3–10 min 14% · 2
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 67% W n=3
  • — T n=0
  • 100% F n=1
  • 100% S n=3
  • 33% S n=3

Stops and timetable

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

Last 90 days, 14 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
11:10on time +1 min
11:15— —
11:22— —
11:26 / 11:27— —
11:29— —
11:34 / 11:35— —
11:41— —
11: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
Thu 5 NovEde Centrum 11:54No data—
Wed 4 NovEde Centrum 11:58Partial coverage+2 min+3 min
Tue 3 NovEde Centrum 11:59No data—
Mon 2 NovEde Centrum 11:54No data—
Sun 1 NovEde Centrum 11:59Partial coverage+5 min+5 min
Sat 31 OctEde Centrum 11:56Partial coverage0 min—
Fri 30 OctEde Centrum 11:57No data—
Thu 29 OctEde Centrum 11:57No data—
Wed 28 OctEde Centrum 11:57Partial coverage0 min—
Tue 27 OctEde Centrum 11:56Partial coverage0 min—
Mon 26 OctEde Centrum 11:57No data—
Sun 25 OctEde Centrum 11:57No data—
Sat 24 OctEde Centrum 11:56Partial coverage+1 min—
Fri 23 OctEde Centrum 11:57No data—
Thu 22 OctEde Centrum 11:58No data—
Wed 21 OctEde Centrum 11:56No data—
Tue 20 OctEde Centrum 11:58Partial coverage0 min—
Mon 19 OctEde Centrum 11:55Partial coverage0 min—
Sun 18 OctEde Centrum 11:550 min—
Sat 17 OctEde Centrum 11:56No data—
Fri 16 OctEde Centrum 11:52No data—
Thu 15 OctEde Centrum 11:54No data—
Wed 14 OctEde Centrum 11:53No data—
Tue 13 OctEde Centrum 11:52No data—
Mon 12 OctEde Centrum 11:53No data—
Sun 11 OctEde Centrum 12:00Partial coverage+4 min+4 min
Sat 10 OctEde Centrum 11:56Partial coverage+1 min—
Fri 9 OctEde Centrum 11:57Partial coverage+1 min+2 min
Thu 8 OctEde Centrum 11:55No data—
Wed 7 OctAmersfoort Centraal 12:01Partial coverage+12 min+12 min