Train RRReis A 30467 Apeldoorn – Winterswijk

Apeldoorn 20:23 → Winterswijk 21:10 Daily 0 h 47 min · 7 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Winterswijk West at 21:19 0 min

  1. Apeldoorn20:23
  2. Zutphen20:36
  3. Vorden20:44
  4. Ruurlo20:51
  5. Lichtenvoorde-Groenlo20:59
  6. Winterswijk West21:07
  7. Winterswijk21:10

Next service: tomorrow 20:23 from Apeldoorn · Sun 8 Nov

Next departure 20:23 tomorrow · Apeldoorn
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 8 full · 6 partial · 10 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 11 full · 6 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 16 Oct Max en route +5 min · last fix heading to — +4 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 94% · 16
  • 3–10 min 6% · 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=2
  • 100% T n=2
  • 67% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
20:23on time +2 min
20:36 / 20:37≈ on time ≈ +2 min
20:44 / 20:45≈ on time ≈ +2 min
20:51≈ on time ≈ +2 min
20:59 / 21:00≈ on time ≈ +2 min
21:07≈ on time ≈ +2 min
21:10on time +2 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
Sat 7 NovWinterswijk West 21:19Partial coverage0 min—
Fri 6 Nov— 21:090 min—
Thu 5 Nov— 21:12No data—
Wed 4 Nov— 21:130 min—
Mon 2 Nov— 21:14+2 min+2 min
Sun 1 NovWinterswijk West 21:23Partial coverage+1 min+3 min
Sat 31 OctWinterswijk West 21:21Partial coverage0 min—
Fri 30 Oct— 21:16No data—
Thu 29 Oct— 21:130 min—
Wed 28 Oct— 21:34No data—
Tue 27 Oct— 21:130 min—
Mon 26 Oct— 21:19No data—
Sun 25 OctWinterswijk West 21:24No data—
Sat 24 OctWinterswijk West 21:32No data—
Thu 22 Oct— 21:12No data—
Tue 20 Oct— 22:010 min—
Mon 19 Oct— 21:15No data—
Sun 18 OctWinterswijk West 21:22Partial coverage+1 min+1 min
Sat 17 OctWinterswijk West 21:21No data—
Fri 16 Oct— 21:16+4 min+5 min
Tue 13 Oct— 21:11No data—
Sun 11 OctWinterswijk West 21:24Partial coverage+2 min+4 min
Sat 10 OctWinterswijk West 21:21Partial coverage0 min+1 min
Fri 9 Oct— 21:130 min+2 min
Thu 8 Oct— 21:11+1 min+2 min
Wed 7 Oct— 21:130 min+1 min
Mon 5 Oct— 21:15+2 min+2 min
Sun 4 OctWinterswijk West 21:21No data—
Sat 3 OctWinterswijk West 21:23No data—
Sun 27 SeptWinterswijk West 21:22No data—