Train RRReis A 30964 Winterswijk – Arnhem Centraal

Winterswijk 19:50 → Arnhem Centraal 20:55 Daily 1 h 05 min · 14 stops RRReis A

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 19:50 from Winterswijk · Mon 16 Nov

Next departure 19:50 today · Winterswijk
On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 13 full · 2 partial · 8 no data
On-time · 90 days
76%
16/21 runs under 3 min
RT coverage: 19 full · 2 partial · 28 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: +4 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

  • Wed 11 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 7 Oct Max en route +5 min · last fix heading to — +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 23 Oct Max en route +4 min · last fix heading to — +3 min
  • Sun 8 Nov Max en route +3 min · last fix heading to Wehl +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 16
  • 3–10 min 24% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • — T n=0
  • 0% W n=3
  • 100% T n=1
  • 67% F n=3
  • 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, 21 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:50on time on time
19:59 / 20:00≈ on time ≈ +1 min
20:07≈ on time ≈ +1 min
20:14 / 20:15≈ on time ≈ +2 min
20:17≈ on time ≈ +2 min
20:22 / 20:23≈ on time ≈ +2 min
20:26≈ on time ≈ +2 min
20:29 / 20:30≈ on time ≈ +2 min
20:35≈ on time ≈ +3 min
20:39 / 20:40≈ +1 min ≈ +3 min
20:44≈ +1 min ≈ +3 min
20:48≈ +1 min ≈ +4 min
20:52≈ +1 min ≈ +4 min
20: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
Sun 15 NovArnhem Velperpoort 21:09Partial coverage+3 min+5 min
Sat 14 NovArnhem Velperpoort 21:08+2 min+2 min
Wed 11 Nov— 21:02+6 min+6 min
Mon 9 Nov— 20:540 min—
Sun 8 NovWehl 20:47+3 min+3 min
Sat 7 NovWehl 20:59+1 min+1 min
Fri 6 Nov— 20:59+1 min+1 min
Thu 5 Nov— 20:58No data—
Wed 4 Nov— 21:02+4 min+4 min
Mon 2 Nov— 20:59No data—
Sun 1 NovWehl 20:440 min—
Sat 31 OctWehl 20:440 min—
Thu 29 Oct— 20:580 min+1 min
Wed 28 Oct— 20:58No data—
Tue 27 Oct— 20:57No data—
Mon 26 Oct— 21:000 min—
Sun 25 OctArnhem Velperpoort 21:09No data—
Sat 24 OctArnhem Velperpoort 21:09No data—
Fri 23 Oct— 21:01+3 min+4 min
Thu 22 Oct— 20:58No data—
Wed 21 Oct— 20:59No data—
Mon 19 Oct— 20:590 min—
Sun 18 OctArnhem Velperpoort 21:07Partial coverage0 min—
Sat 17 OctArnhem Velperpoort 21:07No data—
Fri 16 OctWinterswijk 20:04No data—
Thu 15 Oct— 20:58No data—
Wed 14 Oct— 20:57No data—
Tue 13 Oct— 21:03No data—
Mon 12 Oct— 20:570 min—
Sun 11 OctArnhem Velperpoort 21:060 min—