Train Arriva 30860 Winterswijk – Zutphen

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:50 from Winterswijk · Thu 5 Nov

Next departure 18:50 today · Winterswijk
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 8 full · 6 partial · 13 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 9 full · 6 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Thu 8 Oct Max en route +9 min · last fix heading to — +9 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Vorden +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 13
  • 3–10 min 13% · 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=2
  • 50% T n=2
  • 100% F n=1
  • 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, 15 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
18:50on time on time
18:52≈ on time ≈ on time
18:59 / 19:00≈ on time ≈ +1 min
19:08≈ on time ≈ +1 min
19:14 / 19:15≈ on time ≈ +2 min
19: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
Wed 4 Nov— 19:240 min—
Mon 2 Nov— 19:240 min—
Sun 1 NovVorden 19:34Partial coverage+5 min+5 min
Sat 31 OctVorden 19:29Partial coverage0 min—
Fri 30 OctWinterswijk West 19:26No data—
Thu 29 Oct— 19:260 min—
Wed 28 Oct— 19:26No data—
Tue 27 Oct— 19:300 min—
Mon 26 Oct— 19:27No data—
Sun 25 OctVorden 19:29No data—
Sat 24 OctVorden 19:32No data—
Fri 23 OctVorden 19:30Partial coverage+1 min+1 min
Thu 22 Oct— 19:26No data—
Wed 21 Oct— 19:27No data—
Tue 20 Oct— 19:260 min—
Mon 19 Oct— 19:26No data—
Sun 18 OctVorden 19:29Partial coverage0 min—
Sat 17 OctVorden 19:29No data—
Fri 16 OctVorden 19:29No data—
Thu 15 Oct— 19:27No data—
Wed 14 OctVorden 19:38No data—
Tue 13 Oct— 19:26No data—
Mon 12 Oct— 19:270 min—
Sun 11 OctVorden 19:30Partial coverage+1 min+1 min
Sat 10 OctVorden 19:31Partial coverage+2 min+3 min
Thu 8 Oct— 19:36+9 min+9 min
Wed 7 Oct— 19:250 min—
Mon 5 Oct— 19:27+1 min—
Sun 4 OctVorden 19:31No data—
Sat 3 OctVorden 19:30No data—