Train Arriva 30874 Winterswijk → Zutphen

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

It has not run yet today

Last recorded run: Friday 20 November +2 min

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

Next departure 22:20 today · Winterswijk
On-time · 30 days
71%
12/17 runs under 3 min
RT coverage: 15 full · 2 partial · 7 no data
On-time · 90 days
64%
16/25 runs under 3 min
RT coverage: 23 full · 2 partial · 24 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +8 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 23 Oct Max en route +12 min · last fix heading to — +12 min
  • Tue 17 Nov Max en route +10 min · last fix heading to — +10 min
  • Mon 12 Oct Max en route +8 min · last fix heading to — +7 min
  • Mon 2 Nov Max en route +7 min · last fix heading to — +7 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 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 64% · 16
  • 3–10 min 32% · 8
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=3
  • 0% T n=1
  • 100% W n=4
  • 100% T n=4
  • 40% F n=5
  • 100% S n=3
  • 40% 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
22:20on time on time
22:22≈ on time ≈ on time
22:29 / 22:30≈ +1 min ≈ +2 min
22:38≈ +1 min ≈ +4 min
22:44 / 22:45≈ +1 min ≈ +5 min
22:54+2 min +7 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
Fri 20 Nov— 22:59+2 min+2 min
Thu 19 Nov— 22:540 min—
Wed 18 Nov— 22:540 min—
Tue 17 Nov— 23:04+10 min+10 min
Mon 16 Nov— 22:59+2 min+2 min
Sun 15 NovVorden 23:03+4 min+4 min
Sat 14 NovVorden 22:59Partial coverage+2 min+2 min
Thu 12 Nov— 22:57+1 min—
Wed 11 Nov— 22:540 min—
Sun 8 NovVorden 22:59+2 min+2 min
Sat 7 NovVorden 22:59Partial coverage0 min—
Fri 6 Nov— 22:540 min+1 min
Thu 5 Nov— 22:57No data—
Wed 4 Nov— 22:54+1 min+1 min
Mon 2 Nov— 23:03+7 min+7 min
Sun 1 NovVorden 23:04+4 min+5 min
Sat 31 OctVorden 22:59No data—
Fri 30 Oct— 22:58No data—
Thu 29 Oct— 22:59+2 min+3 min
Wed 28 Oct— 22:56No data—
Mon 26 Oct— 23:00No data—
Sun 25 OctVorden 22:59No data—
Sat 24 OctRuurlo 22:58No data—
Fri 23 Oct— 23:09+12 min+12 min
Thu 22 Oct— 22:58No data—
Wed 21 Oct— 23:00No data—
Tue 20 Oct— 23:01No data—
Sun 18 OctVorden 23:03+3 min+3 min
Sat 17 OctVorden 22:59No data—
Fri 16 Oct— 23:01+4 min+4 min