S25 5015 Rorschach → Heiden

View line S25

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

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

✓ Today’s run finished

Today it reached Heiden at 09:25 0 min

  1. Rorschach09:11
  2. Seebleiche09:13
  3. Sandbüchel09:14
  4. Wartensee09:15
  5. Wienacht-Tobel09:17
  6. Schwendi bei Heiden09:19
  7. Heiden09:25

Next service: tomorrow 09:11 from Rorschach · Sun 22 Nov

Next departure 09:11 tomorrow · Rorschach
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 1 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Mon 16 Nov Max en route +3 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 65% · 31
  • On time 33% · 16
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=6
  • 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, 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
09:113 min early 1 min early
09:13≈ 3 min early ≈ 1 min early
09:14≈ 3 min early ≈ 1 min early
09:15≈ 3 min early ≈ 1 min early
09:17≈ 2 min early ≈ 1 min early
09:19≈ 2 min early ≈ on time
09:252 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 NovHeiden 09:240 min—
Fri 20 NovHeiden 09:27+1 min—
Thu 19 NovHeiden 09:24No data—
Wed 18 NovHeiden 09:24−2 min—
Tue 17 NovHeiden 09:250 min—
Mon 16 NovHeiden 09:29+3 min+3 min
Sun 15 NovHeiden 09:24−1 min—
Sat 14 NovHeiden 09:24−1 min—
Fri 13 NovHeiden 09:28+1 min+1 min
Thu 12 NovHeiden 09:24−1 min—
Wed 11 NovHeiden 09:24−1 min—
Tue 10 NovHeiden 09:27+1 min+1 min
Mon 9 NovHeiden 09:240 min—
Sun 8 NovHeiden 09:240 min—
Sat 7 NovHeiden 09:24−2 min—
Fri 6 NovHeiden 09:24−1 min—
Thu 5 NovHeiden 09:24−1 min—
Wed 4 NovHeiden 09:24−1 min—
Tue 3 NovHeiden 09:27+1 min—
Mon 2 NovHeiden 09:24−1 min—
Sun 1 NovHeiden 09:26−2 min—
Sat 31 OctHeiden 09:27−2 min—
Fri 30 OctHeiden 09:26−3 min—
Thu 29 OctHeiden 09:26−3 min—
Wed 28 OctHeiden 09:27−1 min—
Tue 27 OctHeiden 09:25−3 min—
Mon 26 OctHeiden 09:25−3 min—
Sun 25 OctHeiden 09:26−3 min—
Sat 24 OctHeiden 09:27−2 min—
Fri 23 OctHeiden 09:270 min—