Train RRReis A 30812 Winterswijk – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Vorden at 07:28 No data

  1. Winterswijk06:47
  2. Winterswijk West06:49
  3. Lichtenvoorde-Groenlo06:56
  4. Ruurlo07:05
  5. Vorden07:11
  6. Zutphen07:21

Next service: Monday 06:47 from Winterswijk · Mon 9 Nov

Next departure 06:47 Monday · Winterswijk
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 3 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 0 full · 21 partial · 43 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 30 Oct Max en route +5 min · last fix heading to Vorden +4 min
  • Tue 13 Oct Max en route +3 min · last fix heading to Vorden +3 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Vorden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 18
  • 3–10 min 14% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 60% T n=5
  • 100% W n=5
  • 100% T n=4
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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
06:47on time on time
06:49— —
06:56 / 06:57— —
07:05— —
07:11 / 07:12— —
07:21— —

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