Train Arriva 30961 Arnhem Centraal – Winterswijk

Arnhem Centraal 18:35 → Winterswijk 19:40 Daily 1 h 05 min · 14 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:35 from Arnhem Centraal · Thu 5 Nov

Next departure 18:35 today · Arnhem Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 8 full · 7 partial · 12 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 9 full · 7 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Varsseveld +5 min
  • Wed 7 Oct Max en route +3 min · last fix heading to — +3 min

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 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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
18:35on time on time
18:37≈ on time ≈ on time
18:41≈ on time ≈ on time
18:45≈ on time ≈ on time
18:49 / 18:50≈ on time ≈ on time
18:54≈ on time ≈ +1 min
18:59 / 19:00≈ on time ≈ +1 min
19:03≈ on time ≈ +1 min
19:07 / 19:08≈ on time ≈ +1 min
19:12≈ on time ≈ +1 min
19:14 / 19:15≈ on time ≈ +1 min
19:21≈ on time ≈ +1 min
19:29 / 19:30≈ on time ≈ +1 min
19:40on time +2 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
Wed 4 Nov— 19:430 min—
Mon 2 Nov— 19:440 min—
Sun 1 NovAalten 19:44+1 min+1 min
Sat 31 OctAalten 19:44No data—
Fri 30 OctDidam 19:08No data—
Thu 29 Oct— 19:430 min—
Wed 28 Oct— 19:430 min—
Tue 27 Oct— 19:460 min—
Mon 26 Oct— 19:43No data—
Sun 25 OctAalten 19:44No data—
Sat 24 OctAalten 19:48No data—
Fri 23 OctVarsseveld 19:47Partial coverage+5 min+5 min
Thu 22 OctDuiven 19:44No data—
Wed 21 OctArnhem Velperpoort 19:45No data—
Tue 20 OctDuiven 18:50Partial coverage0 min—
Mon 19 OctWestervoort 19:44Partial coverage0 min—
Sun 18 OctAalten 19:440 min—
Sat 17 OctAalten 19:44No data—
Fri 16 OctAalten 19:44No data—
Thu 15 Oct— 19:43No data—
Wed 14 OctAalten 19:52No data—
Tue 13 OctArnhem Velperpoort 19:44No data—
Mon 12 OctDuiven 19:43Partial coverage0 min—
Sun 11 OctAalten 19:44Partial coverage0 min—
Sat 10 OctAalten 19:44Partial coverage0 min—
Fri 9 OctArnhem Centraal 19:42Partial coverage0 min—
Wed 7 Oct— 19:46+3 min+3 min
Mon 5 Oct— 19:480 min—
Sun 4 OctAalten 19:44No data—
Sat 3 OctAalten 19:44No data—