Train Arriva 30873 Zutphen → Winterswijk

Zutphen 22:07 → Winterswijk 22:40 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 6 stops Arriva

Arriva 30873 Zutphen–Winterswijk: final delay under 3 min on 9 of its 12 runs with data in the last 30 days (75%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 23:50 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 22:07 from Zutphen · Mon 23 Nov

Next departure 22:07 Monday · Zutphen
On-time · 30 days
75%
9/12 runs under 3 min
RT coverage: 12 full · 0 partial · 3 no data
On-time · 90 days
80%
16/20 runs under 3 min
RT coverage: 20 full · 0 partial · 7 no data
Typical delay
0min
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 Winterswijk, 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 17 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Mon 2 Nov Max en route +6 min · last fix heading to — +5 min
  • Tue 10 Nov Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 16
  • 3–10 min 20% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:07on time +2 min
22:14 / 22:15≈ on time ≈ +2 min
22:21≈ on time ≈ +2 min
22:29 / 22:30≈ on time ≈ +4 min
22:37≈ on time ≈ +5 min
22:40on time +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
Fri 20 Nov— 22:430 min—
Thu 19 Nov— 22:390 min—
Tue 17 Nov— 22:49+8 min+8 min
Mon 16 Nov— 22:430 min—
Thu 12 Nov— 22:420 min—
Wed 11 Nov— 22:430 min—
Tue 10 Nov— 22:44+4 min+5 min
Fri 6 Nov— 22:44+2 min+2 min
Thu 5 Nov— 22:44No data—
Wed 4 Nov— 22:44+2 min+2 min
Mon 2 Nov— 22:47+5 min+6 min
Fri 30 Oct— 22:44No data—
Thu 29 Oct— 22:410 min—
Tue 27 Oct— 22:44No data—
Mon 26 Oct— 22:450 min—
Thu 22 Oct— 22:43No data—
Wed 21 Oct— 22:43No data—
Tue 20 Oct— 22:450 min—
Mon 19 Oct— 22:420 min—
Fri 16 Oct— 22:45+3 min+3 min
Thu 15 Oct— 22:45No data—
Tue 13 Oct— 22:42No data—
Mon 12 Oct— 22:46+2 min+2 min
Fri 9 Oct— 22:47+5 min+5 min
Thu 8 Oct— 22:45+2 min+2 min
Wed 7 Oct— 22:410 min—
Mon 5 Oct— 22:420 min—