S25 5013 Rorschach – Heiden

View line S25

Rorschach 08:11 → Heiden 08:25 Daily 0 h 14 min · 7 stops Appenzeller Bahnen

✓ Today’s run finished

Today it reached Heiden at 08:26 +1 min

  1. Rorschach08:11
  2. Seebleiche08:13
  3. Sandbüchel08:14
  4. Wartensee08:15
  5. Wienacht-Tobel08:17
  6. Schwendi bei Heiden08:19
  7. Heiden08:25

Next service: tomorrow 08:11 from Rorschach · Sat 21 Nov

Next departure 08:11 tomorrow · Rorschach
On-time · 30 days
100%
30/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
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sat 17 Oct Max en route +5 min · last fix heading to Heiden +5 min

Distribution · 90 days

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

  • Early 25% · 12
  • On time 73% · 35
  • 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
  • 83% S n=6
  • 100% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
08:111 min early on time
08:13≈ 1 min early ≈ on time
08:14≈ 1 min early ≈ on time
08:15≈ 1 min early ≈ on time
08:17≈ 1 min early ≈ on time
08:19≈ on time ≈ +1 min
08:25on 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
Fri 20 NovHeiden 08:24+1 min—
Thu 19 NovHeiden 08:240 min—
Wed 18 NovHeiden 08:240 min—
Tue 17 NovHeiden 08:240 min—
Mon 16 NovHeiden 08:240 min—
Sun 15 NovHeiden 08:24+1 min+1 min
Sat 14 NovHeiden 08:240 min—
Fri 13 NovHeiden 08:270 min—
Thu 12 NovHeiden 08:240 min—
Wed 11 NovHeiden 08:24+1 min—
Tue 10 NovHeiden 08:240 min—
Mon 9 NovHeiden 08:28+2 min+2 min
Sun 8 NovHeiden 08:23−4 min—
Sat 7 NovHeiden 08:23−1 min—
Fri 6 NovHeiden 08:24−1 min—
Thu 5 NovHeiden 08:23−1 min—
Wed 4 NovHeiden 08:240 min—
Tue 3 NovHeiden 08:240 min—
Mon 2 NovHeiden 08:27+1 min—
Sun 1 NovHeiden 08:24−2 min—
Sat 31 OctHeiden 08:25−1 min—
Fri 30 OctHeiden 08:25−1 min—
Thu 29 OctHeiden 08:250 min—
Wed 28 OctHeiden 08:26+2 min+2 min
Tue 27 OctHeiden 08:26+1 min+1 min
Mon 26 OctHeiden 08:26−1 min—
Sun 25 OctHeiden 08:260 min—
Sat 24 OctHeiden 08:27+1 min+1 min
Fri 23 OctHeiden 08:28+2 min+2 min
Thu 22 OctHeiden 08:29+2 min+2 min