Train NS 7589 Ede-Wageningen – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 00:44 0 min

  1. Ede-Wageningen00:29
  2. Wolfheze00:35
  3. Oosterbeek00:39
  4. Arnhem Centraal00:43

Next service: tomorrow 00:29 from Ede-Wageningen · Fri 6 Nov

Next departure 00:29 tomorrow · Ede-Wageningen
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 12 full · 2 partial · 1 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 13 full · 2 partial · 10 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 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

  • Sat 17 Oct Max en route +7 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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:29on time on time
00:35≈ on time ≈ +1 min
00:39≈ on time ≈ +2 min
00:43on time +2 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— 00:440 min—
Tue 3 Nov— 00:49+3 min+3 min
Mon 2 NovOosterbeek 01:04Partial coverage0 min—
Mon 19 OctOosterbeek 00:55Partial coverage0 min—
Sun 18 OctOosterbeek 00:53No data—
Sat 17 Oct— 00:56+6 min+7 min
Fri 16 Oct— 00:440 min—
Thu 15 Oct— 00:440 min—
Wed 14 Oct— 00:440 min—
Tue 13 Oct— 00:440 min—
Mon 12 OctOosterbeek 00:540 min—
Sun 11 Oct— 00:450 min—
Sat 10 Oct— 00:46+1 min+1 min
Thu 8 Oct— 00:440 min—
Wed 7 Oct— 00:440 min—
Tue 6 Oct— 00:450 min+1 min
Mon 5 OctOosterbeek 00:53No data—
Sun 4 OctWolfheze 00:49No data—
Mon 28 SeptOosterbeek 00:53No data—
Mon 21 SeptOosterbeek 00:53No data—
Mon 14 SeptOosterbeek 00:53No data—
Mon 7 SeptOosterbeek 00:53No data—
Mon 31 AugOosterbeek 00:55No data—
Mon 17 AugOosterbeek 00:53No data—
Mon 10 AugOosterbeek 00:54No data—