Train NS 7525 Ede-Wageningen – Arnhem Centraal

Ede-Wageningen 08:42 → Arnhem Centraal 08:56 Daily 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Oosterbeek at 09:07 0 min

  1. Ede-Wageningen08:42
  2. Wolfheze08:48
  3. Oosterbeek08:52
  4. Arnhem Centraal08:56

Next service: tomorrow 08:42 from Ede-Wageningen · Fri 20 Nov

Next departure 08:42 tomorrow · Ede-Wageningen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 0 full · 16 partial · 3 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 0 full · 26 partial · 49 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 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

  • Tue 17 Nov Max en route +5 min · last fix heading to Oosterbeek +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 100% W n=4
  • 100% T n=5
  • 100% F n=2
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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
08:42on time on time
08:48— —
08:52— —
08:56— —

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 19 NovOosterbeek 09:07Partial coverage0 min—
Wed 18 NovOosterbeek 09:07Partial coverage0 min—
Tue 17 NovOosterbeek 09:09Partial coverage+5 min+5 min
Mon 16 NovOosterbeek 09:07Partial coverage0 min—
Sun 15 NovOosterbeek 09:08Partial coverage0 min—
Sat 14 NovOosterbeek 09:07Partial coverage0 min—
Fri 13 NovOosterbeek 09:08Partial coverage+1 min+2 min
Thu 12 NovOosterbeek 09:07Partial coverage0 min—
Wed 11 NovOosterbeek 09:07Partial coverage+1 min—
Tue 10 NovOosterbeek 09:04Partial coverage0 min—
Mon 9 NovOosterbeek 09:04Partial coverage0 min—
Sun 8 NovOosterbeek 09:07Partial coverage+1 min—
Sat 7 NovOosterbeek 09:07Partial coverage0 min—
Fri 6 NovOosterbeek 09:04No data—
Thu 5 NovOosterbeek 09:09Partial coverage0 min—
Wed 4 NovOosterbeek 09:07Partial coverage0 min—
Tue 3 NovOosterbeek 09:08No data—
Mon 2 NovOosterbeek 09:07Partial coverage0 min—
Sun 1 NovOosterbeek 09:05No data—
Mon 19 OctOosterbeek 09:07No data—
Sun 18 OctOosterbeek 09:07Partial coverage0 min—
Sat 17 OctOosterbeek 09:07Partial coverage0 min—
Fri 16 OctOosterbeek 09:06No data—
Thu 15 OctOosterbeek 09:07Partial coverage0 min—
Wed 14 OctOosterbeek 09:07No data—
Tue 13 OctOosterbeek 09:07No data—
Mon 12 OctOosterbeek 09:08Partial coverage0 min—
Sun 11 OctOosterbeek 09:07Partial coverage+1 min—
Sat 10 OctOosterbeek 09:07Partial coverage0 min—
Fri 9 OctOosterbeek 09:07Partial coverage+1 min—