Train Arriva 30974 Winterswijk – Arnhem Centraal

Winterswijk 22:20 → Arnhem Centraal 23:25 Daily 1 h 05 min · 14 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 22:20 from Winterswijk · Fri 20 Nov

Next departure 22:20 today · Winterswijk
On-time · 30 days
71%
12/17 runs under 3 min
RT coverage: 16 full · 1 partial · 8 no data
On-time · 90 days
73%
19/26 runs under 3 min
RT coverage: 25 full · 1 partial · 26 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Tue 17 Nov Max en route +6 min · last fix heading to — +6 min
  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Tue 10 Nov Max en route +5 min · last fix heading to — +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 19
  • 3–10 min 27% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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