Train NS 7576 Arnhem Centraal – Ede-Wageningen

Arnhem Centraal 21:04 → Ede-Wageningen 21: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 21:04 from Arnhem Centraal · Sat 14 Nov

Next departure 21:04 today · Arnhem Centraal
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 10 full · 3 partial · 4 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
+4min
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

  • Mon 2 Nov Max en route +7 min · last fix heading to — +7 min
  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 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 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
21:04on time on time
21:08≈ on time ≈ +1 min
21:12≈ on time ≈ +3 min
21: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— 21:19+1 min—
Thu 12 Nov— 21:190 min—
Wed 11 Nov— 21:190 min—
Tue 10 Nov— 21:19+1 min+1 min
Mon 9 Nov— 21:22+2 min+2 min
Sun 8 NovWolfheze 21:29Partial coverage+3 min+3 min
Sat 7 NovWolfheze 21:24Partial coverage0 min—
Fri 6 Nov— 21:190 min—
Thu 5 Nov— 21:190 min—
Wed 4 Nov— 21:24+3 min+3 min
Tue 3 Nov— 21:22No data—
Mon 2 Nov— 21:34+7 min+7 min
Sun 1 Nov— 21:19No data—
Mon 19 Oct— 21:24No data—
Sun 18 OctWolfheze 21:29Partial coverage+3 min+3 min
Sat 17 OctWolfheze 21:27No data—
Fri 16 Oct— 21:22+4 min+4 min
Thu 15 Oct— 21:220 min—
Wed 14 Oct— 21:22No data—
Tue 13 Oct— 21:340 min—
Mon 12 Oct— 21:340 min—
Sun 11 OctWolfheze 21:27Partial coverage+1 min—
Sat 10 OctWolfheze 21:26Partial coverage0 min—
Fri 9 Oct— 21:30+6 min+6 min
Thu 8 Oct— 21:19+1 min—
Wed 7 Oct— 21:20+1 min+1 min
Tue 6 Oct— 21:190 min—
Mon 5 Oct— 21:24+2 min+2 min
Sun 4 OctWolfheze 21:27No data—
Sat 3 OctWolfheze 21:27No data—