Train Arriva 30861 Zutphen – Winterswijk

Zutphen 19:07 → Winterswijk 19:40 Daily 0 h 33 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 19:44 +1 min

  1. Zutphen19:07
  2. Vorden19:14
  3. Ruurlo19:21
  4. Lichtenvoorde-Groenlo19:29
  5. Winterswijk West19:37
  6. Winterswijk19:40

Next service: tomorrow 19:07 from Zutphen · Sat 7 Nov

Next departure 19:07 tomorrow · Zutphen
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 6 full · 6 partial · 12 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 9 full · 6 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sun 1 Nov Max en route +4 min · last fix heading to Winterswijk West +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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:07on time on time
19:14 / 19:15≈ on time ≈ on time
19:21≈ on time ≈ on time
19:29 / 19:30≈ on time ≈ +1 min
19:37≈ on time ≈ +1 min
19:40on 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
Fri 6 Nov— 19:44+1 min+2 min
Thu 5 Nov— 19:43No data—
Wed 4 Nov— 19:43+1 min—
Mon 2 Nov— 19:42No data—
Sun 1 NovWinterswijk West 19:54Partial coverage+4 min+4 min
Sat 31 OctWinterswijk West 19:52Partial coverage+1 min+1 min
Thu 29 Oct— 19:410 min—
Wed 28 Oct— 19:42No data—
Mon 26 Oct— 19:43No data—
Sun 25 OctWinterswijk West 19:51No data—
Sat 24 OctWinterswijk West 19:56No data—
Fri 23 OctRuurlo 19:44Partial coverage+2 min+2 min
Thu 22 Oct— 19:42No data—
Wed 21 Oct— 19:43No data—
Tue 20 Oct— 19:420 min—
Mon 19 Oct— 19:41No data—
Sun 18 OctWinterswijk West 19:53Partial coverage+2 min+2 min
Sat 17 OctWinterswijk West 19:51No data—
Fri 16 OctWinterswijk West 19:51No data—
Wed 14 OctWinterswijk West 19:51No data—
Sun 11 OctWinterswijk West 19:51Partial coverage0 min—
Sat 10 OctWinterswijk West 19:53Partial coverage+1 min+2 min
Fri 9 Oct— 19:410 min—
Thu 8 Oct— 19:110 min—
Wed 7 Oct— 19:320 min—
Tue 6 Oct— 19:420 min—
Mon 5 Oct— 19:360 min—
Sun 4 OctWinterswijk West 19:52No data—
Sat 3 OctWinterswijk West 19:52No data—
Sun 27 SeptWinterswijk West 19:51No data—