Train RRReis A 30878 Winterswijk – Zutphen

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

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 23:20 from Winterswijk · Sun 8 Nov

Next departure 23:20 today · Winterswijk
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 8 full · 0 partial · 13 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 10 full · 1 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 12 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 9% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
23:20on time on time
23:22≈ on time ≈ on time
23:29 / 23:30≈ on time ≈ +1 min
23:38≈ on time ≈ +1 min
23:44 / 23:45≈ on time ≈ +2 min
23: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
Sat 7 NovWinterswijk West 23:54No data—
Thu 5 Nov— 00:14No data—
Wed 4 Nov— 23:58+1 min+1 min
Sun 1 NovVorden 23:59+2 min+2 min
Sat 31 OctWinterswijk West 23:57No data—
Fri 30 Oct— 23:56No data—
Wed 28 Oct— 23:57No data—
Tue 27 Oct— 23:550 min—
Mon 26 Oct— 23:54No data—
Sun 25 OctVorden 00:01No data—
Sat 24 Oct— 00:01No data—
Fri 23 Oct— 23:52+1 min—
Tue 20 Oct— 00:02No data—
Mon 19 Oct— 23:58+2 min+2 min
Sun 18 OctVorden 23:590 min—
Sat 17 OctVorden 23:59No data—
Thu 15 Oct— 23:56No data—
Wed 14 Oct— 23:54No data—
Tue 13 Oct— 23:58No data—
Mon 12 Oct— 00:02+5 min+5 min
Sun 11 OctVorden 00:000 min—
Thu 8 Oct— 23:550 min—
Wed 7 Oct— 23:540 min—
Tue 6 Oct— 23:56No data—
Mon 5 OctVorden 00:14Partial coverage+1 min+1 min
Sun 4 OctVorden 23:59No data—
Sat 3 OctVorden 23:54No data—
Sun 27 SeptVorden 23:59No data—
Sat 26 SeptRuurlo 23:52No data—
Sun 20 SeptVorden 23:59No data—