Train RRReis A 30919 Arnhem Centraal → Winterswijk

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

RRReis A 30919 Arnhem Centraal–Winterswijk: final delay under 3 min on 16 of its 20 runs with data in the last 30 days (80%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 00:10 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 08:05 from Arnhem Centraal · Sun 22 Nov

Next departure 08:05 today · Arnhem Centraal
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 4 full · 16 partial · 9 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 4 full · 25 partial · 58 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: +6 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 17 Nov Max en route +10 min · last fix heading to Aalten +10 min
  • Wed 18 Nov Max en route +7 min · last fix heading to Aalten +7 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Aalten +6 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Aalten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 25
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 80% T n=5
  • 60% W n=5
  • 67% T n=3
  • 100% F n=3
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 29 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:05on time on time
08:07— —
08:11— —
08:15— —
08:19 / 08:20— —
08:24— —
08:29 / 08:30— —
08:33— —
08:37 / 08:38— —
08:42— —
08:44 / 08:45— —
08:51— —
08:59 / 09:00— —
09:10— —

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
Sat 21 NovAalten 09:14Partial coverage0 min—
Fri 20 NovAalten 09:14Partial coverage+1 min+2 min
Thu 19 NovAalten 09:14Partial coverage+1 min+2 min
Wed 18 NovAalten 09:19Partial coverage+7 min+7 min
Tue 17 NovAalten 09:23Partial coverage+10 min+10 min
Mon 16 NovAalten 09:14Partial coverage0 min—
Sun 15 NovAalten 09:14Partial coverage0 min—
Sat 14 NovAalten 09:14Partial coverage0 min—
Fri 13 NovAalten 09:19Partial coverage0 min+5 min
Thu 12 NovAalten 09:19Partial coverage+6 min+6 min
Wed 11 NovAalten 09:18Partial coverage0 min—
Tue 10 NovAalten 09:14Partial coverage+1 min+3 min
Mon 9 NovAalten 09:14Partial coverage+3 min+3 min
Sun 8 NovAalten 09:140 min—
Sat 7 NovAalten 09:140 min—
Fri 6 NovAalten 09:18No data—
Thu 5 NovAalten 09:14No data—
Wed 4 NovAalten 09:17Partial coverage+3 min+3 min
Tue 3 NovAalten 09:14No data—
Mon 2 NovAalten 09:19No data—
Sun 1 NovAalten 09:140 min—
Sat 31 OctAalten 09:140 min—
Fri 30 OctAalten 09:14No data—
Thu 29 OctAalten 09:16No data—
Wed 28 OctAalten 09:16Partial coverage0 min—
Tue 27 OctAalten 09:15Partial coverage0 min—
Mon 26 OctAalten 09:14No data—
Sun 25 OctAalten 09:14No data—
Sat 24 OctDoetinchem De Huet 08:47Partial coverageNo data—
Fri 23 OctAalten 09:14No data—