Train RRReis A 30945 Didam – Winterswijk

Didam 14:54 → Winterswijk 15:40 Daily 0 h 46 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:54 from Didam · Sun 8 Nov

Next departure 14:54 today · Didam
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 10 full · 2 partial · 17 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 15 full · 2 partial · 71 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: 0 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

  • Sat 10 Oct Max en route +8 min · last fix heading to Aalten +8 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=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 75% S n=4
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
14:54on time on time
14:59 / 15:00≈ on time ≈ on time
15:03≈ on time ≈ +1 min
15:07 / 15:08≈ on time ≈ +1 min
15:12≈ on time ≈ +1 min
15:14 / 15:15≈ on time ≈ +1 min
15:21≈ on time ≈ +1 min
15:29 / 15:30≈ on time ≈ +2 min
15:40on 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 NovAalten 15:44Partial coverage0 min—
Fri 6 NovAalten 15:44No data—
Thu 5 NovAalten 15:44No data—
Wed 4 NovAalten 15:440 min—
Tue 3 NovAalten 15:44No data—
Mon 2 NovAalten 15:44No data—
Sun 1 NovAalten 15:45No data—
Sat 31 OctAalten 15:44Partial coverage0 min—
Fri 30 OctAalten 15:44No data—
Thu 29 OctAalten 15:44No data—
Wed 28 OctAalten 15:450 min—
Tue 27 OctAalten 15:440 min—
Mon 26 OctAalten 15:44No data—
Sun 25 OctAalten 15:44No data—
Sat 24 OctAalten 15:440 min—
Fri 23 OctAalten 15:44No data—
Thu 22 OctAalten 15:44No data—
Wed 21 OctAalten 15:45No data—
Tue 20 OctAalten 16:230 min—
Mon 19 OctAalten 15:450 min—
Sun 18 OctAalten 15:440 min—
Sat 17 OctAalten 15:45No data—
Fri 16 OctAalten 15:44No data—
Thu 15 OctAalten 15:44No data—
Wed 14 OctAalten 15:44No data—
Tue 13 OctAalten 15:44No data—
Mon 12 OctAalten 15:45+1 min—
Sun 11 OctAalten 15:440 min—
Sat 10 OctAalten 15:52+8 min+8 min
Fri 9 OctAalten 15:45+2 min+2 min