Train NS 7521 Ede-Wageningen – Arnhem Centraal

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

Running now · updated 08:05

Position estimated from the timetable

Heading to Arnhem Centraal +2 min

Estimated arrival at Arnhem Centraal 07:58 07:56

  1. Ede-Wageningen07:42
  2. Wolfheze07:48
  3. Oosterbeek07:52
  4. Arnhem Centraal07:56

Today it is running worse than usual: typical arrival delay is +1 min; 88% of the last 16 runs arrived on time.

On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 5 full · 11 partial · 2 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 9 full · 19 partial · 47 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: +5 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 +9 min · last fix heading to Oosterbeek +9 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Oosterbeek +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=2
  • 100% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 28 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 10Today
07:42on time on time
07:48≈ on time ≈ +1 min
07:52≈ on time ≈ +2 min
07:56+1 min +3 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
Wed 18 NovOosterbeek 08:04Partial coverage+2 min+2 min
Tue 17 NovOosterbeek 08:14Partial coverage+9 min+9 min
Mon 16 NovOosterbeek 08:08Partial coverage+2 min+2 min
Sun 15 NovOosterbeek 08:070 min—
Sat 14 NovOosterbeek 08:070 min—
Fri 13 NovOosterbeek 08:07Partial coverage+1 min—
Thu 12 NovOosterbeek 08:07Partial coverage+1 min—
Wed 11 NovOosterbeek 08:07Partial coverage+1 min—
Tue 10 NovOosterbeek 08:08Partial coverage+1 min+1 min
Mon 9 NovOosterbeek 08:07Partial coverage0 min—
Sun 8 NovOosterbeek 08:08+1 min+2 min
Sat 7 NovOosterbeek 08:070 min—
Fri 6 NovOosterbeek 08:08No data—
Thu 5 NovOosterbeek 08:09Partial coverage0 min—
Wed 4 NovOosterbeek 08:07Partial coverage+1 min+1 min
Tue 3 NovOosterbeek 08:07No data—
Mon 2 NovOosterbeek 08:07Partial coverage0 min—
Sun 1 NovOosterbeek 08:11+8 min+8 min
Mon 19 OctOosterbeek 08:07Partial coverage0 min—
Sun 18 OctOosterbeek 08:070 min—
Sat 17 OctOosterbeek 08:08+1 min—
Fri 16 OctOosterbeek 08:06No data—
Thu 15 OctOosterbeek 08:07Partial coverage0 min—
Wed 14 OctOosterbeek 08:07No data—
Tue 13 OctOosterbeek 08:07Partial coverage0 min—
Mon 12 OctOosterbeek 08:07Partial coverage0 min—
Sun 11 OctOosterbeek 08:08+1 min+2 min
Sat 10 OctOosterbeek 08:09+2 min+2 min
Fri 9 OctOosterbeek 08:08Partial coverage+1 min—
Thu 8 OctOosterbeek 08:07Partial coverage0 min—