Train RRReis A 30826 Winterswijk – Zutphen

Winterswijk 10:20 → Zutphen 10:53 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 6 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Vorden at 11:04 No data

  1. Winterswijk10:20
  2. Winterswijk West10:22
  3. Lichtenvoorde-Groenlo10:29
  4. Ruurlo10:38
  5. Vorden10:44
  6. Zutphen10:53

Next service: tomorrow 10:20 from Winterswijk · Fri 6 Nov

Next departure 10:20 tomorrow · Winterswijk
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 1 full · 7 partial · 14 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 1 full · 8 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
10:20on time on time
10:22— —
10:29 / 10:30— —
10:38— —
10:44 / 10:45— —
10:53— —

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 NovVorden 11:04No data—
Wed 4 NovVorden 10:59Partial coverage0 min—
Tue 3 NovVorden 10:59No data—
Mon 2 NovVorden 10:59No data—
Fri 30 OctVorden 11:03No data—
Thu 29 OctVorden 10:59No data—
Wed 28 OctVorden 10:59Partial coverage0 min—
Tue 27 OctVorden 10:59Partial coverage0 min—
Mon 26 OctVorden 11:00No data—
Fri 23 OctVorden 11:03No data—
Thu 22 OctVorden 11:03No data—
Wed 21 OctVorden 11:08No data—
Tue 20 OctVorden 11:02Partial coverage0 min—
Mon 19 OctVorden 10:59Partial coverage0 min—
Fri 16 OctVorden 11:00No data—
Thu 15 OctVorden 11:01No data—
Wed 14 OctVorden 10:59No data—
Tue 13 OctVorden 10:59No data—
Mon 12 OctVorden 10:59No data—
Fri 9 OctVorden 11:00Partial coverage+1 min+1 min
Thu 8 OctVorden 10:59Partial coverage0 min—
Wed 7 OctRuurlo 12:000 min—
Tue 6 OctVorden 11:01Partial coverage+2 min+2 min
Mon 5 OctVorden 11:02No data—
Fri 2 OctVorden 11:00No data—
Thu 1 OctVorden 11:01No data—
Wed 30 SeptVorden 11:00No data—
Tue 29 SeptVorden 11:01No data—
Mon 28 SeptVorden 11:00No data—
Fri 25 SeptVorden 10:59No data—