S25 5029 Rorschach Hafen → Heiden

View line S25

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

S25 5029 Rorschach Hafen–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 22 Nov 2026, 01:14 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 16:01 from Rorschach Hafen · Sun 22 Nov

Next departure 16:01 today · Rorschach Hafen
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 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
+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

Worst days

  • Fri 6 Nov Max en route +6 min · last fix heading to Heiden +6 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
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 86% 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, 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
16:013 min early 1 min early
16:04 / 16:11≈ 2 min early ≈ 1 min early
16:13≈ 2 min early ≈ on time
16:14≈ 1 min early ≈ on time
16:15≈ 1 min early ≈ on time
16:17≈ 1 min early ≈ on time
16:19≈ 1 min early ≈ on time
16: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 16:240 min—
Fri 20 NovHeiden 16:27+1 min+1 min
Thu 19 NovHeiden 16:24−1 min—
Wed 18 NovHeiden 16:24−1 min—
Tue 17 NovHeiden 16:240 min—
Mon 16 NovHeiden 16:24+1 min—
Sun 15 NovHeiden 16:24−1 min—
Sat 14 NovHeiden 16:27+1 min+2 min
Fri 13 NovHeiden 16:240 min—
Thu 12 NovHeiden 16:27+2 min+2 min
Wed 11 NovHeiden 16:240 min—
Tue 10 NovHeiden 16:240 min—
Mon 9 NovHeiden 16:24+1 min—
Sun 8 NovHeiden 16:24−1 min—
Sat 7 NovHeiden 16:24−1 min—
Fri 6 NovHeiden 16:32+6 min+6 min
Thu 5 NovHeiden 16:24−1 min—
Wed 4 NovHeiden 16:270 min—
Tue 3 NovHeiden 16:28+2 min+2 min
Mon 2 NovHeiden 16:24−1 min—
Sun 1 NovHeiden 16:25−3 min—
Sat 31 OctHeiden 16:25−3 min—
Fri 30 OctHeiden 16:26−3 min—
Thu 29 OctHeiden 16:26−2 min—
Wed 28 OctHeiden 16:28−1 min—
Tue 27 OctHeiden 16:290 min—
Mon 26 OctHeiden 16:27−3 min—
Sun 25 OctHeiden 16:26−3 min—
Sat 24 OctHeiden 16:26−3 min—
Fri 23 OctHeiden 16:25−3 min—