Train NS 7541 Ede-Wageningen – Arnhem Centraal

Ede-Wageningen 12:42 → Arnhem Centraal 12:56 Daily 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 12:42 from Ede-Wageningen · Fri 6 Nov

Next departure 12:42 today · Ede-Wageningen
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 7 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 61 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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