Train RRReis A 30849 Zutphen – Winterswijk

Zutphen 16:07 → Winterswijk 16:40 Daily 0 h 33 min · 6 stops RRReis A

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 16:07 from Zutphen · Sat 7 Nov

Next departure 16:07 today · Zutphen
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 0 full · 12 partial · 17 no data
On-time · 90 days
81%
13/16 runs under 3 min
RT coverage: 0 full · 16 partial · 72 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Winterswijk, 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 5 Oct Max en route +4 min · last fix heading to Winterswijk West +4 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Winterswijk West +4 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Winterswijk West +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 13
  • 3–10 min 19% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 0% F n=1
  • 100% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 16 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:07on time on time
16:14 / 16:15— —
16:21— —
16:29 / 16:30— —
16:37— —
16:40— —

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 6 NovWinterswijk West 16:49No data—
Thu 5 NovWinterswijk West 16:52No data—
Wed 4 NovWinterswijk West 16:53Partial coverage0 min—
Tue 3 NovWinterswijk West 16:53No data—
Mon 2 NovWinterswijk West 16:49No data—
Sun 1 NovWinterswijk West 16:52Partial coverage+1 min+1 min
Sat 31 OctWinterswijk West 16:51Partial coverage0 min—
Fri 30 OctWinterswijk West 16:52No data—
Thu 29 OctWinterswijk West 16:51No data—
Wed 28 OctWinterswijk West 16:48Partial coverage0 min—
Tue 27 OctWinterswijk West 16:51Partial coverage0 min—
Mon 26 OctWinterswijk West 16:52No data—
Sun 25 OctWinterswijk West 16:51No data—
Sat 24 OctWinterswijk West 16:51Partial coverage0 min—
Fri 23 OctWinterswijk West 16:52No data—
Thu 22 OctWinterswijk West 16:51No data—
Wed 21 OctWinterswijk West 16:51No data—
Tue 20 OctWinterswijk West 16:51Partial coverage0 min—
Mon 19 OctWinterswijk West 16:51No data—
Sun 18 OctWinterswijk West 16:55Partial coverage+4 min+4 min
Sat 17 OctWinterswijk West 16:52No data—
Fri 16 OctWinterswijk West 16:53No data—
Thu 15 OctWinterswijk West 16:53No data—
Wed 14 OctWinterswijk West 16:51No data—
Tue 13 OctWinterswijk West 16:51No data—
Mon 12 OctWinterswijk West 16:52Partial coverage+1 min+2 min
Sun 11 OctWinterswijk West 16:52Partial coverage0 min+1 min
Sat 10 OctWinterswijk West 16:51Partial coverage0 min—
Fri 9 OctWinterswijk West 16:56Partial coverage+4 min+5 min
Thu 8 OctWinterswijk West 16:51Partial coverage0 min+1 min