Train RRReis A 30850 Winterswijk – Zutphen

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:20 from Winterswijk · Thu 5 Nov

Next departure 16:20 today · Winterswijk
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 0 full · 10 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
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 9 Oct Max en route +6 min · last fix heading to Vorden +6 min
  • Mon 5 Oct Max en route +6 min · last fix heading to Vorden +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 8
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 0% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 10 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
16:20on time on time
16:22— —
16:29 / 16:30— —
16:38— —
16:44 / 16:45— —
16: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
Wed 4 NovVorden 16:59No data—
Tue 3 NovVorden 16:59No data—
Mon 2 NovVorden 16:59No data—
Fri 30 OctVorden 17:01No data—
Thu 29 OctVorden 16:59Partial coverage0 min—
Wed 28 OctVorden 16:59Partial coverage0 min—
Tue 27 OctVorden 16:59No data—
Mon 26 OctVorden 16:59No data—
Fri 23 OctVorden 17:01No data—
Thu 22 OctVorden 16:59No data—
Wed 21 OctVorden 16:59No data—
Tue 20 OctVorden 16:59Partial coverage0 min—
Mon 19 OctVorden 17:00Partial coverage0 min—
Fri 16 OctVorden 17:00No data—
Thu 15 OctVorden 17:02No data—
Wed 14 OctVorden 16:59No data—
Tue 13 OctVorden 16:59No data—
Mon 12 OctVorden 17:00Partial coverage0 min—
Fri 9 OctVorden 17:05Partial coverage+6 min+6 min
Thu 8 OctVorden 16:59Partial coverage0 min—
Wed 7 OctVorden 17:00Partial coverage+1 min+1 min
Tue 6 OctVorden 16:59Partial coverage0 min—
Mon 5 OctVorden 17:03Partial coverage+6 min+6 min
Fri 2 OctVorden 16:59No data—
Thu 1 OctVorden 17:01No data—
Wed 30 SeptVorden 17:00No data—
Tue 29 SeptVorden 16:59No data—
Mon 28 SeptVorden 16:59No data—
Fri 25 SeptVorden 17:00No data—
Thu 24 SeptVorden 16:59No data—