Train Arriva 30970 Winterswijk – Arnhem Centraal

Winterswijk 21:20 → Arnhem Centraal 22:24 Daily 1 h 04 min · 14 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 21:20 from Winterswijk · Sat 7 Nov

Next departure 21:20 today · Winterswijk
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 10 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 26 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 2 Nov Max en route +12 min · last fix heading to — +12 min
  • Thu 8 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 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=1
  • 50% T n=2
  • 100% 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, 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
21:20on time on time
21:29 / 21:30≈ on time ≈ on time
21:37≈ on time ≈ +1 min
21:44 / 21:45≈ on time ≈ +1 min
21:47≈ on time ≈ +1 min
21:52 / 21:53≈ +1 min ≈ +1 min
21:56≈ +1 min ≈ +2 min
21:59 / 22:00≈ +1 min ≈ +2 min
22:05≈ +1 min ≈ +2 min
22:09≈ +1 min ≈ +2 min
22:13≈ +1 min ≈ +2 min
22:17≈ +1 min ≈ +3 min
22:21≈ +1 min ≈ +3 min
22:24+1 min +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
Fri 6 Nov— 22:28+1 min—
Thu 5 Nov— 22:29No data—
Mon 2 Nov— 22:38+12 min+12 min
Sun 1 NovWehl 22:140 min—
Sat 31 OctWehl 22:17No data—
Fri 30 Oct— 22:30No data—
Thu 29 Oct— 22:29+1 min+1 min
Wed 28 Oct— 22:280 min—
Tue 27 Oct— 22:280 min—
Sun 25 OctArnhem Velperpoort 22:50No data—
Sat 24 OctArnhem Velperpoort 22:36No data—
Thu 22 Oct— 22:28No data—
Wed 21 Oct— 22:28No data—
Tue 20 Oct— 22:430 min—
Mon 19 Oct— 22:280 min—
Sun 18 OctArnhem Velperpoort 22:37+2 min+2 min
Sat 17 OctArnhem Velperpoort 22:38No data—
Fri 16 Oct— 22:29+2 min+2 min
Thu 15 Oct— 22:28No data—
Wed 14 Oct— 22:27No data—
Mon 12 Oct— 22:250 min—
Sun 11 OctArnhem Velperpoort 22:37+1 min+2 min
Sat 10 OctDidam 22:28+1 min—
Fri 9 Oct— 22:29+2 min+2 min
Thu 8 Oct— 22:29+3 min+3 min
Mon 5 Oct— 22:120 min—
Sun 4 OctArnhem Velperpoort 22:39No data—
Sat 3 OctArnhem Velperpoort 22:36No data—
Sun 27 SeptArnhem Velperpoort 22:36No data—
Sat 26 SeptArnhem Velperpoort 22:35No data—