Train RRReis A 30814 Winterswijk – Zutphen

Winterswijk 07:17 → Zutphen 07:51 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 6 stops RRReis A

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 07:17 from Winterswijk · Mon 9 Nov

Next departure 07:17 Monday · Winterswijk
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 7 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 0 full · 17 partial · 47 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: +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

  • Wed 4 Nov Max en route +5 min · last fix heading to Vorden +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 75% W n=4
  • 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, 17 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
07:17on time on time
07:19— —
07:26 / 07:27— —
07:35— —
07:41 / 07:42— —
07:51— —

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