Train RRReis A 30836 Winterswijk → Zutphen

Winterswijk 12:50 → Zutphen 13:23 Daily 0 h 33 min · 6 stops RRReis A

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

It has not run yet today

Last recorded run: Saturday 21 November +5 min

Next service: today 12:50 from Winterswijk · Sun 22 Nov

Next departure 12:50 today · Winterswijk
On-time · 30 days
82%
18/22 runs under 3 min
RT coverage: 0 full · 22 partial · 7 no data
On-time · 90 days
80%
24/30 runs under 3 min
RT coverage: 0 full · 30 partial · 56 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

  • Sat 14 Nov Max en route +14 min · last fix heading to Vorden +14 min
  • Sat 21 Nov Max en route +5 min · last fix heading to Vorden +5 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Vorden +4 min
  • Fri 20 Nov Max en route +4 min · last fix heading to Vorden +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Vorden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 24
  • 3–10 min 17% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=4
  • 100% W n=5
  • 100% T n=4
  • 67% F n=3
  • 33% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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
12:50on time on time
12:52— —
12:59 / 13:00— —
13:08— —
13:14 / 13:15— —
13:23— —

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
Sat 21 NovVorden 13:33Partial coverage+5 min+5 min
Fri 20 NovVorden 13:33Partial coverage+4 min+4 min
Thu 19 NovVorden 13:29Partial coverage+1 min+1 min
Wed 18 NovVorden 13:29Partial coverage+1 min+1 min
Tue 17 NovVorden 13:29Partial coverage0 min—
Mon 16 NovVorden 13:30Partial coverage+1 min+1 min
Sun 15 NovVorden 13:30Partial coverage+2 min+2 min
Sat 14 NovVorden 13:42Partial coverage+14 min+14 min
Fri 13 NovVorden 13:29Partial coverage+1 min+1 min
Thu 12 NovVorden 13:29Partial coverage0 min—
Wed 11 NovVorden 13:32Partial coverage+3 min+3 min
Tue 10 NovVorden 13:29Partial coverage+1 min+1 min
Mon 9 NovVorden 13:29Partial coverage+1 min+1 min
Sun 8 NovVorden 13:29Partial coverage0 min—
Sat 7 NovVorden 13:33Partial coverage+3 min+4 min
Fri 6 NovVorden 13:29No data—
Thu 5 NovVorden 13:29No data—
Wed 4 NovVorden 13:29Partial coverage+1 min+1 min
Tue 3 NovVorden 13:29Partial coverage0 min—
Mon 2 NovVorden 13:29No data—
Sun 1 NovVorden 13:30Partial coverage0 min—
Sat 31 OctVorden 13:30Partial coverage+1 min+1 min
Fri 30 OctVorden 13:31No data—
Thu 29 OctVorden 13:29Partial coverage0 min—
Wed 28 OctVorden 13:29Partial coverage0 min—
Tue 27 OctVorden 13:30No data—
Mon 26 OctVorden 13:29No data—
Sun 25 OctVorden 13:30No data—
Sat 24 OctVorden 13:29Partial coverage0 min—
Fri 23 OctVorden 13:30No data—