Train Arriva 30963 Arnhem Centraal – Winterswijk

Arnhem Centraal 19:05 → Winterswijk 20:10 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 19:05 from Arnhem Centraal · Fri 20 Nov

Next departure 19: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%
21/24 runs under 3 min
RT coverage: 18 full · 6 partial · 29 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: +5 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

  • Sun 15 Nov Max en route +11 min · last fix heading to Aalten +11 min
  • Wed 11 Nov Max en route +6 min · last fix heading to — +6 min
  • Thu 8 Oct Max en route +5 min · last fix heading to — +5 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 88% · 21
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 67% W n=3
  • 67% T n=3
  • 100% F n=2
  • 100% S n=4
  • 80% S n=5

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
19:05on time on time
19:07≈ on time ≈ on time
19:11≈ on time ≈ on time
19:15≈ on time ≈ +1 min
19:19 / 19:20≈ on time ≈ +1 min
19:24≈ on time ≈ +1 min
19:29 / 19:30≈ on time ≈ +1 min
19:33≈ on time ≈ +2 min
19:37 / 19:38≈ on time ≈ +2 min
19:42≈ on time ≈ +2 min
19:44 / 19:45≈ on time ≈ +2 min
19:51≈ on time ≈ +3 min
19:59 / 20:00≈ on time ≈ +3 min
20:10on time +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
Thu 19 Nov— 20:090 min—
Wed 18 Nov— 20:130 min—
Tue 17 Nov— 20:140 min—
Mon 16 Nov— 20:140 min—
Sun 15 NovAalten 20:24Partial coverage+11 min+11 min
Sat 14 NovAalten 20:14Partial coverage+3 min+3 min
Fri 13 Nov— 19:48+1 min—
Wed 11 Nov— 20:19+6 min+6 min
Mon 9 Nov— 20:130 min—
Sun 8 NovAalten 20:17+3 min+4 min
Sat 7 NovAalten 20:140 min—
Thu 5 Nov— 20:12No data—
Mon 2 Nov— 20:090 min—
Sun 1 NovAalten 20:140 min—
Sat 31 OctAalten 20:150 min—
Fri 30 Oct— 20:15No data—
Thu 29 Oct— 20:14+1 min+1 min
Wed 28 Oct— 20:13No data—
Tue 27 Oct— 20:16No data—
Sun 25 OctAalten 20:15No data—
Sat 24 OctAalten 20:16No data—
Fri 23 OctDidam 20:16Partial coverage0 min—
Thu 22 Oct— 20:13No data—
Wed 21 Oct— 20:12No data—
Tue 20 Oct— 20:150 min—
Mon 19 Oct— 20:13No data—
Sun 18 OctAalten 20:14Partial coverage0 min—
Sat 17 OctAalten 20:14No data—
Fri 16 OctVarsseveld 20:05No data—
Thu 15 Oct— 20:13No data—