Train RRReis A 30410 Winterswijk – Apeldoorn

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

It does not run today

Last recorded run: Saturday 10 October 0 min

Next service: Saturday 06:20 from Winterswijk · Sat 17 Oct

Next departure 06:20 Saturday · Winterswijk
On-time · 30 days
—
Too little data (1/4 runs with data)
RT coverage: 0 full · 1 partial · 3 no data
On-time · 90 days
—
Too little data (1/11 runs with data)
RT coverage: 0 full · 1 partial · 10 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

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

  • Early 0% · 0
  • On time 100% · 1
  • 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=1
  • — S n=0

Stops and timetable

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

StopSched.
06:20
06:22
06:29 / 06:30
06:38
06:44 / 06:45
06:53 / 06:55
07: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.

Recent runs

DateLast stopFinalMax
Sat 10 OctZutphen 07:11Partial coverage0 min—
Sat 3 OctZutphen 07:09No data—
Sat 26 SeptZutphen 07:09No data—
Sat 19 SeptZutphen 07:09No data—
Sat 5 SeptZutphen 07:09No data—
Sat 29 AugZutphen 07:09No data—
Sat 22 AugZutphen 07:09No data—
Sat 15 AugZutphen 07:09No data—
Sat 8 AugZutphen 07:10No data—
Sat 1 AugZutphen 07:09No data—
Sat 25 JulZutphen 07:09No data—