S36 23954 Rekingen AG – Waldshut

View line S36

Rekingen AG 05:28 → Waldshut 05:53 Daily 0 h 25 min · 6 stops Thurbo

✓ Today’s run finished

Today it reached Waldshut at 05:53 0 min

  1. Rekingen AG05:28
  2. Bad Zurzach05:33
  3. Rietheim05:35
  4. Koblenz Dorf05:38
  5. Koblenz05:42
  6. Waldshut05:53

Next service: tomorrow 05:28 from Rekingen AG · Sun 8 Nov

Next departure 05:28 tomorrow · Rekingen AG
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Waldshut, 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 13 Oct Max en route +4 min · last fix heading to Koblenz +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 35
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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
05:28on time on time
05:33≈ on time ≈ on time
05:35≈ on time ≈ on time
05:38≈ on time ≈ on time
05:42 / 05:47≈ on time ≈ on time
05:53on time on time

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 NovWaldshut 05:540 min—
Fri 6 NovWaldshut 05:540 min—
Thu 5 NovWaldshut 05:540 min—
Wed 4 NovWaldshut 05:540 min—
Tue 3 NovWaldshut 05:540 min—
Mon 2 NovWaldshut 05:540 min—
Sun 1 NovWaldshut 05:540 min—
Sat 31 OctWaldshut 05:540 min—
Fri 30 OctWaldshut 05:540 min—
Thu 29 OctWaldshut 05:540 min—
Wed 28 OctWaldshut 05:55+1 min—
Tue 27 OctWaldshut 05:540 min—
Mon 26 OctWaldshut 05:540 min—
Sun 25 OctWaldshut 05:540 min—
Sat 24 OctWaldshut 05:540 min—
Fri 23 OctWaldshut 05:540 min—
Thu 22 OctWaldshut 05:540 min—
Wed 21 OctWaldshut 05:540 min—
Tue 20 OctWaldshut 05:540 min—
Mon 19 OctWaldshut 05:540 min—
Sun 18 OctWaldshut 05:550 min—
Sat 17 OctWaldshut 05:540 min—
Fri 16 OctKoblenz 05:430 min—
Thu 15 OctKoblenz 05:43−1 min—
Wed 14 OctKoblenz 05:430 min—
Tue 13 OctKoblenz 05:46+4 min+4 min
Mon 12 OctKoblenz 05:430 min—
Sun 11 OctKoblenz 05:430 min—
Sat 10 OctKoblenz 05:430 min—
Fri 9 OctKoblenz 05:42−1 min—