Train RRReis A 30852 Winterswijk – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Vorden at 17:29 0 min

  1. Winterswijk16:50
  2. Winterswijk West16:52
  3. Lichtenvoorde-Groenlo16:59
  4. Ruurlo17:08
  5. Vorden17:14
  6. Zutphen17:23

Next service: tomorrow 16:50 from Winterswijk · Sat 21 Nov

Next departure 16:50 tomorrow · Winterswijk
On-time · 30 days
70%
14/20 runs under 3 min
RT coverage: 0 full · 20 partial · 10 no data
On-time · 90 days
63%
19/30 runs under 3 min
RT coverage: 0 full · 30 partial · 57 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 16 Nov Max en route +7 min · last fix heading to Vorden +7 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Vorden +5 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Vorden +5 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Vorden +5 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Vorden +4 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 63% · 19
  • 3–10 min 37% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=4
  • 80% T n=5
  • 100% W n=5
  • 67% T n=3
  • 50% F n=4
  • 25% S n=4
  • 60% 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
16:50on time on time
16:52— —
16:59 / 17:00— —
17:08— —
17:14 / 17:15— —
17: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
Fri 20 NovVorden 17:29Partial coverage0 min—
Thu 19 NovVorden 17:29Partial coverage+5 min+5 min
Wed 18 NovVorden 17:29Partial coverage+1 min+1 min
Tue 17 NovVorden 17:29Partial coverage0 min—
Mon 16 NovVorden 17:34Partial coverage+7 min+7 min
Sun 15 NovVorden 17:29Partial coverage0 min—
Sat 14 NovVorden 17:32Partial coverage+4 min+4 min
Fri 13 NovVorden 17:32Partial coverage+4 min+4 min
Thu 12 NovVorden 17:29Partial coverage+1 min+1 min
Wed 11 NovVorden 17:29Partial coverage0 min—
Tue 10 NovVorden 17:29Partial coverage+3 min+3 min
Mon 9 NovVorden 17:29Partial coverage0 min—
Sun 8 NovVorden 17:29Partial coverage0 min—
Sat 7 NovVorden 17:32Partial coverage+5 min+5 min
Fri 6 NovVorden 17:29Partial coverage0 min—
Thu 5 NovVorden 17:29No data—
Wed 4 NovVorden 17:29Partial coverage0 min—
Tue 3 NovVorden 17:29No data—
Mon 2 NovVorden 17:29No data—
Sun 1 NovVorden 17:31Partial coverage+3 min+3 min
Sat 31 OctVorden 17:31Partial coverage+3 min+4 min
Fri 30 OctVorden 17:30No data—
Thu 29 OctVorden 17:29No data—
Wed 28 OctVorden 17:29Partial coverage0 min—
Tue 27 OctVorden 17:29Partial coverage0 min—
Mon 26 OctVorden 17:29No data—
Sun 25 OctVorden 17:29No data—
Sat 24 OctVorden 17:29No data—
Fri 23 OctVorden 17:32No data—
Thu 22 OctVorden 17:31No data—