Train NS 7519 Ede-Wageningen – Arnhem Centraal

Ede-Wageningen 07:12 → Arnhem Centraal 07:26 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Ede-Wageningen07:12
  2. Wolfheze07:18
  3. Oosterbeek07:22
  4. Arnhem Centraal07:26

Next service: tomorrow 07:12 from Ede-Wageningen · Fri 6 Nov

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

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=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • — S n=0
  • — S n=0

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
07:12on time on time
07:18— —
07:22— —
07:26— —

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 07:39Partial coverage0 min—
Wed 4 NovOosterbeek 07:39Partial coverage+2 min+2 min
Tue 3 NovOosterbeek 07:37Partial coverage0 min—
Mon 2 NovOosterbeek 07:38Partial coverage0 min—
Mon 19 OctOosterbeek 07:37Partial coverage0 min—
Fri 16 OctOosterbeek 07:37Partial coverage0 min—
Thu 15 OctOosterbeek 07:38Partial coverage0 min—
Wed 14 OctOosterbeek 07:37Partial coverage0 min—
Tue 13 OctOosterbeek 07:37Partial coverage0 min—
Mon 12 OctOosterbeek 07:37No data—
Fri 9 OctOosterbeek 07:37Partial coverage+1 min—
Thu 8 OctOosterbeek 07:37Partial coverage0 min—
Wed 7 OctOosterbeek 07:37Partial coverage0 min—
Tue 6 OctOosterbeek 07:37Partial coverage+1 min—
Mon 5 OctOosterbeek 07:37No data—
Fri 2 OctOosterbeek 07:37No data—
Thu 1 OctOosterbeek 07:37No data—
Wed 30 SeptOosterbeek 07:37No data—
Tue 29 SeptOosterbeek 07:37No data—
Mon 28 SeptOosterbeek 07:37No data—
Fri 25 SeptOosterbeek 07:36No data—
Thu 24 SeptOosterbeek 07:38No data—
Wed 23 SeptOosterbeek 07:36No data—
Tue 22 SeptOosterbeek 07:37No data—
Mon 21 SeptOosterbeek 07:37No data—
Fri 18 SeptOosterbeek 07:37No data—
Thu 17 SeptOosterbeek 07:37No data—
Wed 16 SeptOosterbeek 07:37No data—
Tue 15 SeptOosterbeek 07:37No data—
Mon 14 SeptOosterbeek 07:36No data—