Train NS 7556 Arnhem Centraal – Ede-Wageningen

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

✓ Today’s run finished

Today, last fix heading to Wolfheze at 16:27 No data

  1. Arnhem Centraal16:04
  2. Oosterbeek16:08
  3. Wolfheze16:12
  4. Ede-Wageningen16:18

Next service: tomorrow 16:04 from Arnhem Centraal · Sat 7 Nov

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

  • Wed 4 Nov Max en route +4 min · last fix heading to Wolfheze +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
16:04on time on time
16:08— —
16:12— —
16:18— —

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 6 NovWolfheze 16:27No data—
Thu 5 NovWolfheze 16:27Partial coverage0 min—
Wed 4 NovWolfheze 16:29+4 min+4 min
Tue 3 NovWolfheze 16:27No data—
Mon 2 NovWolfheze 16:390 min—
Mon 19 OctWolfheze 16:28No data—
Sun 18 OctWolfheze 16:27Partial coverage+1 min+1 min
Sat 17 OctWolfheze 16:27No data—
Fri 16 OctWolfheze 16:27No data—
Thu 15 OctWolfheze 16:26Partial coverage0 min—
Wed 14 OctWolfheze 16:27No data—
Tue 13 OctWolfheze 16:27No data—
Mon 12 OctWolfheze 16:27Partial coverage+1 min—
Sun 11 OctWolfheze 16:27Partial coverage+1 min—
Sat 10 OctWolfheze 16:27Partial coverage+1 min—
Fri 9 OctWolfheze 16:27Partial coverage+1 min—
Thu 8 OctWolfheze 16:29Partial coverage+2 min+3 min
Wed 7 OctWolfheze 16:27Partial coverage0 min—
Tue 6 OctWolfheze 16:28Partial coverage+2 min+2 min
Mon 5 OctWolfheze 16:24Partial coverage0 min—
Sun 4 OctWolfheze 16:27No data—
Sat 3 OctWolfheze 16:27No data—
Fri 2 OctWolfheze 16:26No data—
Thu 1 OctWolfheze 16:27No data—
Wed 30 SeptWolfheze 16:27No data—
Tue 29 SeptWolfheze 16:26No data—
Mon 28 SeptWolfheze 16:27No data—
Sun 27 SeptWolfheze 16:27No data—
Sat 26 SeptWolfheze 16:27No data—
Fri 25 SeptWolfheze 16:27No data—