Train NS 7528 Arnhem Centraal – Ede-Wageningen

Arnhem Centraal 09:05 → Ede-Wageningen 09:19 Daily 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 09:05 from Arnhem Centraal · Sun 15 Nov

Next departure 09:05 today · Arnhem Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 2 full · 11 partial · 4 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 8 full · 13 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 8 Nov Max en route +3 min · last fix heading to Wolfheze +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
09:05on time on time
09:09≈ on time ≈ +1 min
09:13≈ on time ≈ +1 min
09:19+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
Sat 14 NovWolfheze 09:28Partial coverage+1 min+1 min
Fri 13 NovWolfheze 09:28Partial coverage+1 min—
Thu 12 NovWolfheze 09:28Partial coverage0 min—
Wed 11 NovWolfheze 09:28Partial coverage0 min—
Tue 10 NovWolfheze 09:28Partial coverage0 min—
Mon 9 NovWolfheze 09:28Partial coverage0 min—
Sun 8 NovWolfheze 09:29Partial coverage+3 min+3 min
Sat 7 NovWolfheze 09:28Partial coverage+1 min—
Fri 6 NovWolfheze 09:34No data—
Thu 5 NovWolfheze 09:29Partial coverage0 min—
Wed 4 NovWolfheze 09:280 min—
Tue 3 NovWolfheze 09:29No data—
Mon 2 NovWolfheze 09:280 min—
Sun 1 NovWolfheze 09:29No data—
Mon 19 OctWolfheze 09:28No data—
Sun 18 OctWolfheze 09:28Partial coverage0 min—
Sat 17 OctWolfheze 09:28Partial coverage+1 min+1 min
Fri 16 OctWolfheze 09:27No data—
Thu 15 OctWolfheze 09:28Partial coverage0 min—
Wed 14 OctWolfheze 09:27No data—
Tue 13 OctWolfheze 09:28No data—
Mon 12 OctWolfheze 09:29Partial coverage0 min—
Sun 11 OctWolfheze 09:27+1 min+1 min
Sat 10 OctWolfheze 09:28+1 min+1 min
Fri 9 OctWolfheze 09:29+3 min+3 min
Thu 8 OctWolfheze 09:28+1 min+1 min
Wed 7 OctWolfheze 09:270 min—
Tue 6 OctWolfheze 09:270 min—
Mon 5 OctWolfheze 09:27No data—
Sun 4 OctWolfheze 09:28No data—