Train Arriva 30967 Arnhem Centraal – Winterswijk

Arnhem Centraal 20:05 → Winterswijk 21:10 Daily 1 h 05 min · 14 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 20:05 from Arnhem Centraal · Tue 17 Nov

Next departure 20:05 today · Arnhem Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 13 full · 2 partial · 9 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 18 full · 5 partial · 27 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

  • Sun 15 Nov Max en route +7 min · last fix heading to Aalten +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 80% S n=5

Stops and timetable

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

Last 90 days, 23 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
20:05on time on time
20:07≈ on time ≈ on time
20:11≈ on time ≈ on time
20:15≈ on time ≈ on time
20:19 / 20:20≈ on time ≈ +1 min
20:24≈ on time ≈ +1 min
20:29 / 20:30≈ on time ≈ +1 min
20:33≈ on time ≈ +1 min
20:37 / 20:38≈ on time ≈ +1 min
20:42≈ on time ≈ +1 min
20:44 / 20:45≈ on time ≈ +1 min
20:51≈ on time ≈ +1 min
20:59 / 21:00≈ on time ≈ +2 min
21:10on 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
Mon 16 Nov— 21:090 min—
Sun 15 NovAalten 21:19Partial coverage+7 min+7 min
Sat 14 NovAalten 21:14Partial coverage0 min—
Thu 12 Nov— 21:030 min—
Wed 11 Nov— 21:15+3 min+3 min
Tue 10 Nov— 21:13No data—
Mon 9 Nov— 21:140 min—
Sun 8 NovAalten 21:140 min—
Sat 7 NovAalten 21:14+2 min+2 min
Fri 6 Nov— 21:130 min—
Thu 5 Nov— 21:14No data—
Mon 2 Nov— 21:13+1 min—
Sun 1 NovAalten 21:140 min+1 min
Sat 31 OctAalten 21:14No data—
Fri 30 Oct— 21:14No data—
Thu 29 Oct— 21:140 min—
Wed 28 Oct— 21:130 min—
Tue 27 Oct— 21:130 min—
Sun 25 OctAalten 21:14No data—
Sat 24 OctAalten 21:16No data—
Thu 22 Oct— 21:15No data—
Wed 21 Oct— 21:15No data—
Tue 20 Oct— 21:240 min—
Mon 19 Oct— 21:13No data—
Sun 18 OctAalten 21:14Partial coverage0 min—
Sat 17 OctAalten 21:14No data—
Fri 16 Oct— 21:15+2 min+2 min
Thu 15 Oct— 21:15No data—
Wed 14 Oct— 21:13No data—
Mon 12 Oct— 21:140 min—