Train Arriva 30975 Arnhem Centraal – Winterswijk

Arnhem Centraal 22:07 → Winterswijk 23:10 Daily 1 h 03 min · 14 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 22:07 from Arnhem Centraal · Thu 5 Nov

Next departure 22:07 today · Arnhem Centraal
On-time · 30 days
69%
9/13 runs under 3 min
RT coverage: 11 full · 2 partial · 10 no data
On-time · 90 days
73%
11/15 runs under 3 min
RT coverage: 13 full · 2 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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 +7 min · last fix heading to — +7 min
  • Mon 2 Nov Max en route +7 min · last fix heading to — +6 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +4 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 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 73% · 11
  • 3–10 min 27% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 0% F n=3
  • 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, 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
22:07on time on time
22:09≈ on time ≈ on time
22:13≈ on time ≈ +1 min
22:17≈ on time ≈ +1 min
22:21≈ on time ≈ +1 min
22:25≈ on time ≈ +2 min
22:30 / 22:31≈ on time ≈ +2 min
22:34≈ on time ≈ +2 min
22:37 / 22:38≈ on time ≈ +3 min
22:42≈ on time ≈ +3 min
22:44 / 22:45≈ on time ≈ +3 min
22:51≈ on time ≈ +4 min
22:59 / 23:00≈ on time ≈ +5 min
23:10on time +6 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— 23:130 min—
Mon 2 Nov— 23:19+6 min+7 min
Sun 1 NovAalten 23:140 min—
Sat 31 OctAalten 23:14No data—
Wed 28 Oct— 23:17No data—
Tue 27 Oct— 23:140 min—
Mon 26 Oct— 23:16No data—
Sun 25 OctAalten 23:19No data—
Sat 24 OctDoetinchem 23:17No data—
Fri 23 Oct— 23:19+7 min+7 min
Thu 22 Oct— 23:13No data—
Wed 21 Oct— 23:15No data—
Tue 20 Oct— 23:19No data—
Sun 18 OctAalten 23:14Partial coverage0 min—
Sat 17 OctAalten 23:14No data—
Fri 16 Oct— 23:17+4 min+5 min
Tue 13 Oct— 23:18No data—
Mon 12 Oct— 23:15+2 min+2 min
Sun 11 OctAalten 23:15Partial coverage+1 min+1 min
Sat 10 Oct— 23:140 min—
Fri 9 Oct— 23:16+3 min+3 min
Thu 8 Oct— 22:400 min—
Wed 7 Oct— 23:130 min—
Tue 6 Oct— 23:13+1 min—
Mon 5 Oct— 23:130 min—
Sun 4 OctAalten 23:17No data—
Sat 3 OctAalten 23:15No data—
Sun 27 SeptAalten 23:14No data—
Sat 26 SeptAalten 23:14No data—
Sun 20 SeptAalten 23:14No data—