S7 11789 Romanshorn – Rorschach

View line S7

Romanshorn 23:16 → Rorschach 23:36 Daily 0 h 20 min · 8 stops Thurbo

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 23:16 from Romanshorn · Sat 7 Nov

Next departure 23:16 today · Romanshorn
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 1 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 Rorschach, 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

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

  • Early 37% · 16
  • On time 63% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 100% W n=5
  • 100% T n=5
  • 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, 43 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
23:16on time on time
23:19≈ on time ≈ on time
23:22≈ on time ≈ on time
23:24 / 23:25≈ on time ≈ on time
23:26≈ on time ≈ on time
23:29 / 23:30≈ 1 min early ≈ on time
23:33≈ 1 min early ≈ +1 min
23:361 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
Fri 6 NovRorschach 23:340 min—
Thu 5 NovRorschach 23:34−1 min—
Wed 4 NovRorschach 23:34−1 min—
Tue 3 NovRorschach 23:340 min—
Mon 2 NovRorschach 23:37No data—
Sun 1 NovRorschach 23:340 min—
Sat 31 OctRorschach 23:36−1 min—
Fri 30 OctRorschach 23:36−1 min—
Thu 29 OctRorschach 23:36−1 min—
Wed 28 OctRorschach 23:36−1 min—
Tue 27 OctRorschach 23:370 min—
Mon 26 OctRorschach 23:36−1 min—
Sun 25 OctRorschach 23:360 min—
Sat 24 OctRorschach 23:370 min+1 min
Fri 23 OctRorschach 23:38+1 min—
Thu 22 OctRorschach 23:36−1 min—
Wed 21 OctRorschach 23:370 min—
Tue 20 OctRorschach 23:37−1 min—
Mon 19 OctRorschach 23:36−1 min—
Sun 18 OctRorschach 23:36−1 min—
Sat 17 OctRorschach 23:36−1 min—
Fri 16 OctRorschach 23:36−1 min—
Thu 15 OctRorschach 23:35−2 min—
Wed 14 OctRorschach 23:36−1 min—
Tue 13 OctRorschach 23:36−1 min—
Mon 12 OctRorschach 23:36−1 min—
Sun 11 OctRorschach 23:36−1 min—
Sat 10 OctRorschach 23:36−1 min—
Fri 9 OctRorschach 23:39+1 min+2 min
Thu 8 OctRorschach 23:39+2 min+2 min