Train RRReis A 30833 Zutphen – Winterswijk

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

Running now · updated 12:55

Position estimated from the timetable

Heading to Winterswijk +3 min

Estimated arrival at Winterswijk 12:43 12:40

  1. Zutphen12:07
  2. Vorden12:14
  3. Ruurlo12:21
  4. Lichtenvoorde-Groenlo12:29
  5. Winterswijk West12:37
  6. Winterswijk12:40

Today it is running worse than usual: typical arrival delay is 0 min; 88% of the last 8 runs arrived on time.

On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 14 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 50 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

Worst days

  • Wed 11 Nov Max en route +3 min · last fix heading to Winterswijk West +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 75% W n=4
  • 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, 13 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 10Today
12:07on time on time
12:14 / 12:15— —
12:21— —
12:29 / 12:30— —
12:37— —
12: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
Wed 11 NovWinterswijk West 12:54Partial coverage+3 min+3 min
Tue 10 NovWinterswijk West 12:52Partial coverage+1 min+1 min
Mon 9 NovWinterswijk West 12:49Partial coverage0 min—
Fri 6 NovWinterswijk West 12:49No data—
Thu 5 NovWinterswijk West 12:52No data—
Wed 4 NovWinterswijk West 12:49Partial coverage0 min—
Tue 3 NovWinterswijk West 12:49No data—
Mon 2 NovWinterswijk West 12:49No data—
Fri 30 OctWinterswijk West 12:54No data—
Thu 29 OctWinterswijk West 12:51No data—
Wed 28 OctWinterswijk West 12:51Partial coverage0 min—
Tue 27 OctWinterswijk West 12:54Partial coverage0 min—
Mon 26 OctWinterswijk West 12:51No data—
Fri 23 OctWinterswijk West 12:57No data—
Thu 22 OctWinterswijk West 12:53No data—
Wed 21 OctWinterswijk West 12:54No data—
Tue 20 OctWinterswijk West 12:52Partial coverage0 min—
Mon 19 OctWinterswijk West 12:51Partial coverage0 min—
Fri 16 OctWinterswijk West 12:51No data—
Thu 15 OctWinterswijk West 12:51No data—
Wed 14 OctWinterswijk West 12:51No data—
Tue 13 OctWinterswijk West 12:52No data—
Mon 12 OctWinterswijk West 12:51No data—
Fri 9 OctWinterswijk West 12:51Partial coverage+1 min—
Thu 8 OctWinterswijk West 12:51Partial coverage0 min—
Wed 7 OctWinterswijk West 12:51Partial coverage+1 min—
Tue 6 OctWinterswijk West 12:52Partial coverage+1 min—
Mon 5 OctWinterswijk West 12:51Partial coverage0 min—
Fri 2 OctWinterswijk West 12:53No data—
Thu 1 OctWinterswijk West 12:52No data—