Train RRReis A 30419 Apeldoorn – Winterswijk

Apeldoorn 08:24 → Winterswijk 09:10 Sat, Sun 0 h 46 min · 7 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Winterswijk West at 09:19 0 min

  1. Apeldoorn08:24
  2. Zutphen08:37
  3. Vorden08:45
  4. Ruurlo08:52
  5. Lichtenvoorde-Groenlo09:00
  6. Winterswijk West09:07
  7. Winterswijk09:10

Next service: tomorrow 08:24 from Apeldoorn · Sun 8 Nov

Next departure 08:24 tomorrow · Apeldoorn
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 3 full · 5 partial · 1 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 3 full · 5 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Winterswijk, 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 18 Oct Max en route +5 min · last fix heading to Winterswijk West +4 min

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 88% · 7
  • 3–10 min 13% · 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=5
  • 67% 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 10
08:24on time on time
08:37 / 08:38— —
08:45 / 08:46— —
08:52— —
09:00— —
09:07— —
09:10— —

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 NovWinterswijk West 09:19Partial coverage0 min—
Sun 1 NovWinterswijk West 09:220 min—
Sat 31 OctWinterswijk West 09:21Partial coverage0 min—
Sun 25 OctWinterswijk West 09:22No data—
Sat 24 OctWinterswijk West 09:23Partial coverage+2 min+2 min
Sun 18 OctWinterswijk West 09:26+4 min+5 min
Sat 17 OctWinterswijk West 09:21Partial coverage0 min—
Sun 11 OctWinterswijk West 09:220 min—
Sat 10 OctWinterswijk West 09:22Partial coverage+1 min+1 min
Sun 4 OctWinterswijk West 09:22No data—
Sat 3 OctWinterswijk West 09:23No data—
Sun 27 SeptWinterswijk West 09:22No data—
Sat 26 SeptWinterswijk West 09:23No data—
Sun 20 SeptWinterswijk West 09:23No data—
Sat 19 SeptWinterswijk West 09:24No data—
Sun 6 SeptWinterswijk West 09:22No data—
Sat 5 SeptWinterswijk West 09:21No data—
Sun 30 AugWinterswijk West 09:22No data—
Sat 29 AugWinterswijk West 09:22No data—
Sun 23 AugWinterswijk West 09:22No data—
Sat 22 AugWinterswijk West 09:21No data—
Sun 16 AugWinterswijk West 09:22No data—
Sat 15 AugWinterswijk West 09:23No data—