Train RRReis A 30422 Winterswijk – Apeldoorn

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

✓ Today’s run finished

Today, last fix heading to Zutphen at 10:09 0 min

  1. Winterswijk09:20
  2. Winterswijk West09:22
  3. Lichtenvoorde-Groenlo09:29
  4. Ruurlo09:38
  5. Vorden09:44
  6. Zutphen09:54
  7. Apeldoorn10:08

Next service: tomorrow 09:20 from Winterswijk · Sun 8 Nov

Next departure 09:20 tomorrow · Winterswijk
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 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 18 Oct Max en route +4 min · last fix heading to Zutphen +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
09:20on time on time
09:22— —
09:29 / 09:30— —
09:38— —
09:44 / 09:46— —
09:54 / 09:55— —
10: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 10:09Partial coverage0 min—
Sun 1 NovZutphen 10:100 min—
Sat 31 OctZutphen 10:10Partial coverage0 min—
Sun 25 OctZutphen 10:09No data—
Sat 24 OctZutphen 10:13Partial coverage+2 min+3 min
Sun 18 OctZutphen 10:09+4 min+4 min
Sat 17 OctZutphen 10:12Partial coverage0 min—
Sun 11 OctZutphen 10:090 min—
Sat 10 OctZutphen 10:10Partial coverage+1 min+1 min
Sun 4 OctZutphen 10:11No data—
Sat 3 OctZutphen 10:11No data—
Sun 27 SeptZutphen 10:09No data—
Sat 26 SeptZutphen 10:10No data—
Sun 20 SeptZutphen 10:09No data—
Sat 19 SeptZutphen 10:09No data—
Sun 6 SeptZutphen 10:09No data—
Sat 5 SeptZutphen 10:12No data—
Sun 30 AugZutphen 10:10No data—
Sat 29 AugZutphen 10:18No data—
Sun 23 AugZutphen 10:09No data—
Sat 22 AugZutphen 10:10No data—
Sun 16 AugZutphen 10:09No data—
Sat 15 AugZutphen 10:10No data—