Train RRReis A 30935 Arnhem Centraal – Winterswijk

Arnhem Centraal 12:05 → Winterswijk 13: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 12:05 from Arnhem Centraal · Fri 20 Nov

Next departure 12:05 today · Arnhem Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 5 full · 15 partial · 9 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 6 full · 23 partial · 59 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: +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

  • Mon 5 Oct Max en route +5 min · last fix heading to Aalten +5 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Aalten +3 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Aalten +3 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 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 80% W n=5
  • 100% T n=4
  • 50% F n=2
  • 100% 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
12:05on time on time
12:07≈ on time ≈ on time
12:11≈ on time ≈ on time
12:15≈ on time ≈ on time
12:19 / 12:20≈ on time ≈ on time
12:24≈ on time ≈ on time
12:29 / 12:30≈ on time ≈ on time
12:33≈ on time ≈ on time
12:37 / 12:38≈ on time ≈ on time
12:42≈ on time ≈ on time
12:44 / 12:45≈ on time ≈ on time
12:51≈ on time ≈ on time
12:59 / 13:00≈ on time ≈ on time
13:10on time +1 min

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