Train RRReis A 30960 Winterswijk – Arnhem Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November +10 min

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

Next departure 18:50 today · Winterswijk
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 11 full · 6 partial · 10 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 16 full · 8 partial · 36 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 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

  • Sun 15 Nov Max en route +10 min · last fix heading to Arnhem Velperpoort +10 min
  • Sun 8 Nov Max en route +8 min · last fix heading to Wehl +7 min
  • Thu 8 Oct Max en route +6 min · last fix heading to — +4 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 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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