Train RRReis A 30981 Arnhem Centraal – Winterswijk

Arnhem Centraal 23:35 → Winterswijk 00:40 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 23:35 from Arnhem Centraal · Mon 16 Nov

Next departure 23:35 today · Arnhem Centraal
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 13 full · 2 partial · 8 no data
On-time · 90 days
74%
17/23 runs under 3 min
RT coverage: 19 full · 4 partial · 23 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
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

  • Mon 5 Oct Max en route +17 min · last fix heading to Zevenaar +16 min
  • Thu 12 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Sat 14 Nov Max en route +5 min · last fix heading to — +5 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 17
  • 3–10 min 22% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 100% T n=2
  • 100% W n=2
  • 0% T n=2
  • 80% F n=5
  • 50% S n=2
  • 100% S n=5

Stops and timetable

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

Last 90 days, 23 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:35on time on time
23:37≈ on time ≈ on time
23:41≈ on time ≈ on time
23:45≈ on time ≈ +1 min
23:49 / 23:50≈ on time ≈ +1 min
23:54≈ on time ≈ +1 min
23:59 / 00:00≈ on time ≈ +2 min
00:03≈ +1 min ≈ +2 min
00:07 / 00:08≈ +1 min ≈ +2 min
00:12≈ +1 min ≈ +3 min
00:14 / 00:15≈ +1 min ≈ +3 min
00:21≈ +1 min ≈ +4 min
00:29 / 00:30≈ +1 min ≈ +4 min
00: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
Sun 15 NovAalten 00:44Partial coverage+3 min+3 min
Sat 14 Nov— 00:48+5 min+5 min
Thu 12 Nov— 00:49+8 min+8 min
Wed 11 Nov— 00:430 min—
Tue 10 Nov— 00:430 min—
Mon 9 Nov— 00:44+1 min+1 min
Sun 8 NovAalten 00:440 min—
Sat 7 Nov— 21:58No data—
Fri 6 Nov— 00:44+2 min+2 min
Thu 5 Nov— 00:49No data—
Mon 2 Nov— 00:44+3 min+3 min
Sun 1 NovAalten 00:440 min—
Fri 30 Oct— 00:43+2 min+2 min
Wed 28 Oct— 00:44No data—
Tue 27 Oct— 00:430 min—
Sun 25 OctAalten 00:46No data—
Sat 24 Oct— 00:43No data—
Fri 23 Oct— 00:47+1 min+1 min
Thu 22 Oct— 00:44No data—
Wed 21 Oct— 00:43No data—
Tue 20 Oct— 00:43No data—
Mon 19 Oct— 00:440 min—
Sun 18 OctAalten 00:44Partial coverage0 min—
Sat 17 OctArnhem Velperpoort 00:43No data—
Fri 16 Oct— 00:44+1 min+2 min
Thu 15 Oct— 00:43No data—
Wed 14 Oct— 00:44No data—
Mon 12 Oct— 00:430 min—
Sun 11 OctAalten 00:45Partial coverage0 min—
Sat 10 Oct— 00:46+3 min+3 min