Train NS 7526 Arnhem Centraal – Ede-Wageningen

Arnhem Centraal 08:34 → Ede-Wageningen 08:48 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 08:57 0 min

  1. Arnhem Centraal08:34
  2. Oosterbeek08:38
  3. Wolfheze08:43
  4. Ede-Wageningen08:48

Next service: tomorrow 08:34 from Arnhem Centraal · Fri 20 Nov

Next departure 08:34 tomorrow · Arnhem Centraal
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 2 full · 10 partial · 2 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 2 full · 17 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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 11 Nov Max en route +6 min · last fix heading to Wolfheze +6 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Wolfheze +4 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 89% · 17
  • 3–10 min 11% · 2
  • 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
  • 100% T n=5
  • 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, 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
08:34on time on time
08:38— —
08:43— —
08: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
Thu 19 NovWolfheze 08:57Partial coverage0 min+3 min
Wed 18 NovWolfheze 08:57Partial coverage+1 min—
Tue 17 NovWolfheze 08:58Partial coverage+1 min+1 min
Mon 16 NovWolfheze 08:57Partial coverage0 min—
Fri 13 NovWolfheze 08:57Partial coverage0 min—
Thu 12 NovWolfheze 08:57Partial coverage+1 min—
Wed 11 NovWolfheze 09:03Partial coverage+6 min+6 min
Tue 10 NovWolfheze 08:59Partial coverage+4 min+4 min
Mon 9 NovWolfheze 08:57Partial coverage0 min—
Fri 6 NovWolfheze 08:57No data—
Thu 5 NovWolfheze 08:58Partial coverage0 min—
Wed 4 NovWolfheze 08:58+3 min+3 min
Tue 3 NovWolfheze 08:59No data—
Mon 2 NovWolfheze 08:570 min—
Mon 19 OctWolfheze 08:57Partial coverage0 min—
Fri 16 OctWolfheze 08:57No data—
Thu 15 OctWolfheze 08:57Partial coverage0 min—
Wed 14 OctWolfheze 08:57No data—
Tue 13 OctWolfheze 08:57Partial coverage0 min—
Mon 12 OctWolfheze 08:59No data—
Fri 9 OctWolfheze 08:58Partial coverage+1 min+2 min
Thu 8 OctWolfheze 08:59Partial coverage+3 min+3 min
Wed 7 OctWolfheze 08:57Partial coverage0 min—
Tue 6 OctWolfheze 08:57Partial coverage0 min—
Mon 5 OctWolfheze 08:57No data—
Fri 2 OctWolfheze 08:57No data—
Thu 1 OctWolfheze 08:57No data—
Wed 30 SeptWolfheze 08:59No data—
Tue 29 SeptWolfheze 09:00No data—
Mon 28 SeptWolfheze 08:57No data—