Train Arriva 30863 Zutphen – Winterswijk

Zutphen 19:37 → Winterswijk 20:10 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 6 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 19:37 from Zutphen · Fri 20 Nov

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=4
  • 100% 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, 16 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
19:37on time on time
19:44 / 19:45≈ on time ≈ on time
19:51≈ on time ≈ +1 min
19:59 / 20:00≈ on time ≈ +1 min
20:07≈ on time ≈ +1 min
20:10on time +1 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 19 Nov— 20:14+1 min+2 min
Tue 17 Nov— 20:14+2 min+2 min
Fri 13 Nov— 19:48+1 min+1 min
Thu 12 Nov— 20:14+1 min+2 min
Mon 9 Nov— 20:090 min—
Thu 5 Nov— 20:12No data—
Wed 4 Nov— 20:13+1 min—
Mon 2 Nov— 20:09No data—
Fri 30 Oct— 20:13No data—
Thu 29 Oct— 20:120 min—
Wed 28 Oct— 20:130 min—
Tue 27 Oct— 20:130 min—
Mon 26 Oct— 20:11No data—
Fri 23 Oct— 20:150 min—
Thu 22 Oct— 20:14No data—
Wed 21 Oct— 20:13No data—
Tue 20 Oct— 20:120 min—
Mon 19 Oct— 20:130 min—
Fri 16 OctRuurlo 20:16No data—
Thu 15 Oct— 20:13No data—
Wed 14 OctVorden 20:13No data—
Tue 13 Oct— 20:12No data—
Mon 12 Oct— 20:110 min—
Thu 8 Oct— 20:130 min—
Wed 7 Oct— 20:120 min—
Mon 5 Oct— 20:130 min—
Sun 13 SeptWinterswijk West 20:28No data—
Sat 12 SeptWinterswijk West 20:28No data—