Train RRReis A 30815 Zutphen – Winterswijk

Zutphen 07:32 → Winterswijk 08:07 Mon, Tue, Wed, Thu, Fri, Sat 0 h 35 min · 6 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Winterswijk West at 08:24 No data

  1. Zutphen07:32
  2. Vorden07:40
  3. Ruurlo07:48
  4. Lichtenvoorde-Groenlo07:56
  5. Winterswijk West08:04
  6. Winterswijk08:07

Next service: tomorrow 07:32 from Zutphen · Fri 6 Nov

Next departure 07:32 tomorrow · Zutphen
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 5 full · 11 partial · 10 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 5 full · 12 partial · 60 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sat 24 Oct Max en route +23 min · last fix heading to Winterswijk West +23 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Winterswijk West +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
07:32on time on time
07:40 / 07:41≈ on time ≈ +3 min
07:48≈ on time ≈ +7 min
07:56 / 07:57≈ on time ≈ +10 min
08:04≈ on time ≈ +13 min
08:07on time +14 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
Thu 5 NovWinterswijk West 08:24No data—
Wed 4 NovWinterswijk West 08:22Partial coverage+4 min+4 min
Tue 3 NovWinterswijk West 08:19No data—
Mon 2 NovWinterswijk West 08:18No data—
Sat 31 OctWinterswijk West 08:220 min—
Fri 30 OctWinterswijk West 08:23Partial coverage+1 min—
Thu 29 OctWinterswijk West 08:18Partial coverage0 min—
Wed 28 OctWinterswijk West 08:18Partial coverage0 min—
Tue 27 OctWinterswijk West 08:21No data—
Mon 26 OctWinterswijk West 08:19Partial coverage+1 min—
Sat 24 OctWinterswijk West 08:50+23 min+23 min
Fri 23 OctWinterswijk West 08:19Partial coverage+2 min+2 min
Thu 22 OctWinterswijk West 08:18No data—
Wed 21 OctWinterswijk West 08:18No data—
Tue 20 OctWinterswijk West 08:18Partial coverage0 min—
Mon 19 OctWinterswijk West 08:180 min—
Sat 17 OctWinterswijk West 08:23+1 min+1 min
Fri 16 OctWinterswijk West 08:18No data—
Thu 15 OctWinterswijk West 08:22Partial coverage0 min—
Wed 14 OctWinterswijk West 08:22No data—
Tue 13 OctWinterswijk West 08:22No data—
Mon 12 OctWinterswijk West 08:18No data—
Sat 10 OctWinterswijk West 08:210 min—
Fri 9 OctWinterswijk West 08:20Partial coverage+2 min+2 min
Thu 8 OctWinterswijk West 08:20Partial coverage+1 min+2 min
Wed 7 OctWinterswijk West 08:18Partial coverage0 min—
Tue 6 OctWinterswijk West 08:20Partial coverage+2 min+2 min
Mon 5 OctWinterswijk West 08:19No data—
Sat 3 OctWinterswijk West 08:21No data—
Fri 2 OctWinterswijk West 08:18No data—