Train RRReis A 30912 Winterswijk – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 08:08 +1 min

  1. Winterswijk06:50
  2. Varsseveld07:07
  3. Gaanderen07:17
  4. Wehl07:29
  5. Zevenaar07:39
  6. Arnhem Velperpoort07:52
  7. Arnhem Centraal07:55

Next service: tomorrow 06:50 from Winterswijk · Sat 24 Oct

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

  • Wed 7 Oct Max en route +7 min · last fix heading to Arnhem Velperpoort +7 min
  • Fri 9 Oct Max en route +6 min · last fix heading to Arnhem Velperpoort +6 min
  • Tue 6 Oct Max en route +6 min · last fix heading to Arnhem Velperpoort +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Arnhem Velperpoort +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 22% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
06:50
06:59 / 07:00
07:07
07:14 / 07:15
07:17
07:22 / 07:23
07:26
07:29 / 07:30
07:35
07:39 / 07:40
07:44
07:48
07:52
07: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.

Recent runs

DateLast stopFinalMax
Fri 23 OctArnhem Velperpoort 08:08Partial coverage+1 min—
Thu 22 OctArnhem Velperpoort 08:08Partial coverage0 min—
Wed 21 OctArnhem Velperpoort 08:07Partial coverage0 min—
Tue 20 OctArnhem Velperpoort 08:08Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 08:07Partial coverage0 min—
Sun 18 OctArnhem Velperpoort 08:07+1 min—
Sat 17 OctArnhem Velperpoort 08:08+2 min+2 min
Fri 16 OctArnhem Velperpoort 08:08Partial coverage0 min—
Thu 15 OctArnhem Velperpoort 08:08Partial coverage0 min—
Wed 14 OctArnhem Velperpoort 08:10Partial coverage0 min—
Tue 13 OctArnhem Velperpoort 08:10Partial coverage0 min—
Mon 12 OctArnhem Velperpoort 08:12Partial coverage0 min—
Sun 11 OctArnhem Velperpoort 08:07+1 min+1 min
Sat 10 OctArnhem Velperpoort 08:060 min—
Fri 9 OctArnhem Velperpoort 08:13Partial coverage+6 min+6 min
Thu 8 OctArnhem Velperpoort 08:11Partial coverage+5 min+5 min
Wed 7 OctArnhem Velperpoort 08:13Partial coverage+7 min+7 min
Tue 6 OctArnhem Velperpoort 08:12Partial coverage+5 min+6 min
Mon 5 OctArnhem Velperpoort 08:08No data—
Sun 4 OctArnhem Velperpoort 08:07No data—
Sat 3 OctArnhem Velperpoort 08:08No data—
Fri 2 OctArnhem Velperpoort 08:07No data—
Thu 1 OctArnhem Velperpoort 08:09No data—
Wed 30 SeptArnhem Velperpoort 08:08No data—
Tue 29 SeptArnhem Velperpoort 08:08No data—
Mon 28 SeptArnhem Velperpoort 08:07No data—
Sun 27 SeptArnhem Velperpoort 08:06No data—
Sat 26 SeptArnhem Velperpoort 08:06No data—
Fri 25 SeptArnhem Velperpoort 08:07No data—
Thu 24 SeptArnhem Velperpoort 08:08No data—