Train RRReis A 30945 Arnhem Centraal – Winterswijk

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

It has not run yet today

Last recorded run: Thursday 19 November +5 min

Next service: today 14:35 from Arnhem Centraal · Fri 20 Nov

Next departure 14:35 today · Arnhem Centraal
On-time · 30 days
67%
12/18 runs under 3 min
RT coverage: 3 full · 15 partial · 11 no data
On-time · 90 days
76%
22/29 runs under 3 min
RT coverage: 4 full · 25 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Mon 16 Nov Max en route +10 min · last fix heading to Aalten +10 min
  • Sat 10 Oct Max en route +8 min · last fix heading to Aalten +8 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Aalten +5 min
  • Sat 14 Nov Max en route +5 min · last fix heading to Aalten +5 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Aalten +4 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 76% · 22
  • 3–10 min 21% · 6
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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
14:35on time on time
14:37— —
14:41— —
14:45— —
14:49 / 14:50— —
14:54— —
14:59 / 15:00— —
15:03— —
15:07 / 15:08— —
15:12— —
15:14 / 15:15— —
15:21— —
15:29 / 15:30— —
15:40— —

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 19 NovAalten 15:48Partial coverage+5 min+5 min
Wed 18 NovAalten 15:48Partial coverage+4 min+4 min
Tue 17 NovAalten 15:47Partial coverage+4 min+4 min
Mon 16 NovAalten 15:55Partial coverage+10 min+10 min
Sun 15 NovAalten 15:44Partial coverage+1 min+1 min
Sat 14 NovAalten 15:49Partial coverage+5 min+5 min
Fri 13 NovAalten 15:47Partial coverage+3 min+3 min
Thu 12 NovAalten 15:44Partial coverage0 min—
Wed 11 NovAalten 15:44Partial coverage0 min—
Tue 10 NovAalten 15:44Partial coverage0 min—
Mon 9 NovAalten 15:45Partial coverage0 min—
Sun 8 NovAalten 15:440 min—
Sat 7 NovAalten 15:440 min—
Fri 6 NovAalten 15:44No data—
Thu 5 NovAalten 15:44No data—
Wed 4 NovAalten 15:44Partial coverage0 min—
Tue 3 NovAalten 15:44No data—
Mon 2 NovAalten 15:44No data—
Sun 1 NovAalten 15:45No data—
Sat 31 OctAalten 15:440 min—
Fri 30 OctAalten 15:44No data—
Thu 29 OctAalten 15:44No data—
Wed 28 OctAalten 15:45Partial coverage0 min—
Tue 27 OctAalten 15:44Partial coverage0 min—
Mon 26 OctAalten 15:44No data—
Sun 25 OctAalten 15:44No data—
Sat 24 OctAalten 15:44Partial coverage0 min—
Fri 23 OctAalten 15:44No data—
Thu 22 OctAalten 15:44No data—
Wed 21 OctAalten 15:45No data—