Train RRReis A 30442 Winterswijk – Apeldoorn

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:20 from Winterswijk · Sun 8 Nov

Next departure 14:20 today · Winterswijk
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 2 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 16 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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 +8 min · last fix heading to Zutphen +8 min

Distribution · 90 days

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

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

Stops and timetable

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

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