Train NS 7580 Arnhem Centraal – Ede-Wageningen

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

✓ Today’s run finished

Today, last fix heading to — at 22:19 +2 min

  1. Arnhem Centraal22:04
  2. Oosterbeek22:08
  3. Wolfheze22:12
  4. Ede-Wageningen22:18

Next service: tomorrow 22:04 from Arnhem Centraal · Sat 14 Nov

Next departure 22:04 tomorrow · Arnhem Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 12 full · 3 partial · 2 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 18 full · 5 partial · 17 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

  • Sun 1 Nov Max en route +11 min · last fix heading to Wolfheze +11 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 9% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
22:04on time on time
22:08≈ on time ≈ +1 min
22:12≈ +1 min ≈ +2 min
22: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 Nov— 22:19+2 min+2 min
Thu 12 Nov— 22:22+1 min+1 min
Wed 11 Nov— 22:190 min—
Tue 10 Nov— 22:19+1 min+1 min
Mon 9 Nov— 22:19+1 min—
Sun 8 NovWolfheze 22:27Partial coverage0 min—
Sat 7 NovWolfheze 22:24Partial coverage0 min—
Fri 6 Nov— 22:19+1 min—
Thu 5 Nov— 22:190 min—
Wed 4 Nov— 22:190 min—
Mon 2 Nov— 22:19+2 min+2 min
Sun 1 NovWolfheze 22:39+11 min+11 min
Mon 19 Oct— 22:20No data—
Sun 18 OctWolfheze 22:27Partial coverage+1 min+1 min
Sat 17 OctWolfheze 22:34No data—
Fri 16 Oct— 22:20+1 min+1 min
Thu 15 Oct— 22:200 min—
Wed 14 Oct— 22:20No data—
Tue 13 Oct— 22:210 min—
Mon 12 Oct— 22:20No data—
Sun 11 OctWolfheze 22:26Partial coverage0 min—
Sat 10 OctArnhem Centraal 22:20Partial coverage0 min—
Fri 9 Oct— 22:20+1 min+1 min
Thu 8 Oct— 22:28+4 min+4 min
Wed 7 Oct— 22:20+1 min—
Tue 6 Oct— 22:27+3 min+4 min
Mon 5 Oct— 22:190 min—
Sun 4 OctWolfheze 22:31No data—
Sat 3 OctWolfheze 22:27No data—
Sun 27 SeptWolfheze 22:26No data—