Train RRReis A 30949 Arnhem Centraal – Winterswijk

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 15:36 from Arnhem Centraal · Sat 7 Nov

Next departure 15:36 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
+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

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