Train RRReis A 30983 Arnhem Centraal – Winterswijk

Arnhem Centraal 00:05 → Winterswijk 01:10 Daily 1 h 05 min · 14 stops RRReis A

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 00:05 from Arnhem Centraal · Tue 17 Nov

Next departure 00:05 tomorrow · Arnhem Centraal
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 15 full · 1 partial · 5 no data
On-time · 90 days
83%
19/23 runs under 3 min
RT coverage: 21 full · 2 partial · 15 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

  • Tue 3 Nov Max en route +21 min · last fix heading to — +21 min
  • Thu 5 Nov Max en route +9 min · last fix heading to — +8 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 10 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 83% · 19
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 83% T n=6
  • 100% W n=2
  • 50% T n=4
  • 100% F n=3
  • 67% S n=3
  • 100% S n=3

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