Train RRReis A 30870 Winterswijk → Zutphen

Winterswijk 21:20 → Zutphen 21:54 Daily 0 h 34 min · 6 stops RRReis A

RRReis A 30870 Winterswijk–Zutphen: final delay under 3 min on 13 of its 18 runs with data in the last 30 days (72%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 08:09 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +5 min

Next service: today 21:20 from Winterswijk · Sun 22 Nov

Next departure 21:20 today · Winterswijk
On-time · 30 days
72%
13/18 runs under 3 min
RT coverage: 12 full · 6 partial · 6 no data
On-time · 90 days
75%
21/28 runs under 3 min
RT coverage: 19 full · 9 partial · 21 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Mon 2 Nov Max en route +8 min · last fix heading to — +7 min
  • Sat 14 Nov Max en route +7 min · last fix heading to Vorden +7 min
  • Fri 9 Oct Max en route +7 min · last fix heading to — +6 min
  • Sat 21 Nov Max en route +5 min · last fix heading to Vorden +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +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 75% · 21
  • 3–10 min 25% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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 10
21:20on time on time
21:22≈ on time ≈ +1 min
21:29 / 21:30≈ on time ≈ +2 min
21:38≈ +1 min ≈ +3 min
21:44 / 21:45≈ +1 min ≈ +4 min
21:54+1 min +4 min

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 21 NovVorden 21:59Partial coverage+5 min+5 min
Fri 20 Nov— 21:57+1 min—
Thu 19 Nov— 21:540 min—
Tue 17 Nov— 21:59+3 min+3 min
Mon 16 NovRuurlo 21:570 min—
Sun 15 NovVorden 21:59Partial coverage0 min—
Sat 14 NovVorden 22:04Partial coverage+7 min+7 min
Thu 12 Nov— 21:540 min—
Wed 11 Nov— 21:57+1 min+1 min
Tue 10 Nov— 21:59+3 min+3 min
Sun 8 NovVorden 21:59Partial coverage0 min—
Sat 7 NovVorden 21:59Partial coverage0 min—
Fri 6 Nov— 21:59+3 min+3 min
Thu 5 Nov— 21:54No data—
Wed 4 Nov— 21:59+3 min+4 min
Mon 2 Nov— 22:03+7 min+8 min
Sun 1 NovVorden 21:59Partial coverage+1 min—
Sat 31 OctVorden 21:59No data—
Fri 30 Oct— 21:59No data—
Thu 29 Oct— 21:58+2 min+2 min
Tue 27 Oct— 21:590 min—
Mon 26 Oct— 22:00No data—
Sun 25 OctVorden 22:00No data—
Sat 24 OctVorden 21:59No data—
Thu 22 Oct— 21:57No data—
Wed 21 Oct— 21:57No data—
Mon 19 Oct— 21:570 min—
Sun 18 OctVorden 22:01Partial coverage+1 min+1 min
Sat 17 OctVorden 21:59No data—
Fri 16 Oct— 22:01+3 min+5 min