Train RRReis A 30923 Arnhem Centraal → Winterswijk

Arnhem Centraal 09:05 → Winterswijk 10:10 Daily 1 h 05 min · 14 stops RRReis A

Running now · updated 09:15

Heading to Winterswijk 0 min

Estimated arrival at Winterswijk 10:10 · 7 km/h

  1. Arnhem Centraal09:05
  2. Westervoort09:11
  3. Zevenaar09:19
  4. Doetinchem De Huet09:33
  5. Gaanderen09:42
  6. Varsseveld09:51
  7. Winterswijk10:10

Today it is running no worse than usual: typical arrival delay is 0 min; 84% of the last 19 runs arrived on time.

On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 3 full · 16 partial · 11 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 3 full · 25 partial · 61 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: +5 min

Last 30 days

Arrival delay at Winterswijk, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 10 Nov Max en route +12 min · last fix heading to Aalten +12 min
  • Tue 17 Nov Max en route +10 min · last fix heading to Aalten +10 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Arnhem Centraal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 4% · 1
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 60% T n=5
  • 100% W n=5
  • 67% T n=3
  • 100% F n=3
  • 100% S n=7
  • 100% S n=4

Stops and timetable

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

Last 90 days, 28 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 10Today
09:05on time on time
09:07— —
09:11— —
09:15— —
09:19 / 09:20— —
09:24— —
09:29 / 09:30— —
09:33— —
09:37 / 09:38— —
09:42— —
09:44 / 09:45— —
09:51— —
09:59 / 10:00— —
10:10— —

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 21 NovDuiven 09:14Partial coverage0 min—
Fri 20 NovAalten 10:14Partial coverage0 min—
Thu 19 NovAalten 10:14Partial coverage0 min—
Wed 18 NovAalten 10:14Partial coverage+2 min+2 min
Tue 17 NovAalten 10:24Partial coverage+10 min+10 min
Mon 16 NovAalten 10:14Partial coverage0 min—
Sun 15 NovAalten 10:14Partial coverage0 min—
Sat 14 NovAalten 10:14Partial coverage0 min—
Fri 13 NovAalten 10:14Partial coverage0 min—
Thu 12 NovArnhem Centraal 10:18Partial coverage+4 min+4 min
Wed 11 NovAalten 10:14Partial coverage0 min—
Tue 10 NovAalten 10:24Partial coverage+12 min+12 min
Mon 9 NovVarsseveld 10:04Partial coverageNo data—
Sun 8 NovAalten 10:140 min—
Sat 7 NovAalten 10:140 min—
Fri 6 NovAalten 10:14No data—
Thu 5 NovAalten 10:14No data—
Wed 4 NovAalten 10:14Partial coverage0 min—
Tue 3 NovAalten 10:14No data—
Mon 2 NovAalten 10:14No data—
Sun 1 NovAalten 10:15No data—
Sat 31 OctAalten 10:140 min—
Fri 30 OctAalten 10:15No data—
Thu 29 OctAalten 10:14No data—
Wed 28 OctAalten 10:14Partial coverage0 min—
Tue 27 OctAalten 10:14Partial coverage0 min—
Mon 26 OctAalten 10:14No data—
Sun 25 OctAalten 10:14No data—
Sat 24 OctAalten 10:14Partial coverage0 min—
Fri 23 OctAalten 10:14No data—