Train Arriva 30965 Arnhem Centraal – Winterswijk

Arnhem Centraal 19:36 → Winterswijk 20:40 Daily 1 h 04 min · 14 stops Arriva

Running now · updated 20:43

Heading to Winterswijk 0 min

Estimated arrival at Winterswijk 20:40

  1. Arnhem Centraal19:36
  2. Westervoort19:42
  3. Zevenaar19:50
  4. Doetinchem De Huet20:04
  5. Gaanderen20:12
  6. Varsseveld20:21
  7. Winterswijk20:40

Today it is running no worse than usual: typical arrival delay is +1 min; 73% of the last 15 runs arrived on time.

On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 12 full · 3 partial · 9 no data
On-time · 90 days
72%
18/25 runs under 3 min
RT coverage: 20 full · 5 partial · 27 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Mon 5 Oct Max en route +7 min · last fix heading to — +7 min
  • Sun 15 Nov Max en route +7 min · last fix heading to Aalten +7 min
  • Wed 11 Nov Max en route +7 min · last fix heading to — +7 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Aalten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 72% · 18
  • 3–10 min 28% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 67% W n=3
  • 50% T n=2
  • 33% F n=3
  • 75% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 25 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 10Today
19:36on time +1 min
19:38≈ on time ≈ +2 min
19:42≈ on time ≈ +2 min
19:46≈ on time ≈ +2 min
19:50≈ on time ≈ +3 min
19:55≈ on time ≈ +3 min
19:59 / 20:00≈ on time ≈ +3 min
20:04≈ on time ≈ +3 min
20:07 / 20:08≈ on time ≈ +3 min
20:12≈ on time ≈ +4 min
20:14 / 20:15≈ on time ≈ +4 min
20:21≈ on time ≈ +4 min
20:29 / 20:30≈ +1 min ≈ +4 min
20:40+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
Mon 16 Nov— 20:390 min—
Sun 15 NovAalten 20:49Partial coverage+7 min+7 min
Sat 14 NovAalten 20:44Partial coverage+3 min+3 min
Thu 12 Nov— 20:44+3 min+5 min
Wed 11 Nov— 20:49+7 min+7 min
Tue 10 Nov— 20:420 min—
Mon 9 Nov— 20:440 min—
Sun 8 NovAalten 20:44+1 min+1 min
Sat 7 NovAalten 20:440 min—
Wed 4 Nov— 20:47+3 min+3 min
Mon 2 Nov— 20:43No data—
Sun 1 NovAalten 20:44No data—
Sat 31 OctAalten 20:450 min—
Fri 30 Oct— 20:47No data—
Wed 28 Oct— 20:43No data—
Tue 27 Oct— 20:430 min—
Mon 26 OctDuiven 20:41No data—
Sun 25 OctAalten 20:46No data—
Sat 24 OctAalten 20:45No data—
Fri 23 Oct— 20:48+5 min+5 min
Thu 22 Oct— 20:46No data—
Wed 21 Oct— 20:44No data—
Tue 20 Oct— 20:470 min—
Sun 18 OctAalten 20:45Partial coverage+1 min+1 min
Sat 17 OctAalten 20:44No data—
Fri 16 OctDidam 20:46+3 min+3 min
Thu 15 Oct— 20:45No data—
Wed 14 OctDuiven 20:00No data—
Tue 13 Oct— 20:440 min—
Mon 12 Oct— 20:430 min—