Train NS 7514 Arnhem Centraal – Ede-Wageningen

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

✓ Today’s run finished

Today, last fix heading to Wolfheze at 06:07 +2 min

  1. Arnhem Centraal05:43
  2. Oosterbeek05:47
  3. Wolfheze05:52
  4. Ede-Wageningen05:57

Next service: tomorrow 05:43 from Arnhem Centraal · Fri 6 Nov

Next departure 05:43 tomorrow · Arnhem Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 10 full · 3 partial · 0 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 11 full · 3 partial · 40 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

  • Tue 3 Nov Max en route +16 min · last fix heading to Wolfheze +16 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
  • 67% T n=3
  • 100% W n=3
  • 100% 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
05:43on time on time
05:47≈ on time ≈ +1 min
05:52≈ on time ≈ +1 min
05:57+1 min +2 min

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