Train Arriva 30976 Winterswijk – Arnhem Centraal

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

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 22:50 from Winterswijk · Thu 19 Nov

Next departure 22:50 today · Winterswijk
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 13 full · 1 partial · 10 no data
On-time · 90 days
79%
19/24 runs under 3 min
RT coverage: 22 full · 2 partial · 27 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +7 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 12 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +4 min
  • Tue 17 Nov Max en route +4 min · last fix heading to — +4 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 19
  • 3–10 min 17% · 4
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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:50on time on time
22:59 / 23:00≈ on time ≈ +1 min
23:07≈ on time ≈ +1 min
23:14 / 23:15≈ on time ≈ +2 min
23:17≈ on time ≈ +2 min
23:22 / 23:23≈ +1 min ≈ +2 min
23:26≈ +1 min ≈ +2 min
23:29 / 23:30≈ +1 min ≈ +3 min
23:35≈ +1 min ≈ +3 min
23:39 / 23:40≈ +1 min ≈ +3 min
23:44≈ +1 min ≈ +4 min
23:48≈ +1 min ≈ +4 min
23:52≈ +1 min ≈ +4 min
23:55+1 min +4 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— 23:59+2 min+2 min
Tue 17 Nov— 23:59+4 min+4 min
Sun 15 NovArnhem Velperpoort 00:07+1 min—
Sat 14 NovAalten 23:14Partial coverage0 min—
Thu 12 Nov— 00:04+8 min+8 min
Wed 11 Nov— 23:58+1 min+1 min
Tue 10 Nov— 23:57No data—
Mon 9 Nov— 23:58+1 min—
Sun 8 NovWehl 23:54No data—
Sat 7 NovGaanderen 23:24No data—
Fri 6 Nov— 23:540 min—
Wed 4 Nov— 23:580 min—
Mon 2 Nov— 00:09+12 min+12 min
Sun 1 NovWehl 23:440 min—
Sat 31 OctGaanderen 23:31No data—
Fri 30 Oct— 23:57No data—
Thu 29 Oct— 00:00+2 min+3 min
Wed 28 Oct— 23:57No data—
Tue 27 Oct— 23:58No data—
Mon 26 Oct— 23:580 min—
Sun 25 OctArnhem Velperpoort 00:10No data—
Sat 24 Oct— 23:58No data—
Fri 23 Oct— 00:02+4 min+5 min
Thu 22 Oct— 00:01No data—
Tue 20 Oct— 00:00No data—
Mon 19 Oct— 23:580 min—
Sun 18 OctArnhem Velperpoort 00:10Partial coverage0 min+4 min
Sat 17 OctArnhem Velperpoort 00:06No data—
Thu 15 Oct— 23:56No data—
Wed 14 Oct— 23:580 min—