S7 11777 Romanshorn – Rorschach

View line S7

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 20:16 from Romanshorn · Sat 14 Nov

Next departure 20:16 today · Romanshorn
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 44 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 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

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

  • Early 23% · 10
  • On time 77% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=6
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 44 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
20:16on time on time
20:19≈ on time ≈ on time
20:22≈ on time ≈ on time
20:24 / 20:25≈ on time ≈ on time
20:26≈ on time ≈ on time
20:29 / 20:30≈ on time ≈ on time
20:33≈ 1 min early ≈ on time
20: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 13 NovRorschach 20:340 min—
Thu 12 NovRorschach 20:37−1 min—
Wed 11 NovRorschach 20:340 min—
Tue 10 NovRorschach 20:340 min—
Mon 9 NovRorschach 20:37+1 min—
Sun 8 NovRorschach 20:340 min—
Sat 7 NovRorschach 20:34−1 min—
Fri 6 NovRorschach 20:330 min—
Thu 5 NovRorschach 20:340 min—
Wed 4 NovRorschach 20:340 min—
Tue 3 NovRorschach 20:340 min—
Mon 2 NovRorschach 20:340 min—
Sun 1 NovRorschach 20:340 min—
Sat 31 OctRorschach 20:370 min—
Fri 30 OctRorschach 20:36−1 min—
Thu 29 OctRorschach 20:370 min—
Wed 28 OctRorschach 20:36−1 min—
Tue 27 OctRorschach 20:36−1 min—
Mon 26 OctRorschach 20:36−1 min—
Sun 25 OctRorschach 20:370 min—
Sat 24 OctRorschach 20:36−1 min—
Fri 23 OctRorschach 20:35−2 min—
Thu 22 OctRorschach 20:36−1 min—
Wed 21 OctRorschach 20:36−1 min—
Tue 20 OctRorschach 20:36−1 min—
Mon 19 OctRorschach 20:370 min—
Sun 18 OctRorschach 20:36−1 min—
Sat 17 OctRorschach 20:370 min—
Fri 16 OctRorschach 20:36−1 min—
Thu 15 OctRorschach 20:36−1 min—