S7 11753 Romanshorn – Rorschach

View line S7

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

✓ Today’s run finished

Today it reached Rorschach at 14:36 0 min

  1. Romanshorn14:16
  2. Egnach14:19
  3. Arbon Seemoosriet14:22
  4. Steinach14:26
  5. Horn14:29
  6. Rorschach Hafen14:33
  7. Rorschach14:36

Next service: tomorrow 14:16 from Romanshorn · Sat 21 Nov

Next departure 14:16 tomorrow · Romanshorn
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 10 no data
Typical delay
0min
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

Worst days

  • Thu 27 Aug Max en route +25 min · last fix heading to Rorschach +10 min

Distribution · 90 days

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

  • Early 18% · 7
  • On time 79% · 31
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 75% T n=4
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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