Train Arriva 30877 Zutphen – Winterswijk

Zutphen 23:07 → Winterswijk 23:40 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 23:07 from Zutphen · Fri 6 Nov

Next departure 23:07 today · Zutphen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 11 full · 0 partial · 9 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 13
  • 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=1
  • 100% W n=3
  • 100% T n=2
  • 100% 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, 13 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
23:07on time on time
23:14 / 23:15≈ on time ≈ on time
23:21≈ on time ≈ on time
23:29 / 23:30≈ on time ≈ +1 min
23:37≈ on time ≈ +1 min
23: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
Thu 5 Nov— 23:54No data—
Wed 4 Nov— 23:44+2 min+2 min
Tue 3 Nov— 23:39No data—
Mon 2 Nov— 23:390 min—
Thu 29 Oct— 23:440 min+1 min
Wed 28 Oct— 23:44No data—
Tue 27 Oct— 23:410 min—
Mon 26 Oct— 23:42No data—
Fri 23 Oct— 23:430 min—
Thu 22 Oct— 23:45No data—
Wed 21 Oct— 23:42No data—
Tue 20 Oct— 23:50No data—
Mon 19 Oct— 23:400 min—
Fri 16 Oct— 23:42+1 min+2 min
Thu 15 Oct— 23:44No data—
Wed 14 Oct— 23:420 min—
Tue 13 Oct— 23:41No data—
Mon 12 Oct— 23:410 min—
Fri 9 Oct— 23:390 min—
Thu 8 Oct— 23:44+1 min+1 min
Wed 7 Oct— 23:420 min—
Tue 6 Oct— 23:41No data—
Mon 5 Oct— 23:420 min—