Train NS 7585 Ede-Wageningen – Arnhem Centraal

Ede-Wageningen 23:29 → Arnhem Centraal 23:43 Daily 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:29 from Ede-Wageningen · Fri 6 Nov

Next departure 23:29 today · Ede-Wageningen
On-time · 30 days
73%
8/11 runs under 3 min
RT coverage: 9 full · 2 partial · 4 no data
On-time · 90 days
71%
10/14 runs under 3 min
RT coverage: 12 full · 2 partial · 15 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 Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 1 Nov Max en route +13 min · last fix heading to Oosterbeek +13 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 10
  • 3–10 min 21% · 3
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
23:29on time on time
23:35≈ on time ≈ +2 min
23:39≈ on time ≈ +3 min
23:43+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
Thu 5 Nov— 23:44No data—
Wed 4 Nov— 23:44+1 min—
Mon 2 Nov— 23:44+2 min+2 min
Sun 1 NovOosterbeek 00:09Partial coverage+13 min+13 min
Sun 18 OctOosterbeek 23:54Partial coverage0 min—
Sat 17 OctOosterbeek 23:54No data—
Fri 16 Oct— 23:52+4 min+4 min
Thu 15 Oct— 23:45No data—
Wed 14 Oct— 23:44No data—
Tue 13 Oct— 23:490 min—
Mon 12 Oct— 23:440 min—
Sun 11 OctOosterbeek 00:060 min—
Sat 10 Oct— 23:47+1 min+1 min
Fri 9 Oct— 23:51+3 min+3 min
Thu 8 Oct— 23:440 min—
Wed 7 Oct— 23:440 min—
Tue 6 Oct— 23:460 min—
Mon 5 Oct— 23:52+4 min+4 min
Sun 4 OctOosterbeek 23:54No data—
Sat 3 OctOosterbeek 23:48No data—
Sun 27 SeptOosterbeek 23:53No data—
Sat 26 SeptOosterbeek 23:53No data—
Sun 20 SeptOosterbeek 23:54No data—
Sun 13 SeptOosterbeek 23:54No data—
Sat 12 SeptOosterbeek 23:53No data—
Sun 6 SeptOosterbeek 23:53No data—
Sun 30 AugOosterbeek 23:54No data—
Sun 16 AugOosterbeek 23:56No data—
Sun 9 AugOosterbeek 23:54No data—