Train Arriva 30872 Winterswijk – Zutphen

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

It has not run yet today

Last recorded run: Tuesday 17 November +5 min

Next service: today 21:50 from Winterswijk · Thu 19 Nov

Next departure 21:50 today · Winterswijk
On-time · 30 days
70%
7/10 runs under 3 min
RT coverage: 10 full · 0 partial · 6 no data
On-time · 90 days
76%
13/17 runs under 3 min
RT coverage: 17 full · 0 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Mon 2 Nov Max en route +8 min · last fix heading to — +7 min
  • Tue 17 Nov 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
  • Wed 4 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 13
  • 3–10 min 24% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 75% T n=4
  • 50% W n=2
  • 100% T n=3
  • 50% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

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