Train RRReis A 30947 Arnhem Centraal – Winterswijk

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

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 15:05 from Arnhem Centraal · Fri 20 Nov

Next departure 15:05 today · Arnhem Centraal
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 5 full · 16 partial · 8 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 6 full · 25 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 18 Nov Max en route +4 min · last fix heading to Aalten +4 min
  • Wed 11 Nov Max en route +3 min · last fix heading to Aalten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 60% W n=5
  • 100% T n=4
  • 100% F n=2
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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

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