Train RRReis A 30933 Arnhem Centraal – Winterswijk

Arnhem Centraal 11:36 → Winterswijk 12:40 Daily 1 h 04 min · 14 stops RRReis A

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 11:36 from Arnhem Centraal · Fri 20 Nov

Next departure 11:36 today · Arnhem Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 2 full · 16 partial · 11 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 2 full · 25 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Sat 24 Oct Max en route +8 min · last fix heading to Aalten +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=2
  • 75% S n=4
  • 100% S n=4

Stops and timetable

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

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