Train NS 7520 Arnhem Centraal – Ede-Wageningen

Arnhem Centraal 07:04 → Ede-Wageningen 07:18 Daily 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November +1 min

Next service: today 07:04 from Arnhem Centraal · Sat 14 Nov

Next departure 07:04 today · Arnhem Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 4 full · 12 partial · 1 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 5 full · 21 partial · 48 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
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 +6 min · last fix heading to Wolfheze +5 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Wolfheze +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Wolfheze +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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