Train RRReis A 30816 Winterswijk → Zutphen

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

RRReis A 30816 Winterswijk–Zutphen: final delay under 3 min on 12 of its 16 runs with data in the last 30 days (75%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 16:22 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 07:47 from Winterswijk · Mon 23 Nov

Next departure 07:47 tomorrow · Winterswijk
On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 0 full · 16 partial · 4 no data
On-time · 90 days
83%
19/23 runs under 3 min
RT coverage: 0 full · 23 partial · 40 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 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

  • Mon 9 Nov Max en route +6 min · last fix heading to Vorden +5 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Vorden +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Vorden +4 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Vorden +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 19
  • 3–10 min 17% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:47on time on time
07:49— —
07:56 / 07:57— —
08:05— —
08:11 / 08:12— —
08: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 20 NovVorden 08:27Partial coverage0 min+1 min
Thu 19 NovVorden 08:28Partial coverage+1 min+2 min
Wed 18 NovVorden 08:28Partial coverage+2 min+2 min
Tue 17 NovVorden 08:29Partial coverage+3 min+3 min
Mon 16 NovVorden 08:28Partial coverage+1 min+1 min
Fri 13 NovVorden 08:27Partial coverage+1 min—
Thu 12 NovVorden 08:29Partial coverage+4 min+4 min
Wed 11 NovVorden 08:29Partial coverage+4 min+4 min
Tue 10 NovVorden 08:29Partial coverage+4 min+4 min
Mon 9 NovVorden 08:29Partial coverage+5 min+6 min
Fri 6 NovVorden 08:27No data—
Thu 5 NovVorden 08:37No data—
Wed 4 NovVorden 08:29Partial coverage+3 min+3 min
Tue 3 NovVorden 08:28No data—
Mon 2 NovVorden 08:27No data—
Fri 30 OctVorden 08:31Partial coverage0 min—
Thu 29 OctVorden 08:26Partial coverage0 min—
Wed 28 OctVorden 08:28Partial coverage0 min—
Tue 27 OctVorden 08:29Partial coverage0 min—
Mon 26 OctVorden 08:28Partial coverage0 min—
Fri 23 OctVorden 08:27Partial coverage0 min—
Thu 22 OctVorden 08:26No data—
Wed 21 OctVorden 08:29No data—
Tue 20 OctVorden 08:26Partial coverage0 min—
Mon 19 OctVorden 08:26Partial coverage0 min—
Fri 16 OctVorden 08:28No data—
Thu 15 OctVorden 08:31No data—
Wed 14 OctVorden 08:27No data—
Tue 13 OctVorden 08:31No data—
Mon 12 OctVorden 08:28No data—