Train Arriva 30862 Winterswijk – Zutphen

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

It has not run yet today

Last recorded run: Tuesday 17 November +2 min

Next service: today 19:20 from Winterswijk · Wed 18 Nov

Next departure 19:20 today · Winterswijk
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 15 full · 2 partial · 5 no data
On-time · 90 days
84%
21/25 runs under 3 min
RT coverage: 23 full · 2 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
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

  • Thu 8 Oct Max en route +13 min · last fix heading to — +13 min
  • Sun 15 Nov Max en route +9 min · last fix heading to Vorden +8 min
  • Fri 13 Nov Max en route +4 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Vorden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 21
  • 3–10 min 12% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 100% W n=1
  • 50% T n=2
  • 75% F n=4
  • 75% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 25 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
19:20on time on time
19:22≈ on time ≈ on time
19:29 / 19:30≈ on time ≈ +1 min
19:38≈ on time ≈ +2 min
19:44 / 19:45≈ on time ≈ +3 min
19: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
Tue 17 Nov— 19:58+2 min+2 min
Mon 16 Nov— 19:59+2 min+2 min
Sun 15 NovVorden 20:08+8 min+9 min
Sat 14 NovVorden 19:59+2 min+2 min
Fri 13 Nov— 19:48+4 min+4 min
Thu 12 Nov— 19:59+2 min+3 min
Tue 10 Nov— 19:570 min—
Mon 9 Nov— 19:540 min—
Sun 8 NovVorden 19:590 min+1 min
Sat 7 NovVorden 20:02+2 min+3 min
Fri 6 Nov— 19:57+1 min+1 min
Wed 4 Nov— 19:54+1 min—
Sun 1 NovVorden 20:03+3 min+4 min
Sat 31 OctVorden 20:000 min—
Fri 30 Oct— 19:58No data—
Wed 28 Oct— 19:57No data—
Tue 27 Oct— 19:58No data—
Mon 26 OctVorden 19:57Partial coverage0 min—
Sun 25 OctVorden 20:03No data—
Sat 24 OctVorden 20:05No data—
Fri 23 OctWinterswijk West 19:58Partial coverage+2 min+3 min
Tue 20 Oct— 19:560 min—
Mon 19 Oct— 19:550 min—
Sun 18 OctVorden 20:00+1 min—
Sat 17 OctVorden 20:02No data—
Fri 16 OctVorden 19:59No data—
Thu 15 Oct— 19:58No data—
Wed 14 OctVorden 19:59No data—
Tue 13 Oct— 19:57No data—
Mon 12 Oct— 19:580 min—