S26 6131 Rheineck – Walzenhausen

View line S26

Rheineck 13:05 → Walzenhausen 13:11 Daily 0 h 06 min · 3 stops Appenzeller Bahnen

✓ Today’s run finished

Today, last fix heading to Walzenhausen at 13:13 No data

  1. Rheineck13:05
  2. Ruderbach13:06
  3. Walzenhausen13:11

Next service: tomorrow 13:05 from Rheineck · Wed 18 Nov

Next departure 13:05 tomorrow · Rheineck
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
96%
69/72 runs under 3 min
RT coverage: 72 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −2 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Walzenhausen, 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 4 Nov Max en route +10 min · last fix heading to Brig +10 min
  • Sat 26 Sept Max en route +4 min · last fix heading to Walzenhausen +4 min
  • Mon 21 Sept Max en route +4 min · last fix heading to Walzenhausen +4 min

Distribution · 90 days

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

  • Early 46% · 33
  • On time 50% · 36
  • 3–10 min 3% · 2
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 100% T n=9
  • 88% W n=8
  • 100% T n=11
  • 100% F n=11
  • 91% S n=11
  • 100% S n=12

Stops and timetable

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

Last 90 days, 72 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
13:05on time on time
13:06≈ on time ≈ on time
13:111 min early +1 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
Tue 17 NovWalzenhausen 13:13No data—
Mon 16 NovBrig 20:54−2 min—
Sun 15 NovBrig 20:54−3 min—
Sat 14 NovBrig 20:55−3 min—
Fri 13 NovBrig 20:54−2 min—
Thu 12 NovBrig 21:00+3 min+3 min
Wed 11 NovBrig 20:540 min—
Tue 10 NovBrig 20:540 min—
Mon 9 NovBrig 20:53−3 min—
Sun 8 NovBrig 20:54−2 min—
Sat 7 NovBrig 20:570 min—
Fri 6 NovBrig 20:54−1 min—
Thu 5 NovBrig 20:54−2 min—
Wed 4 NovBrig 21:07+10 min+10 min
Tue 3 NovBrig 20:54−2 min—
Mon 2 NovBrig 20:54−1 min—
Sun 1 NovBrig 20:54−1 min—
Sat 31 OctBrig 20:54−2 min—
Fri 30 OctBrig 20:56−1 min—
Thu 29 OctBrig 20:55−2 min—
Wed 28 OctBrig 20:55−2 min—
Tue 27 OctBrig 20:55−2 min—
Mon 26 OctBrig 20:570 min—
Sun 25 OctBrig 20:55−1 min—
Sat 24 OctBrig 20:54−2 min—
Fri 23 OctBrig 20:55−2 min—
Thu 22 OctBrig 20:54−3 min—
Wed 21 OctBrig 20:54−2 min—
Tue 20 OctBrig 20:570 min—
Mon 19 OctBrig 20:54−2 min—