Train RRReis A 30434 Winterswijk – Apeldoorn

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

✓ Today’s run finished

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

  1. Winterswijk12:20
  2. Winterswijk West12:22
  3. Lichtenvoorde-Groenlo12:29
  4. Ruurlo12:38
  5. Vorden12:44
  6. Zutphen12:53
  7. Apeldoorn13:08

Next service: Saturday 12:20 from Winterswijk · Sat 14 Nov

Next departure 12:20 Saturday · Winterswijk
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 4 full · 4 partial · 2 no data
On-time · 90 days
75%
6/8 runs under 3 min
RT coverage: 4 full · 4 partial · 16 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 10 Oct Max en route +5 min · last fix heading to Zutphen +5 min
  • Sun 11 Oct Max en route +5 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 75% · 6
  • 3–10 min 25% · 2
  • 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
  • 75% S n=4
  • 75% S n=4

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