Train RRReis A 30831 Zutphen – Winterswijk

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

✓ Today’s run finished

Today, last fix heading to Winterswijk West at 12:19 No data

  1. Zutphen11:37
  2. Vorden11:44
  3. Ruurlo11:51
  4. Lichtenvoorde-Groenlo11:59
  5. Winterswijk West12:07
  6. Winterswijk12:10

Next service: Monday 11:37 from Zutphen · Mon 9 Nov

Next departure 11:37 Monday · Zutphen
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 15 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 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 +9 min · last fix heading to Winterswijk West +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 10% · 1
  • 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
  • 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, 10 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
11:37on time +1 min
11:44 / 11:45— —
11:51— —
11:59 / 12:00— —
12:07— —
12:10— —

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 12:19No data—
Thu 5 NovWinterswijk West 12:22No data—
Wed 4 NovWinterswijk West 12:19Partial coverage0 min—
Tue 3 NovWinterswijk West 12:19No data—
Mon 2 NovWinterswijk West 12:22No data—
Fri 30 OctWinterswijk West 12:23No data—
Thu 29 OctWinterswijk West 12:21No data—
Wed 28 OctWinterswijk West 12:21Partial coverage0 min—
Tue 27 OctWinterswijk West 12:21Partial coverage0 min—
Mon 26 OctWinterswijk West 12:21No data—
Fri 23 OctWinterswijk West 12:23No data—
Thu 22 OctWinterswijk West 12:22No data—
Wed 21 OctWinterswijk West 12:25No data—
Tue 20 OctWinterswijk West 12:21Partial coverage0 min—
Mon 19 OctWinterswijk West 12:21Partial coverage0 min—
Fri 16 OctWinterswijk West 12:22No data—
Thu 15 OctWinterswijk West 12:21No data—
Wed 14 OctWinterswijk West 12:21No data—
Tue 13 OctWinterswijk West 12:23No data—
Mon 12 OctWinterswijk West 12:21No data—
Fri 9 OctWinterswijk West 12:24Partial coverage+2 min+2 min
Thu 8 OctWinterswijk West 12:21Partial coverage0 min—
Wed 7 OctWinterswijk West 12:23Partial coverage+1 min+2 min
Tue 6 OctWinterswijk West 12:21Partial coverage0 min—
Mon 5 OctWinterswijk West 12:30Partial coverage+9 min+9 min
Fri 2 OctWinterswijk West 12:23No data—
Thu 1 OctWinterswijk West 12:22No data—
Wed 30 SeptWinterswijk West 12:21No data—
Tue 29 SeptWinterswijk West 12:21No data—
Mon 28 SeptWinterswijk West 12:21No data—