Train RRReis A 30414 Winterswijk – Apeldoorn

Winterswijk 07:20 → Apeldoorn 08:08 Sat, Sun 0 h 48 min · 7 stops RRReis A

Running now · updated 07:52

Heading to Apeldoorn 0 min

Estimated arrival at Apeldoorn 08:08 · 82 km/h

  1. Winterswijk07:20
  2. Winterswijk West07:22
  3. Lichtenvoorde-Groenlo07:29
  4. Ruurlo07:38
  5. Vorden07:44
  6. Zutphen07:53
  7. Apeldoorn08:08

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 8 runs arrived on time.

On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 1 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 15 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 Apeldoorn, 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 8 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:20on time on time
07:22— —
07:29 / 07:30— —
07:38— —
07:44 / 07:45— —
07:53 / 07:55— —
08:08— —

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
Sat 7 NovZutphen 07:49Partial coverage0 min—
Sun 1 NovZutphen 08:10Partial coverage0 min—
Sat 31 OctZutphen 08:09Partial coverage0 min—
Sun 25 OctZutphen 08:10No data—
Sat 24 OctZutphen 08:10Partial coverage0 min—
Sun 18 OctZutphen 08:11Partial coverage+2 min+3 min
Sat 17 OctZutphen 08:11Partial coverage+1 min+1 min
Sun 11 OctZutphen 08:09Partial coverage+1 min—
Sat 10 OctZutphen 08:10Partial coverage0 min—
Sun 4 OctZutphen 08:09No data—
Sat 3 OctZutphen 08:09No data—
Sun 27 SeptZutphen 08:10No data—
Sat 26 SeptZutphen 08:09No data—
Sun 20 SeptZutphen 08:09No data—
Sat 19 SeptZutphen 08:09No data—
Sun 6 SeptZutphen 08:09No data—
Sat 5 SeptZutphen 08:09No data—
Sun 30 AugZutphen 08:09No data—
Sat 29 AugZutphen 08:10No data—
Sun 23 AugZutphen 08:09No data—
Sat 22 AugZutphen 08:09No data—
Sun 16 AugZutphen 08:09No data—
Sat 15 AugZutphen 08:09No data—