Train RRReis A 30915 Arnhem Centraal – Winterswijk

Arnhem Centraal 07:05 → Winterswijk 08:10 Mon, Tue, Wed, Thu, Fri, Sat 1 h 05 min · 14 stops RRReis A

Running now · updated 07:52

Heading to Winterswijk No data

Estimated arrival at Winterswijk 08:10 · 56 km/h

  1. Arnhem Centraal07:05
  2. Westervoort07:11
  3. Zevenaar07:19
  4. Doetinchem De Huet07:33
  5. Gaanderen07:42
  6. Varsseveld07:51
  7. Winterswijk08:10
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 9 full · 13 partial · 4 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 9 full · 16 partial · 52 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

  • Sat 24 Oct Max en route +8 min · last fix heading to Aalten +8 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Aalten +4 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Aalten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 12% · 3
  • 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
  • 75% T n=4
  • 75% F n=4
  • 75% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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 10Today
07:05on time on time
07:07≈ on time ≈ on time
07:11≈ on time ≈ on time
07:15≈ on time ≈ +1 min
07:19 / 07:20≈ on time ≈ +1 min
07:24≈ on time ≈ +1 min
07:29 / 07:30≈ on time ≈ +1 min
07:33≈ on time ≈ +1 min
07:37 / 07:38≈ on time ≈ +2 min
07:42≈ on time ≈ +2 min
07:44 / 07:45≈ on time ≈ +2 min
07:51≈ on time ≈ +2 min
07:59 / 08:00≈ on time ≈ +3 min
08:10on time +3 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
Sat 7 NovVarsseveld 07:49No data—
Fri 6 NovAalten 08:14No data—
Thu 5 NovAalten 08:14No data—
Wed 4 NovAalten 08:14Partial coverage0 min—
Tue 3 NovAalten 08:14Partial coverage0 min—
Mon 2 NovAalten 08:14No data—
Sat 31 OctAalten 08:16+2 min+2 min
Fri 30 OctAalten 08:14Partial coverage0 min—
Thu 29 OctAalten 08:15Partial coverage0 min—
Wed 28 OctAalten 08:14Partial coverage0 min—
Tue 27 OctAalten 08:14Partial coverage0 min—
Mon 26 OctAalten 08:14Partial coverage0 min—
Sat 24 OctAalten 08:22+8 min+8 min
Fri 23 OctAalten 08:150 min—
Thu 22 OctAalten 08:140 min—
Wed 21 OctAalten 08:150 min—
Tue 20 OctAalten 08:140 min—
Mon 19 OctAalten 08:140 min—
Sat 17 OctAalten 08:15+1 min+1 min
Fri 16 OctAalten 08:14Partial coverage0 min—
Thu 15 OctAalten 08:14Partial coverage0 min—
Wed 14 OctAalten 08:15Partial coverage0 min—
Tue 13 OctAalten 08:15Partial coverage0 min—
Mon 12 OctAalten 08:19Partial coverage0 min—
Sat 10 OctAalten 08:140 min—
Fri 9 OctAalten 08:17Partial coverage+3 min+3 min
Thu 8 OctAalten 08:18Partial coverage+4 min+4 min
Wed 7 OctAalten 08:15Partial coverage0 min—
Tue 6 OctAalten 08:14Partial coverage+1 min+1 min
Mon 5 OctAalten 08:15No data—