Train RRReis A 30458 Winterswijk – Apeldoorn

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

It does not run today

Last recorded run: Sunday 1 November +2 min

Next service: tomorrow 18:20 from Winterswijk · Sat 7 Nov

Next departure 18:20 tomorrow · Winterswijk
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 2 full · 3 partial · 3 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 2 full · 3 partial · 18 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 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=2
  • 100% S n=3

Stops and timetable

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

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