Train NS 7588 Arnhem Centraal – Ede-Wageningen

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

✓ Today’s run finished

Today, last fix heading to — at 00:19 +1 min

  1. Arnhem Centraal00:04
  2. Oosterbeek00:08
  3. Wolfheze00:12
  4. Ede-Wageningen00:18

Next service: tomorrow 00:04 from Arnhem Centraal · Sun 8 Nov

Next departure 00:04 tomorrow · Arnhem Centraal
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 12 full · 2 partial · 1 no data
On-time · 90 days
71%
12/17 runs under 3 min
RT coverage: 14 full · 3 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +8 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

  • Sat 17 Oct Max en route +13 min · last fix heading to Wolfheze +13 min
  • Tue 3 Nov Max en route +9 min · last fix heading to — +9 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Wolfheze +4 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Wolfheze +4 min
  • Sun 18 Oct Max en route +3 min · last fix heading to Wolfheze +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 12
  • 3–10 min 24% · 4
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 50% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=1
  • 67% S n=3
  • 33% S n=3

Stops and timetable

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

Last 90 days, 17 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
00:04on time on time
00:08≈ on time ≈ +3 min
00:12≈ on time ≈ +6 min
00:18on time +7 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 7 Nov— 00:19+1 min—
Fri 6 Nov— 00:440 min—
Thu 5 Nov— 00:250 min—
Wed 4 Nov— 00:190 min—
Tue 3 Nov— 00:24+9 min+9 min
Sun 1 NovWolfheze 00:29+2 min+3 min
Tue 20 Oct— 00:190 min—
Sun 18 OctWolfheze 00:29Partial coverage+3 min+3 min
Sat 17 OctWolfheze 00:26+13 min+13 min
Fri 16 Oct— 00:20No data—
Thu 15 Oct— 00:190 min—
Wed 14 Oct— 00:190 min—
Tue 13 Oct— 00:200 min—
Sun 11 OctWolfheze 00:30Partial coverage+4 min+4 min
Sat 10 Oct— 00:23+3 min+3 min
Thu 8 Oct— 00:20+2 min+2 min
Wed 7 Oct— 00:190 min—
Tue 6 OctWolfheze 00:26Partial coverage+4 min+4 min
Sun 4 OctWolfheze 00:26No data—
Sat 3 OctWolfheze 00:18No data—
Sun 27 SeptWolfheze 00:26No data—
Sun 20 SeptWolfheze 00:27No data—
Sun 13 SeptWolfheze 00:26No data—
Sun 6 SeptWolfheze 00:27No data—
Sun 30 AugWolfheze 00:27No data—
Sun 16 AugWolfheze 00:26No data—