Train NS 7518 Arnhem Centraal – Ede-Wageningen

Arnhem Centraal 06:34 → Ede-Wageningen 06:48 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:34 from Arnhem Centraal · Mon 9 Nov

Next departure 06:34 Monday · Arnhem Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 3 full · 8 partial · 1 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 3 full · 11 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 8 Oct Max en route +20 min · last fix heading to Wolfheze +18 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 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
06:34on time on time
06:38— —
06:42— —
06:48— —

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
Fri 6 NovWolfheze 06:57No data—
Thu 5 NovWolfheze 07:02Partial coverage0 min—
Wed 4 NovWolfheze 06:58+2 min+2 min
Tue 3 NovWolfheze 06:57+1 min+1 min
Mon 2 NovWolfheze 06:570 min—
Mon 19 OctWolfheze 06:57Partial coverage0 min—
Fri 16 OctWolfheze 06:58Partial coverage+2 min+2 min
Thu 15 OctWolfheze 06:57Partial coverage0 min—
Wed 14 OctWolfheze 06:57Partial coverage+1 min—
Tue 13 OctWolfheze 06:57Partial coverage0 min—
Mon 12 OctWolfheze 06:58Partial coverage+1 min+2 min
Fri 9 OctWolfheze 06:57Partial coverage+1 min—
Thu 8 OctWolfheze 07:15Partial coverage+18 min+20 min
Wed 7 OctWolfheze 06:57Partial coverage+1 min—
Tue 6 OctWolfheze 06:57Partial coverage+1 min—
Mon 5 OctWolfheze 06:58No data—
Fri 2 OctWolfheze 06:57No data—
Thu 1 OctWolfheze 06:57No data—
Wed 30 SeptWolfheze 06:56No data—
Tue 29 SeptWolfheze 06:57No data—
Mon 28 SeptWolfheze 06:56No data—
Fri 25 SeptWolfheze 06:56No data—
Thu 24 SeptWolfheze 06:57No data—
Wed 23 SeptWolfheze 07:09No data—
Tue 22 SeptWolfheze 06:57No data—
Mon 21 SeptWolfheze 06:57No data—
Fri 18 SeptWolfheze 06:57No data—
Thu 17 SeptWolfheze 06:57No data—
Wed 16 SeptWolfheze 06:57No data—
Tue 15 SeptWolfheze 06:57No data—