Train Arriva 30971 Arnhem Centraal – Winterswijk

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 21:05 from Arnhem Centraal · Fri 20 Nov

Next departure 21:05 today · Arnhem Centraal
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 15 full · 2 partial · 6 no data
On-time · 90 days
80%
20/25 runs under 3 min
RT coverage: 21 full · 4 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 14 Nov Max en route +4 min · last fix heading to Aalten +4 min
  • Fri 23 Oct Max en route +4 min · last fix heading to — +4 min
  • Wed 4 Nov Max en route +3 min · last fix heading to — +3 min
  • Mon 2 Nov Max en route +3 min · last fix heading to — +3 min
  • Wed 7 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 20
  • 3–10 min 20% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=2
  • 50% W n=4
  • 100% T n=2
  • 67% F n=3
  • 67% S n=3
  • 100% S n=5

Stops and timetable

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

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