Train RRReis A 30829 Zutphen → Winterswijk

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

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 11:07 from Zutphen · Mon 23 Nov

Next departure 11:07 Monday · Zutphen
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 8 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 0 full · 19 partial · 45 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: +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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:07on time on time
11:14 / 11:15— —
11:21— —
11:29 / 11:30— —
11:37— —
11: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 20 NovWinterswijk West 11:52Partial coverage0 min—
Thu 19 NovWinterswijk West 11:52Partial coverage0 min—
Wed 18 NovWinterswijk West 11:49Partial coverage0 min—
Tue 17 NovWinterswijk West 11:52Partial coverage+1 min+2 min
Mon 16 NovWinterswijk West 11:54Partial coverage+1 min+2 min
Fri 13 NovWinterswijk West 11:49Partial coverage0 min—
Thu 12 NovWinterswijk West 11:49Partial coverage0 min—
Wed 11 NovWinterswijk West 11:49Partial coverage0 min—
Tue 10 NovWinterswijk West 11:54Partial coverage+3 min+3 min
Mon 9 NovWinterswijk West 11:49Partial coverage0 min—
Fri 6 NovWinterswijk West 11:49No data—
Thu 5 NovWinterswijk West 11:54No data—
Wed 4 NovWinterswijk West 11:49Partial coverage0 min—
Tue 3 NovWinterswijk West 11:49No data—
Mon 2 NovWinterswijk West 11:52No data—
Fri 30 OctWinterswijk West 11:53No data—
Thu 29 OctWinterswijk West 11:51No data—
Wed 28 OctWinterswijk West 11:52Partial coverage0 min—
Tue 27 OctWinterswijk West 11:51Partial coverage0 min—
Mon 26 OctWinterswijk West 11:51No data—
Fri 23 OctWinterswijk West 11:53No data—
Thu 22 OctWinterswijk West 11:53No data—
Wed 21 OctWinterswijk West 11:55No data—
Tue 20 OctWinterswijk West 11:54Partial coverage0 min—
Mon 19 OctWinterswijk West 11:51Partial coverage0 min—
Fri 16 OctWinterswijk West 11:51No data—
Thu 15 OctWinterswijk West 11:51No data—
Wed 14 OctWinterswijk West 11:51No data—
Tue 13 OctWinterswijk West 11:52No data—
Mon 12 OctWinterswijk West 11:51No data—