Train Arriva 30864 Winterswijk – Zutphen

Winterswijk 19:50 → Zutphen 20:23 Daily 0 h 33 min · 6 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 19:50 from Winterswijk · Fri 20 Nov

Next departure 19:50 today · Winterswijk
On-time · 30 days
81%
13/16 runs under 3 min
RT coverage: 10 full · 6 partial · 7 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 13 full · 9 partial · 24 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Sun 15 Nov Max en route +14 min · last fix heading to Vorden +13 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Vorden +4 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Vorden +4 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Vorden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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:50on time on time
19:52≈ on time ≈ on time
19:59 / 20:00≈ on time ≈ on time
20:08≈ on time ≈ +1 min
20:14 / 20:15≈ on time ≈ +1 min
20:23on time +2 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 19 Nov— 20:27+1 min+2 min
Wed 18 Nov— 20:28+2 min+2 min
Mon 16 Nov— 20:240 min—
Sun 15 NovVorden 20:43Partial coverage+13 min+14 min
Sat 14 NovVorden 20:29Partial coverage0 min—
Thu 12 Nov— 20:24+2 min+2 min
Wed 11 Nov— 20:240 min—
Tue 10 Nov— 20:270 min—
Mon 9 Nov— 20:24No data—
Sun 8 NovVorden 20:29Partial coverage+1 min—
Sat 7 NovVorden 20:32Partial coverage+3 min+4 min
Fri 6 Nov— 20:240 min—
Thu 5 Nov— 20:25No data—
Wed 4 Nov— 20:24+1 min+1 min
Mon 2 Nov— 20:27No data—
Sun 1 NovVorden 20:33Partial coverage+4 min+4 min
Sat 31 OctVorden 20:30Partial coverage+1 min+2 min
Thu 29 Oct— 20:270 min—
Mon 26 Oct— 20:26No data—
Sun 25 OctVorden 20:33No data—
Sat 24 OctVorden 20:37No data—
Fri 23 Oct— 20:27+1 min+1 min
Thu 22 Oct— 20:28No data—
Wed 21 Oct— 20:26No data—
Tue 20 Oct— 20:270 min—
Mon 19 Oct— 20:25No data—
Sun 18 OctVorden 20:29Partial coverage0 min—
Sat 17 OctVorden 20:32No data—
Fri 16 OctWinterswijk West 20:29No data—
Wed 14 Oct— 20:25No data—