S25 5023 Rorschach Hafen → Heiden

View line S25

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

S25 5023 Rorschach Hafen–Heiden: final delay under 3 min on 22 of its 22 runs with data in the last 30 days (100%). Median final delay: −1 min. TrainsRadar data as of 21 Nov 2026, 16:13 (GMT+1).

✓ Today’s run finished

Today it reached Heiden at 13:25 −2 min

  1. Rorschach Hafen13:01
  2. Rorschach13:04
  3. Seebleiche13:13
  4. Wartensee13:15
  5. Wienacht-Tobel13:17
  6. Schwendi bei Heiden13:19
  7. Heiden13:25

Next service: tomorrow 13:01 from Rorschach Hafen · Sun 22 Nov

Next departure 13:01 tomorrow · Rorschach Hafen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 11 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
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

Distribution · 90 days

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

  • Early 50% · 19
  • On time 50% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=2
  • 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 (8 stops).

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