Train RRReis A 30952 Winterswijk – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 18:04 No data

  1. Winterswijk16:50
  2. Varsseveld17:07
  3. Gaanderen17:17
  4. Wehl17:29
  5. Zevenaar17:39
  6. Arnhem Velperpoort17:52
  7. Arnhem Centraal17:55

Next service: tomorrow 16:50 from Winterswijk · Fri 6 Nov

Next departure 16:50 tomorrow · Winterswijk
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 3 full · 12 partial · 15 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 3 full · 14 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 17
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
16:50on time on time
16:59 / 17:00— —
17:07— —
17:14 / 17:15— —
17:17— —
17:22 / 17:23— —
17:26— —
17:29 / 17:30— —
17:35— —
17:39 / 17:40— —
17:44— —
17:48— —
17:52— —
17: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
Thu 5 NovArnhem Velperpoort 18:04No data—
Wed 4 NovArnhem Velperpoort 18:04No data—
Tue 3 NovArnhem Velperpoort 18:04Partial coverage0 min—
Mon 2 NovArnhem Velperpoort 18:04Partial coverage0 min—
Sun 1 NovWehl 17:440 min—
Sat 31 OctWehl 17:440 min—
Fri 30 OctArnhem Velperpoort 18:06No data—
Thu 29 OctArnhem Velperpoort 18:06No data—
Wed 28 OctArnhem Velperpoort 18:06Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 18:06No data—
Mon 26 OctArnhem Velperpoort 18:06Partial coverage+3 min+3 min
Sun 25 OctArnhem Velperpoort 18:09No data—
Sat 24 OctArnhem Velperpoort 18:08Partial coverage+1 min+1 min
Fri 23 OctArnhem Velperpoort 18:08No data—
Thu 22 OctArnhem Velperpoort 18:06No data—
Wed 21 OctArnhem Velperpoort 18:06No data—
Tue 20 OctArnhem Velperpoort 18:06Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 18:06No data—
Sun 18 OctArnhem Velperpoort 18:09Partial coverage+1 min+1 min
Sat 17 OctArnhem Velperpoort 18:07No data—
Fri 16 OctArnhem Velperpoort 18:10No data—
Thu 15 OctArnhem Velperpoort 18:06No data—
Wed 14 OctArnhem Velperpoort 18:06No data—
Tue 13 OctArnhem Velperpoort 18:06No data—
Mon 12 OctArnhem Velperpoort 18:06Partial coverage0 min—
Sun 11 OctArnhem Velperpoort 18:06Partial coverage0 min—
Sat 10 OctArnhem Velperpoort 18:08Partial coverage+2 min+2 min
Fri 9 OctArnhem Velperpoort 18:06Partial coverage0 min—
Thu 8 OctArnhem Velperpoort 18:07+1 min+2 min
Wed 7 OctArnhem Velperpoort 18:06Partial coverage+2 min+2 min