Train NS 7534 Arnhem Centraal – Ede-Wageningen

Arnhem Centraal 10:34 → Ede-Wageningen 10:48 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wolfheze at 10:57 0 min

  1. Arnhem Centraal10:34
  2. Oosterbeek10:38
  3. Wolfheze10:42
  4. Ede-Wageningen10:48

Next service: tomorrow 10:34 from Arnhem Centraal · Fri 6 Nov

Next departure 10:34 tomorrow · Arnhem Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 2 full · 6 partial · 5 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 2 full · 7 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 9
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 9 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
10:34on time on time
10:38— —
10:42— —
10:48— —

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
Thu 5 NovWolfheze 10:57Partial coverage0 min—
Wed 4 NovWolfheze 10:59+3 min+3 min
Tue 3 NovWolfheze 10:57No data—
Mon 2 NovWolfheze 10:54No data—
Mon 19 OctWolfheze 10:57Partial coverage0 min—
Fri 16 OctWolfheze 10:57No data—
Thu 15 OctWolfheze 10:57Partial coverage0 min—
Wed 14 OctWolfheze 10:58No data—
Tue 13 OctWolfheze 11:00Partial coverage0 min—
Mon 12 OctWolfheze 10:57No data—
Fri 9 OctWolfheze 10:57Partial coverage+1 min—
Thu 8 OctWolfheze 10:58Partial coverage+1 min+1 min
Wed 7 OctArnhem Centraal 12:020 min—
Tue 6 OctWolfheze 10:57Partial coverage0 min—
Mon 5 OctWolfheze 11:01No data—
Fri 2 OctWolfheze 10:57No data—
Thu 1 OctWolfheze 10:56No data—
Wed 30 SeptWolfheze 10:58No data—
Tue 29 SeptWolfheze 10:57No data—
Mon 28 SeptWolfheze 10:57No data—
Fri 25 SeptWolfheze 10:56No data—
Thu 24 SeptWolfheze 11:01No data—
Wed 23 SeptWolfheze 10:57No data—
Tue 22 SeptWolfheze 10:57No data—
Mon 21 SeptWolfheze 11:00No data—
Fri 18 SeptWolfheze 10:56No data—
Thu 17 SeptWolfheze 10:56No data—
Wed 16 SeptWolfheze 11:03No data—
Tue 15 SeptWolfheze 10:56No data—
Mon 14 SeptWolfheze 10:56No data—