Train RRReis A 30937 Arnhem Centraal – Winterswijk

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 12:35 from Arnhem Centraal · Sat 7 Nov

Next departure 12:35 today · Arnhem Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 2 full · 9 partial · 18 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 2 full · 13 partial · 73 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: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 15 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
12:35on time on time
12:37— —
12:41— —
12:45— —
12:49 / 12:50— —
12:54— —
12:59 / 13:00— —
13:03— —
13:07 / 13:08— —
13:12— —
13:14 / 13:15— —
13:21— —
13:29 / 13:30— —
13: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
Fri 6 NovAalten 13:44No data—
Thu 5 NovAalten 13:44No data—
Wed 4 NovAalten 13:44Partial coverage+2 min+2 min
Tue 3 NovAalten 13:44No data—
Mon 2 NovAalten 13:44No data—
Sun 1 NovAalten 13:45No data—
Sat 31 OctAalten 13:440 min—
Fri 30 OctAalten 13:44No data—
Thu 29 OctAalten 13:44No data—
Wed 28 OctAalten 13:44Partial coverage0 min—
Tue 27 OctAalten 13:45Partial coverage0 min—
Mon 26 OctAalten 13:44No data—
Sun 25 OctAalten 13:45No data—
Sat 24 OctAalten 13:44Partial coverage0 min—
Fri 23 OctAalten 13:45No data—
Thu 22 OctAalten 13:44No data—
Wed 21 OctAalten 13:44No data—
Tue 20 OctAalten 13:44Partial coverage0 min—
Mon 19 OctAalten 13:46Partial coverage0 min—
Sun 18 OctAalten 13:440 min—
Sat 17 OctAalten 13:46No data—
Fri 16 OctAalten 13:44No data—
Thu 15 OctAalten 13:44No data—
Wed 14 OctAalten 13:46No data—
Tue 13 OctAalten 13:44No data—
Mon 12 OctAalten 13:44No data—
Sun 11 OctAalten 13:44Partial coverage0 min—
Sat 10 OctAalten 13:44Partial coverage0 min—
Fri 9 OctAalten 13:45Partial coverage+2 min+2 min
Thu 8 OctAalten 13:44Partial coverage0 min—