Train RRReis A 30977 Arnhem Centraal – Winterswijk

Arnhem Centraal 22:35 → Winterswijk 23:43 Daily 1 h 08 min · 14 stops RRReis A

Running now · updated 23:36

Heading to Winterswijk No data

Estimated arrival at Winterswijk 23:43 · 146 km/h

  1. Arnhem Centraal22:35
  2. Westervoort22:41
  3. Zevenaar22:49
  4. Doetinchem De Huet23:03
  5. Gaanderen23:12
  6. Varsseveld23:21
  7. Winterswijk23:43
On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 15 full · 0 partial · 13 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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 4 Nov Max en route +15 min · last fix heading to — +15 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Mon 2 Nov Max en route +5 min · last fix heading to — +4 min
  • Thu 29 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 17% · 3
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 67% W n=3
  • 0% T n=1
  • 75% F n=4
  • 100% S n=1
  • 100% S n=3

Stops and timetable

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

Last 90 days, 18 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
22:35on time on time
22:37≈ on time ≈ on time
22:41≈ on time ≈ on time
22:45≈ on time ≈ +1 min
22:49 / 22:50≈ on time ≈ +1 min
22:54≈ on time ≈ +1 min
22:59 / 23:00≈ on time ≈ +2 min
23:03≈ on time ≈ +2 min
23:07 / 23:08≈ on time ≈ +2 min
23:12≈ on time ≈ +2 min
23:14 / 23:15≈ on time ≈ +2 min
23:21≈ on time ≈ +3 min
23:29 / 23:32≈ on time ≈ +3 min
23:43on time +4 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 23:34No data—
Fri 6 Nov— 23:470 min—
Thu 5 Nov— 23:53No data—
Wed 4 Nov— 23:58+15 min+15 min
Tue 3 Nov— 23:44No data—
Mon 2 Nov— 23:44+4 min+5 min
Sun 1 NovDoetinchem De Huet 23:190 min—
Sat 31 OctVarsseveld 23:43No data—
Fri 30 Oct— 23:46No data—
Thu 29 Oct— 23:45+3 min+3 min
Wed 28 Oct— 23:44No data—
Tue 27 Oct— 23:440 min—
Mon 26 Oct— 23:45No data—
Sun 25 OctDoetinchem De Huet 23:33No data—
Sat 24 OctArnhem Velperpoort 23:44No data—
Fri 23 Oct— 23:48+5 min+5 min
Thu 22 Oct— 23:44No data—
Wed 21 Oct— 23:43No data—
Mon 19 Oct— 23:430 min—
Sun 18 OctDoetinchem De Huet 23:180 min—
Sat 17 OctAalten 23:44No data—
Fri 16 Oct— 23:460 min+1 min
Wed 14 Oct— 23:430 min—
Tue 13 Oct— 23:45No data—
Mon 12 Oct— 23:430 min—
Sun 11 OctDoetinchem De Huet 23:200 min+1 min
Sat 10 Oct— 23:440 min—
Fri 9 Oct— 23:450 min—
Wed 7 Oct— 23:45+2 min+2 min
Tue 6 Oct— 23:42+2 min+2 min