Train RRReis A 30948 Winterswijk – Arnhem Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 15:50 from Winterswijk · Mon 16 Nov

Next departure 15:50 today · Winterswijk
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 16 full · 2 partial · 11 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 23 full · 3 partial · 62 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 13 Nov Max en route +10 min · last fix heading to Arnhem Velperpoort +10 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 75% W n=4
  • 100% T n=2
  • 33% F n=3
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

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