Train Arriva 30868 Winterswijk – Zutphen

Winterswijk 20:50 → Zutphen 21:23 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 6 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

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

Next departure 20:50 today · Winterswijk
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 6 no data
On-time · 90 days
67%
8/12 runs under 3 min
RT coverage: 12 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Tue 6 Oct Max en route +7 min · last fix heading to — +6 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 8
  • 3–10 min 33% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 67% T n=3
  • 100% W n=2
  • 100% T n=1
  • 33% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 12 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:50on time +2 min
20:52≈ on time ≈ +2 min
20:59 / 21:00≈ on time ≈ +3 min
21:08≈ on time ≈ +4 min
21:14 / 21:15≈ on time ≈ +4 min
21:23+1 min +5 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— 21:24No data—
Wed 4 Nov— 21:240 min—
Fri 30 Oct— 21:29No data—
Wed 28 Oct— 21:310 min—
Tue 27 Oct— 21:250 min—
Mon 26 Oct— 21:32No data—
Fri 23 Oct— 21:31+5 min+5 min
Tue 20 Oct— 21:280 min—
Mon 19 Oct— 21:260 min—
Fri 16 Oct— 21:31+5 min+5 min
Thu 15 Oct— 21:33No data—
Wed 14 Oct— 21:27No data—
Tue 13 Oct— 21:25No data—
Mon 12 Oct— 21:260 min—
Fri 9 Oct— 21:27+1 min+1 min
Thu 8 Oct— 21:28+3 min+3 min
Tue 6 Oct— 21:28+6 min+7 min
Mon 5 Oct— 21:29+3 min+3 min