Train RRReis A 30921 Arnhem Centraal – Winterswijk

Arnhem Centraal 08:35 → Winterswijk 09:40 Daily 1 h 05 min · 14 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Aalten at 09:44 No data

  1. Arnhem Centraal08:35
  2. Westervoort08:41
  3. Zevenaar08:49
  4. Doetinchem De Huet09:03
  5. Gaanderen09:12
  6. Aalten09:29
  7. Winterswijk09:40

Next service: tomorrow 08:35 from Arnhem Centraal · Fri 6 Nov

Next departure 08:35 tomorrow · Arnhem Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 13 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 6 full · 11 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 6 Oct Max en route +5 min · last fix heading to Aalten +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 67% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 100% 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, 17 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
08:35on time on time
08:37≈ on time ≈ on time
08:41≈ on time ≈ on time
08:45≈ on time ≈ on time
08:49 / 08:50≈ on time ≈ on time
08:54≈ on time ≈ on time
08:59 / 09:00≈ on time ≈ on time
09:03≈ on time ≈ +1 min
09:07 / 09:08≈ on time ≈ +1 min
09:12≈ on time ≈ +1 min
09:14 / 09:15≈ on time ≈ +1 min
09:21≈ on time ≈ +1 min
09:29 / 09:30≈ on time ≈ +1 min
09:40on time +1 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
Thu 5 NovAalten 09:44No data—
Wed 4 NovAalten 09:44Partial coverage0 min—
Tue 3 NovAalten 09:44Partial coverage0 min—
Mon 2 NovArnhem Centraal 14:590 min—
Sun 1 NovAalten 09:440 min—
Sat 31 OctAalten 09:440 min—
Fri 30 OctAalten 09:46No data—
Thu 29 OctAalten 09:44Partial coverage0 min—
Wed 28 OctAalten 09:44Partial coverage0 min—
Tue 27 OctAalten 09:45No data—
Mon 26 OctAalten 09:44No data—
Sun 25 OctAalten 09:44No data—
Fri 23 OctAalten 09:44No data—
Thu 22 OctAalten 09:44No data—
Wed 21 OctAalten 09:45No data—
Tue 20 OctAalten 09:44Partial coverage0 min—
Mon 19 OctAalten 09:48Partial coverage0 min—
Sun 18 OctAalten 09:46+1 min+1 min
Sat 17 OctAalten 09:440 min+1 min
Fri 16 OctAalten 09:44No data—
Thu 15 OctAalten 09:44No data—
Wed 14 OctAalten 09:44No data—
Tue 13 OctAalten 09:44No data—
Mon 12 OctAalten 09:46No data—
Sun 11 OctAalten 09:45Partial coverage0 min—
Sat 10 OctAalten 09:44Partial coverage0 min—
Fri 9 OctAalten 09:45Partial coverage0 min—
Thu 8 OctAalten 09:44Partial coverage+1 min+1 min
Wed 7 OctArnhem Centraal 14:53+1 min+1 min
Tue 6 OctAalten 09:45Partial coverage+5 min+5 min