Train NS 7517 Ede-Wageningen – Arnhem Centraal

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

It does not run today

Last recorded run: Friday 13 November +3 min

Next service: tomorrow 06:42 from Ede-Wageningen · Mon 16 Nov

Next departure 06:42 tomorrow · Ede-Wageningen
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 0 full · 10 partial · 1 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 1 full · 18 partial · 35 no data
Typical delay
+1min
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 Arnhem 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

  • Thu 8 Oct Max en route +6 min · last fix heading to Oosterbeek +6 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Oosterbeek +5 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Oosterbeek +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 16
  • 3–10 min 16% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 75% W n=4
  • 75% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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:42on time on time
06:48— —
06:52— —
06:56— —

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 13 NovOosterbeek 07:09Partial coverage+3 min+3 min
Thu 12 NovOosterbeek 07:07Partial coverage+1 min—
Wed 11 NovOosterbeek 07:08Partial coverage+2 min+2 min
Tue 10 NovOosterbeek 07:08Partial coverage+1 min+1 min
Mon 9 NovOosterbeek 07:07Partial coverage+1 min—
Fri 6 NovOosterbeek 07:09No data—
Thu 5 NovOosterbeek 07:19Partial coverage0 min—
Wed 4 NovOosterbeek 07:09Partial coverage+5 min+5 min
Tue 3 NovOosterbeek 07:09Partial coverage+5 min+5 min
Mon 2 NovOosterbeek 07:08Partial coverage0 min—
Mon 19 OctOosterbeek 07:07Partial coverage+1 min+1 min
Fri 16 OctOosterbeek 07:08Partial coverage0 min—
Thu 15 OctOosterbeek 07:07Partial coverage0 min—
Wed 14 OctOosterbeek 07:070 min—
Tue 13 OctOosterbeek 07:07Partial coverage+1 min—
Mon 12 OctOosterbeek 07:07Partial coverage0 min—
Fri 9 OctOosterbeek 07:08Partial coverage0 min—
Thu 8 OctOosterbeek 07:13Partial coverage+6 min+6 min
Wed 7 OctOosterbeek 07:07Partial coverage+1 min—
Tue 6 OctOosterbeek 07:08Partial coverage+2 min+2 min
Mon 5 OctOosterbeek 07:08No data—
Fri 2 OctOosterbeek 07:07No data—
Thu 1 OctOosterbeek 07:07No data—
Wed 30 SeptOosterbeek 07:07No data—
Tue 29 SeptOosterbeek 07:07No data—
Mon 28 SeptOosterbeek 07:07No data—
Fri 25 SeptOosterbeek 07:07No data—
Thu 24 SeptOosterbeek 07:08No data—
Wed 23 SeptOosterbeek 07:07No data—
Tue 22 SeptOosterbeek 07:07No data—