Train RRReis A 30840 Winterswijk – Zutphen

Winterswijk 13:50 → Zutphen 14:23 Daily 0 h 33 min · 6 stops RRReis A

Running now · updated 13:48

Position estimated from the timetable

Heading to Zutphen 0 min

Estimated arrival at Zutphen 14:23

  1. Winterswijk13:50
  2. Winterswijk West13:52
  3. Lichtenvoorde-Groenlo13:59
  4. Ruurlo14:08
  5. Vorden14:14
  6. Zutphen14:23

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

On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 1 full · 18 partial · 11 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 1 full · 27 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +2 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

Worst days

  • Sat 14 Nov Max en route +10 min · last fix heading to Winterswijk +10 min
  • Sun 11 Oct Max en route +6 min · last fix heading to Vorden +6 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Vorden +5 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Vorden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 67% F n=3
  • 80% S n=5
  • 67% S n=3

Stops and timetable

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

Last 90 days, 28 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
13:50on time on time
13:52— —
13:59 / 14:00— —
14:08— —
14:14 / 14:15— —
14:23— —

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 13:45Partial coverage0 min—
Thu 19 NovVorden 14:29Partial coverage+1 min+1 min
Wed 18 NovVorden 14:29Partial coverage0 min—
Tue 17 NovVorden 14:29Partial coverage0 min—
Mon 16 NovVorden 14:30Partial coverage+1 min+1 min
Sun 15 NovVorden 14:30Partial coverage+3 min+3 min
Sat 14 NovWinterswijk 14:49+10 min+10 min
Fri 13 NovVorden 14:29Partial coverage+1 min—
Thu 12 NovVorden 14:29Partial coverage0 min—
Wed 11 NovVorden 14:29Partial coverage0 min—
Tue 10 NovVorden 14:29Partial coverage+1 min+1 min
Mon 9 NovVorden 14:29Partial coverage+1 min+1 min
Sun 8 NovVorden 14:30Partial coverageNo data—
Sat 7 NovVorden 14:29Partial coverage+2 min+3 min
Fri 6 NovVorden 14:29No data—
Thu 5 NovVorden 14:29No data—
Wed 4 NovVorden 14:29Partial coverage0 min—
Tue 3 NovVorden 14:29No data—
Mon 2 NovVorden 14:29No data—
Sun 1 NovVorden 14:30Partial coverage0 min—
Sat 31 OctVorden 14:30Partial coverage+1 min+1 min
Fri 30 OctVorden 14:29No data—
Thu 29 OctVorden 14:29No data—
Wed 28 OctVorden 14:29Partial coverage0 min—
Tue 27 OctVorden 14:30Partial coverage0 min—
Mon 26 OctVorden 14:29No data—
Sun 25 OctVorden 14:30No data—
Sat 24 OctVorden 14:29Partial coverage0 min—
Fri 23 OctVorden 14:37No data—
Thu 22 OctVorden 14:29No data—