S25 5031 Rorschach Hafen – Heiden

View line S25

Rorschach Hafen 17:01 → Heiden 17:25 Daily 0 h 24 min · 8 stops Appenzeller Bahnen

✓ Today’s run finished

Today it reached Heiden at 17:25 0 min

  1. Rorschach Hafen17:01
  2. Rorschach17:04
  3. Seebleiche17:13
  4. Wartensee17:15
  5. Wienacht-Tobel17:17
  6. Schwendi bei Heiden17:19
  7. Heiden17:25

Next service: tomorrow 17:01 from Rorschach Hafen · Sat 21 Nov

Next departure 17:01 tomorrow · Rorschach Hafen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Sun 15 Nov Max en route +7 min · last fix heading to Heiden +3 min

Distribution · 90 days

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

  • Early 52% · 25
  • On time 46% · 22
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 48 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
17:013 min early 1 min early
17:04 / 17:11≈ 3 min early ≈ 1 min early
17:13≈ 2 min early ≈ on time
17:14≈ 2 min early ≈ on time
17:15≈ 2 min early ≈ on time
17:17≈ 2 min early ≈ on time
17:19≈ 1 min early ≈ +1 min
17:251 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
Fri 20 NovHeiden 17:240 min—
Thu 19 NovHeiden 17:240 min—
Wed 18 NovHeiden 17:24−1 min—
Tue 17 NovHeiden 17:27+1 min+1 min
Mon 16 NovHeiden 17:28+2 min+2 min
Sun 15 NovHeiden 17:29+3 min+7 min
Sat 14 NovHeiden 17:240 min—
Fri 13 NovHeiden 17:240 min—
Thu 12 NovHeiden 17:27+1 min+1 min
Wed 11 NovHeiden 17:24−1 min—
Tue 10 NovHeiden 17:27+1 min+1 min
Mon 9 NovHeiden 17:27+2 min+2 min
Sun 8 NovHeiden 17:270 min—
Sat 7 NovHeiden 17:240 min—
Fri 6 NovHeiden 17:27+1 min—
Thu 5 NovHeiden 17:240 min—
Wed 4 NovHeiden 17:240 min—
Tue 3 NovHeiden 17:28+2 min+2 min
Mon 2 NovHeiden 17:24−1 min—
Sun 1 NovHeiden 17:25−3 min—
Sat 31 OctHeiden 17:25−3 min—
Fri 30 OctHeiden 17:25−3 min—
Thu 29 OctHeiden 17:280 min—
Wed 28 OctHeiden 17:28−1 min—
Tue 27 OctHeiden 17:28−2 min—
Mon 26 OctHeiden 17:27−2 min—
Sun 25 OctHeiden 17:26−3 min—
Sat 24 OctHeiden 17:25−4 min—
Fri 23 OctHeiden 17:26−3 min—
Thu 22 OctHeiden 17:26−4 min—