Train Arriva 30866 Winterswijk – Zutphen

Winterswijk 20:20 → Zutphen 20:54 Daily 0 h 34 min · 6 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 20:20 from Winterswijk · Sat 7 Nov

Next departure 20:20 today · Winterswijk
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 12 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 30 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: +4 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 16 Oct Max en route +6 min · last fix heading to — +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Vorden +4 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

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

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 10
20:20on time on time
20:22≈ on time ≈ on time
20:29 / 20:30≈ on time ≈ +1 min
20:38≈ on time ≈ +2 min
20:44 / 20:45≈ on time ≈ +2 min
20:54on time +3 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
Thu 5 Nov— 20:55No data—
Wed 4 Nov— 20:540 min—
Mon 2 Nov— 20:58No data—
Sun 1 NovVorden 21:03+4 min+4 min
Sat 31 OctVorden 20:590 min—
Fri 30 Oct— 20:59No data—
Thu 29 Oct— 20:560 min—
Wed 28 Oct— 21:010 min—
Tue 27 Oct— 20:570 min—
Mon 26 Oct— 21:04No data—
Sun 25 OctVorden 21:02No data—
Sat 24 OctVorden 21:09No data—
Fri 23 Oct— 21:03+3 min+3 min
Thu 22 Oct— 20:58No data—
Wed 21 Oct— 20:59No data—
Tue 20 Oct— 20:570 min—
Mon 19 Oct— 20:570 min—
Sun 18 OctVorden 21:000 min—
Sat 17 OctVorden 21:00No data—
Fri 16 Oct— 21:02+5 min+6 min
Thu 15 Oct— 21:03No data—
Wed 14 Oct— 20:58No data—
Tue 13 Oct— 20:56No data—
Mon 12 Oct— 20:570 min—
Sun 11 OctVorden 21:03+3 min+4 min
Sat 10 OctVorden 21:00+1 min—
Thu 8 Oct— 20:58+1 min+2 min
Wed 7 Oct— 20:58+2 min+3 min
Mon 5 Oct— 20:570 min—
Sun 4 OctVorden 21:00No data—