Train RRReis A 30940 Winterswijk – Arnhem Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:50 from Winterswijk · Fri 6 Nov

Next departure 13:50 today · Winterswijk
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 16 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 3 full · 12 partial · 73 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: +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

  • Fri 9 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 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 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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