S25 5019 Rorschach Hafen – Heiden

View line S25

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

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 11:01 from Rorschach Hafen · Sun 15 Nov

Next departure 11:01 today · Rorschach Hafen
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 6 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 7 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 Heiden, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 60% · 21
  • On time 40% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=6
  • 100% W n=6
  • 100% T n=2
  • 100% F n=6
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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