Train RRReis A 30430 Winterswijk – Apeldoorn

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

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: Saturday 11:20 from Winterswijk · Sat 7 Nov

Next departure 11:20 Saturday · Winterswijk
On-time · 30 days
67%
4/6 runs under 3 min
RT coverage: 3 full · 3 partial · 2 no data
On-time · 90 days
67%
4/6 runs under 3 min
RT coverage: 3 full · 3 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

Worst days

  • Sun 11 Oct Max en route +5 min · last fix heading to Apeldoorn De Maten +5 min
  • Sat 24 Oct Max en route +9 min · last fix heading to Zutphen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 4
  • 3–10 min 33% · 2
  • 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
  • 67% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 6 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
11:20on time on time
11:22— —
11:29 / 11:30— —
11:38— —
11:44 / 11:45— —
11:53 / 11:55— —
12: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
Sun 1 NovZutphen 12:10Partial coverage0 min—
Sat 31 OctZutphen 12:110 min—
Sun 25 OctZutphen 12:11No data—
Sat 24 OctZutphen 12:15+4 min+9 min
Sun 18 OctZutphen 12:11Partial coverage0 min—
Sat 17 OctZutphen 12:10No data—
Sun 11 OctApeldoorn De Maten 12:24Partial coverage+5 min+5 min
Sat 10 OctZutphen 12:10+1 min+1 min
Sun 4 OctZutphen 12:10No data—
Sat 3 OctZutphen 12:11No data—
Sun 27 SeptZutphen 12:09No data—
Sat 26 SeptZutphen 12:09No data—
Sun 20 SeptZutphen 12:09No data—
Sat 19 SeptZutphen 12:08No data—
Sun 6 SeptZutphen 12:09No data—
Sat 5 SeptZutphen 12:10No data—
Sun 30 AugZutphen 12:09No data—
Sat 29 AugZutphen 12:10No data—
Sun 23 AugZutphen 12:11No data—
Sat 22 AugZutphen 12:09No data—
Sun 16 AugZutphen 12:11No data—
Sat 15 AugZutphen 12:10No data—
Sun 9 AugZutphen 12:09No data—
Sat 8 AugZutphen 12:09No data—