Train NS 7570 Arnhem Centraal – Ede-Wageningen

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 19:34 from Arnhem Centraal · Fri 6 Nov

Next departure 19:34 today · Arnhem Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 4 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 7 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 50% 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, 11 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
19:34on time on time
19:38≈ on time ≈ on time
19:42≈ on time ≈ +1 min
19:48on time +1 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
Thu 5 Nov— 19:490 min—
Wed 4 Nov— 19:49+1 min+1 min
Tue 3 Nov— 19:49No data—
Mon 2 Nov— 19:52No data—
Mon 19 Oct— 19:500 min—
Fri 16 OctWolfheze 19:53No data—
Thu 15 Oct— 19:490 min—
Wed 14 OctWolfheze 19:56No data—
Tue 13 Oct— 19:550 min—
Mon 12 Oct— 19:490 min—
Fri 9 Oct— 19:490 min—
Thu 8 Oct— 19:500 min—
Wed 7 Oct— 20:00+5 min+6 min
Tue 6 Oct— 19:490 min—
Mon 5 Oct— 19:490 min—
Fri 21 AugWolfheze 19:56No data—
Mon 17 AugWolfheze 19:56No data—
Fri 14 AugWolfheze 19:56No data—
Thu 13 AugWolfheze 19:56No data—
Wed 12 AugWolfheze 19:53No data—
Tue 11 AugWolfheze 19:56No data—
Mon 10 AugWolfheze 19:56No data—