Train RRReis A 30956 Winterswijk – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Wehl at 18:44 No data

  1. Winterswijk17:50
  2. Varsseveld18:07
  3. Gaanderen18:17
  4. Wehl18:29
  5. Didam18:35
  6. Zevenaar18:39
  7. Arnhem Centraal18:55

Next service: tomorrow 17:50 from Winterswijk · Sun 8 Nov

Next departure 17:50 tomorrow · Winterswijk
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 1 full · 13 partial · 15 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 2 full · 15 partial · 71 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: +4 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

  • Fri 6 Nov Max en route +18 min · last fix heading to Duiven +18 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Arnhem Velperpoort +5 min

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 88% · 15
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=2
  • 100% T n=2
  • 33% F n=3
  • 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, 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
17:50on time on time
17:59 / 18:00— —
18:07— —
18:14 / 18:15— —
18:17— —
18:22 / 18:23— —
18:26— —
18:29 / 18:30— —
18:35— —
18:39 / 18:40— —
18:44— —
18:48— —
18:52— —
18: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
Sat 7 NovWehl 18:44No data—
Fri 6 NovDuiven 19:13Partial coverage+18 min+18 min
Thu 5 NovVarsseveld 18:59No data—
Wed 4 NovTerborg 18:29No data—
Tue 3 NovVarsseveld 18:19Partial coverage0 min—
Mon 2 NovVarsseveld 18:58Partial coverage+2 min+2 min
Sun 1 NovWehl 18:44+1 min+1 min
Sat 31 OctWehl 18:44No data—
Fri 30 OctArnhem Velperpoort 19:06No data—
Thu 29 OctAalten 18:59Partial coverage+1 min+2 min
Wed 28 OctVarsseveld 18:59Partial coverage+1 min—
Tue 27 OctAalten 19:01Partial coverage0 min—
Mon 26 OctVarsseveld 18:21No data—
Sun 25 OctArnhem Velperpoort 19:07No data—
Sat 24 OctArnhem Velperpoort 19:09No data—
Fri 23 OctArnhem Velperpoort 19:06Partial coverage+5 min+5 min
Thu 22 OctDuiven 18:59No data—
Wed 21 OctZevenaar 19:01No data—
Tue 20 OctDuiven 18:57Partial coverage0 min—
Mon 19 OctZevenaar 18:59No data—
Sun 18 OctArnhem Velperpoort 19:09Partial coverage+2 min+2 min
Sat 17 OctArnhem Velperpoort 19:06No data—
Fri 16 OctArnhem Velperpoort 19:06No data—
Thu 15 OctWehl 18:56No data—
Tue 13 OctZevenaar 19:00No data—
Mon 12 OctDuiven 18:58Partial coverage0 min—
Sun 11 OctArnhem Velperpoort 19:06Partial coverage0 min—
Sat 10 OctArnhem Velperpoort 19:06Partial coverage0 min—
Fri 9 OctDidam 18:49Partial coverage0 min—
Thu 8 OctAalten 19:020 min—