Train Arriva 30979 Arnhem Centraal – Winterswijk

Arnhem Centraal 23:05 → Winterswijk 00: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 23:05 from Arnhem Centraal · Thu 19 Nov

Next departure 23:05 today · Arnhem Centraal
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 13 full · 3 partial · 7 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 22 full · 4 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

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

On-time by weekday

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