Train RRReis A 30858 Winterswijk → Zutphen

Winterswijk 18:20 → Zutphen 18:53 Daily 0 h 33 min · 6 stops RRReis A

RRReis A 30858 Winterswijk–Zutphen: final delay under 3 min on 9 of its 14 runs with data in the last 30 days (64%). Median final delay: +2 min. TrainsRadar data as of 22 Nov 2026, 06:54 (GMT+1).

It does not run today

Last recorded run: Friday 20 November +6 min

Next service: tomorrow 18:20 from Winterswijk · Mon 23 Nov

Next departure 18:20 tomorrow · Winterswijk
On-time · 30 days
64%
9/14 runs under 3 min
RT coverage: 5 full · 9 partial · 4 no data
On-time · 90 days
68%
15/22 runs under 3 min
RT coverage: 8 full · 14 partial · 20 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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 20 Nov Max en route +6 min · last fix heading to Vorden +6 min
  • Fri 13 Nov Max en route +6 min · last fix heading to Vorden +6 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Lichtenvoorde-Groenlo +5 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Vorden +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Winterswijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 15
  • 3–10 min 32% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 75% T n=4
  • 100% W n=3
  • 50% T n=4
  • 20% 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, 22 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
18:20on time +1 min
18:22≈ on time ≈ +1 min
18:29 / 18:30≈ on time ≈ +1 min
18:38≈ +1 min ≈ +2 min
18:44 / 18:45≈ +1 min ≈ +2 min
18:53+1 min +3 min

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 19:03Partial coverage+6 min+6 min
Thu 19 NovLichtenvoorde-Groenlo 18:59Partial coverage+5 min+5 min
Wed 18 NovRuurlo 18:58Partial coverage+1 min+1 min
Tue 17 NovWinterswijk West 18:34Partial coverage+1 min+1 min
Mon 16 NovWinterswijk West 18:55Partial coverage+1 min+1 min
Fri 13 NovVorden 18:59Partial coverage+6 min+6 min
Thu 12 NovWinterswijk West 18:58Partial coverage+3 min+3 min
Wed 11 Nov— 18:57+2 min+2 min
Tue 10 NovWinterswijk 18:59Partial coverage+3 min+3 min
Mon 9 Nov— 18:540 min—
Fri 6 NovVorden 18:59Partial coverage+4 min+4 min
Thu 5 Nov— 18:54No data—
Wed 4 Nov— 18:54No data—
Mon 2 Nov— 18:54+1 min+1 min
Fri 30 OctVorden 18:59No data—
Thu 29 Oct— 18:59+3 min+3 min
Wed 28 Oct— 18:200 min—
Mon 26 Oct— 19:00No data—
Fri 23 OctVorden 18:59Partial coverage+3 min+3 min
Thu 22 OctVorden 18:59No data—
Wed 21 OctRuurlo 18:57No data—
Tue 20 OctVorden 18:57Partial coverage0 min—
Mon 19 OctRuurlo 18:57Partial coverage0 min—
Fri 16 OctVorden 18:59No data—
Thu 15 OctLichtenvoorde-Groenlo 18:44No data—
Wed 14 OctVorden 18:59No data—
Tue 13 OctRuurlo 18:50No data—
Mon 12 OctVorden 18:59Partial coverage0 min—
Fri 9 OctLichtenvoorde-Groenlo 18:56Partial coverage+1 min—
Thu 8 Oct— 18:59+3 min+3 min