S25 5032 Heiden → Rorschach

View line S25

Heiden 17:30 → Rorschach 17:47 Daily 0 h 17 min · 7 stops Appenzeller Bahnen

S25 5032 Heiden–Rorschach: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: −1 min. TrainsRadar data as of 21 Nov 2026, 20:12 (GMT+1).

✓ Today’s run finished

Today it reached Rorschach at 17:47 −1 min

  1. Heiden17:30
  2. Schwendi bei Heiden17:34
  3. Wienacht-Tobel17:36
  4. Wartensee17:38
  5. Sandbüchel17:40
  6. Seebleiche17:41
  7. Rorschach17:47

Next service: tomorrow 17:30 from Heiden · Sun 22 Nov

Next departure 17:30 tomorrow · Heiden
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%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Rorschach, 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 17 Nov Max en route +3 min · last fix heading to Rorschach +3 min

Distribution · 90 days

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

  • Early 55% · 27
  • On time 43% · 21
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 49 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:30on time on time
17:34≈ on time ≈ on time
17:36≈ on time ≈ on time
17:38≈ 1 min early ≈ on time
17:40≈ 1 min early ≈ on time
17:41≈ 1 min early ≈ on time
17:471 min early 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 21 NovRorschach 17:47−1 min—
Fri 20 NovRorschach 17:47+1 min+1 min
Thu 19 NovRorschach 17:47−1 min—
Wed 18 NovRorschach 17:440 min—
Tue 17 NovRorschach 17:52+3 min+3 min
Mon 16 NovRorschach 17:49+1 min+1 min
Sun 15 NovRorschach 17:47−1 min—
Sat 14 NovRorschach 17:440 min—
Fri 13 NovRorschach 17:47−1 min—
Thu 12 NovRorschach 17:480 min—
Wed 11 NovRorschach 17:440 min—
Tue 10 NovRorschach 17:480 min—
Mon 9 NovRorschach 17:490 min—
Sun 8 NovRorschach 17:44−1 min—
Sat 7 NovRorschach 17:440 min—
Fri 6 NovRorschach 17:470 min—
Thu 5 NovRorschach 17:440 min—
Wed 4 NovRorschach 17:440 min—
Tue 3 NovRorschach 17:490 min—
Mon 2 NovRorschach 17:47−2 min—
Sun 1 NovRorschach 17:49−4 min—
Sat 31 OctRorschach 17:48−5 min—
Fri 30 OctRorschach 17:49−4 min—
Thu 29 OctRorschach 17:49−4 min—
Wed 28 OctRorschach 17:50−3 min—
Tue 27 OctRorschach 17:50−3 min—
Mon 26 OctRorschach 17:50−4 min—
Sun 25 OctRorschach 17:49−3 min—
Sat 24 OctRorschach 17:48−5 min—
Fri 23 OctRorschach 17:49−4 min—