Train RRReis A 30816 Winterswijk – Zutphen

Winterswijk 07:47 → Zutphen 08:21 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 6 stops RRReis A

Running now · updated 07:43

Heading to Zutphen No data

Estimated arrival at Zutphen 08:21 · 12 km/h

  1. Winterswijk07:47
  2. Winterswijk West07:49
  3. Lichtenvoorde-Groenlo07:56
  4. Ruurlo08:05
  5. Vorden08:11
  6. Zutphen08:21
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 10 no data
On-time · 90 days
100%
13/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
+2min
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

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 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 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, 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
07:47on time on time
07:49— —
07:56 / 07:57— —
08:05— —
08:11 / 08:12— —
08:21— —

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
Thu 5 NovWinterswijk 07:39No data—
Wed 4 NovVorden 08:29Partial coverage+3 min+3 min
Tue 3 NovVorden 08:28No data—
Mon 2 NovVorden 08:27No data—
Fri 30 OctVorden 08:31Partial coverage0 min—
Thu 29 OctVorden 08:26Partial coverage0 min—
Wed 28 OctVorden 08:28Partial coverage0 min—
Tue 27 OctVorden 08:29Partial coverage0 min—
Mon 26 OctVorden 08:28Partial coverage0 min—
Fri 23 OctVorden 08:27Partial coverage0 min—
Thu 22 OctVorden 08:26No data—
Wed 21 OctVorden 08:29No data—
Tue 20 OctVorden 08:26Partial coverage0 min—
Mon 19 OctVorden 08:26Partial coverage0 min—
Fri 16 OctVorden 08:28No data—
Thu 15 OctVorden 08:31No data—
Wed 14 OctVorden 08:27No data—
Tue 13 OctVorden 08:31No data—
Mon 12 OctVorden 08:28No data—
Fri 9 OctVorden 08:28Partial coverage+1 min+2 min
Thu 8 OctVorden 08:29Partial coverage+2 min+2 min
Wed 7 OctVorden 08:27Partial coverage0 min—
Tue 6 OctVorden 08:29Partial coverage+2 min+3 min
Mon 5 OctVorden 08:29No data—
Fri 2 OctVorden 08:27No data—
Thu 1 OctVorden 08:29No data—
Wed 30 SeptVorden 08:27No data—
Tue 29 SeptVorden 08:27No data—
Mon 28 SeptVorden 08:27No data—
Fri 25 SeptVorden 08:28No data—