Train RRReis A 30841 Zutphen – Winterswijk

Zutphen 14:07 → Winterswijk 14:40 Daily 0 h 33 min · 6 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Winterswijk West at 14:50 0 min

  1. Zutphen14:07
  2. Vorden14:14
  3. Ruurlo14:21
  4. Lichtenvoorde-Groenlo14:29
  5. Winterswijk West14:37
  6. Winterswijk14:40

Next service: tomorrow 14:07 from Zutphen · Sun 8 Nov

Next departure 14:07 tomorrow · Zutphen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 19 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 74 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

  • Mon 5 Oct Max en route +7 min · last fix heading to Winterswijk West +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

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