Train RRReis A 30932 Winterswijk – Arnhem Centraal

Winterswijk 11:50 → Arnhem Centraal 12:55 Daily 1 h 05 min · 14 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 13:07 No data

  1. Winterswijk11:50
  2. Varsseveld12:07
  3. Gaanderen12:17
  4. Wehl12:29
  5. Zevenaar12:39
  6. Arnhem Velperpoort12:52
  7. Arnhem Centraal12:55

Next service: tomorrow 11:50 from Winterswijk · Sat 7 Nov

Next departure 11:50 tomorrow · Winterswijk
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 2 full · 10 partial · 18 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 2 full · 13 partial · 74 no data
Typical delay
+1min
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 Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Arnhem Velperpoort +3 min

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 87% · 13
  • 3–10 min 13% · 2
  • 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
  • 0% T n=1
  • 100% F n=1
  • 50% S n=2
  • 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
11:50on time on time
11:59 / 12:00— —
12:07— —
12:14 / 12:15— —
12:17— —
12:22 / 12:23— —
12:26— —
12:29 / 12:30— —
12:35— —
12:39 / 12:40— —
12:44— —
12:48— —
12:52— —
12:55— —

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 NovArnhem Velperpoort 13:07No data—
Thu 5 NovArnhem Velperpoort 13:08No data—
Wed 4 NovArnhem Velperpoort 13:07Partial coverage0 min—
Tue 3 NovArnhem Velperpoort 13:04No data—
Mon 2 NovArnhem Velperpoort 13:08No data—
Sun 1 NovWehl 12:450 min—
Sat 31 OctWehl 12:44No data—
Fri 30 OctArnhem Velperpoort 13:06No data—
Thu 29 OctArnhem Velperpoort 13:06No data—
Wed 28 OctArnhem Velperpoort 13:08Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 13:07Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 13:07No data—
Sun 25 OctArnhem Velperpoort 13:11No data—
Sat 24 OctArnhem Velperpoort 13:09Partial coverage+3 min+3 min
Fri 23 OctArnhem Velperpoort 13:07No data—
Thu 22 OctArnhem Velperpoort 13:08No data—
Wed 21 OctArnhem Velperpoort 13:06No data—
Tue 20 OctArnhem Velperpoort 13:08Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 13:07Partial coverage0 min—
Sun 18 OctArnhem Velperpoort 13:07+1 min—
Sat 17 OctArnhem Velperpoort 13:09No data—
Fri 16 OctArnhem Velperpoort 13:07No data—
Thu 15 OctArnhem Velperpoort 13:08No data—
Wed 14 OctArnhem Velperpoort 13:08No data—
Tue 13 OctArnhem Velperpoort 13:08No data—
Mon 12 OctArnhem Velperpoort 13:07No data—
Sun 11 OctArnhem Velperpoort 13:09Partial coverage+2 min+2 min
Sat 10 OctArnhem Velperpoort 13:08Partial coverage+1 min+1 min
Fri 9 OctArnhem Velperpoort 13:08Partial coverage+1 min+1 min
Thu 8 OctArnhem Velperpoort 13:10Partial coverage+4 min+4 min