Train RRReis A 30848 Winterswijk → Zutphen

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 15:50 from Winterswijk · Sat 21 Nov

Next departure 15:50 today · Winterswijk
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 0 full · 20 partial · 9 no data
On-time · 90 days
83%
25/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
+5min
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

  • Thu 19 Nov 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
  • Fri 9 Oct Max en route +5 min · last fix heading to Vorden +5 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Vorden +5 min
  • Tue 17 Nov 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 83% · 25
  • 3–10 min 17% · 5
  • 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
  • 75% T n=4
  • 67% F n=3
  • 100% S n=4
  • 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
15:50on time on time
15:52— —
15:59 / 16:00— —
16:08— —
16:14 / 16:15— —
16: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 16:30Partial coverage0 min—
Thu 19 NovVorden 16:34Partial coverage+6 min+6 min
Wed 18 NovVorden 16:29Partial coverage+2 min+2 min
Tue 17 NovVorden 16:33Partial coverage+4 min+4 min
Mon 16 NovVorden 16:34Partial coverage+5 min+5 min
Sun 15 NovVorden 16:29Partial coverage0 min—
Sat 14 NovVorden 16:29Partial coverage+2 min+2 min
Fri 13 NovVorden 16:29Partial coverage+3 min+3 min
Thu 12 NovVorden 16:29Partial coverage+1 min+2 min
Wed 11 NovVorden 16:29Partial coverage+1 min+1 min
Tue 10 NovVorden 16:29Partial coverage+1 min+1 min
Mon 9 NovVorden 16:29Partial coverage+1 min+1 min
Sun 8 NovVorden 16:30Partial coverage0 min—
Sat 7 NovVorden 16:29Partial coverage0 min—
Fri 6 NovVorden 16:29No data—
Thu 5 NovVorden 16:29No data—
Wed 4 NovVorden 16:29Partial coverage0 min—
Tue 3 NovVorden 16:32No data—
Mon 2 NovVorden 16:29No data—
Sun 1 NovVorden 16:32Partial coverage+2 min+2 min
Sat 31 OctVorden 16:29Partial coverage0 min—
Fri 30 OctVorden 16:30No data—
Thu 29 OctVorden 16:30Partial coverage0 min—
Wed 28 OctVorden 16:29Partial coverage0 min—
Tue 27 OctVorden 16:30Partial coverage0 min—
Mon 26 OctVorden 16:30No data—
Sun 25 OctVorden 16:31No data—
Sat 24 OctVorden 16:29No data—
Fri 23 OctVorden 16:30No data—
Thu 22 OctVorden 16:29No data—