Train RRReis A 30856 Winterswijk – Zutphen

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

Running now · updated 18:06

Heading to Zutphen 0 min

Estimated arrival at Zutphen 18:23 · 97 km/h

  1. Winterswijk17:50
  2. Winterswijk West17:52
  3. Lichtenvoorde-Groenlo17:59
  4. Ruurlo18:08
  5. Vorden18:14
  6. Zutphen18:23

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

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

  • Fri 9 Oct Max en route +3 min · last fix heading to Vorden +3 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Ruurlo +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 50% F n=2
  • 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, 17 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
17:50on time on time
17:52— —
17:59 / 18:00— —
18:08— —
18:14 / 18:15— —
18: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
Sat 7 NovRuurlo 18:04Partial coverage0 min—
Fri 6 NovVorden 18:29Partial coverage+2 min+2 min
Thu 5 NovRuurlo 18:27No data—
Wed 4 NovVorden 18:29Partial coverage0 min—
Tue 3 NovRuurlo 18:22No data—
Mon 2 NovRuurlo 18:22No data—
Sun 1 NovVorden 18:29Partial coverage+3 min+3 min
Sat 31 OctVorden 18:29Partial coverage0 min—
Fri 30 OctVorden 18:29No data—
Thu 29 OctLichtenvoorde-Groenlo 18:33No data—
Wed 28 OctRuurlo 18:27Partial coverage0 min—
Tue 27 OctLichtenvoorde-Groenlo 18:30No data—
Mon 26 OctRuurlo 18:29Partial coverage0 min—
Sun 25 OctVorden 18:29No data—
Sat 24 OctVorden 18:31No data—
Fri 23 OctVorden 18:32No data—
Thu 22 OctVorden 18:29No data—
Wed 21 OctVorden 18:29No data—
Tue 20 OctVorden 18:29Partial coverage0 min—
Mon 19 OctVorden 18:29Partial coverage0 min—
Sun 18 OctVorden 18:29No data—
Sat 17 OctVorden 18:29No data—
Fri 16 OctVorden 18:30No data—
Thu 15 OctVorden 18:29No data—
Wed 14 OctVorden 18:29No data—
Tue 13 OctVorden 18:29No data—
Mon 12 OctVorden 18:29Partial coverage0 min—
Sun 11 OctVorden 18:31Partial coverage+1 min+1 min
Sat 10 OctVorden 18:30Partial coverage+2 min+2 min
Fri 9 OctVorden 18:29Partial coverage+3 min+3 min