Train RRReis A 30822 Winterswijk → Zutphen

Winterswijk 09:20 → Zutphen 09:53 Mon, Tue, Wed, Thu, Fri, Sat 0 h 33 min · 6 stops RRReis A

It does not run today

Last recorded run: Friday 20 November +1 min

Next service: Monday 09:20 from Winterswijk · Mon 23 Nov

Next departure 09:20 Monday · Winterswijk
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 8 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Zutphen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +5 min · last fix heading to Vorden +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Vorden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 80% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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:45— —
09:53— —

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
Fri 20 NovVorden 09:59Partial coverage+1 min+1 min
Thu 19 NovVorden 09:59Partial coverage0 min—
Wed 18 NovVorden 09:59Partial coverage0 min—
Tue 17 NovVorden 09:59Partial coverage0 min—
Mon 16 NovVorden 09:59Partial coverage+1 min+1 min
Fri 13 NovVorden 09:59Partial coverage+1 min+1 min
Thu 12 NovVorden 09:59Partial coverage0 min—
Wed 11 NovVorden 09:59Partial coverage+2 min+2 min
Tue 10 NovVorden 09:59Partial coverage+2 min+2 min
Mon 9 NovVorden 09:59Partial coverage+3 min+3 min
Fri 6 NovVorden 09:59No data—
Thu 5 NovVorden 10:13No data—
Wed 4 NovVorden 09:59Partial coverage0 min—
Tue 3 NovVorden 09:59No data—
Mon 2 NovVorden 09:59No data—
Fri 30 OctVorden 10:00No data—
Thu 29 OctVorden 10:01No data—
Wed 28 OctVorden 10:00Partial coverage0 min—
Tue 27 OctVorden 10:00Partial coverage0 min—
Mon 26 OctVorden 09:59No data—
Fri 23 OctVorden 10:02No data—
Thu 22 OctVorden 10:02No data—
Wed 21 OctVorden 10:10No data—
Tue 20 OctVorden 10:02Partial coverage0 min—
Mon 19 OctVorden 09:59Partial coverage0 min—
Fri 16 OctVorden 09:59No data—
Thu 15 OctVorden 10:00No data—
Wed 14 OctVorden 09:59No data—
Tue 13 OctVorden 10:00No data—
Mon 12 OctVorden 10:00No data—