S7 11719 Romanshorn – Rorschach

View line S7

Romanshorn 05:46 → Rorschach 06:06 Daily 0 h 20 min · 8 stops Thurbo

✓ Today’s run finished

Today it reached Rorschach at 06:06 0 min

  1. Romanshorn05:46
  2. Egnach05:49
  3. Arbon Seemoosriet05:52
  4. Steinach05:56
  5. Horn05:59
  6. Rorschach Hafen06:03
  7. Rorschach06:06

Next service: tomorrow 05:46 from Romanshorn · Sun 8 Nov

Next departure 05:46 tomorrow · Romanshorn
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Tue 3 Nov Max en route +5 min · last fix heading to Rorschach +5 min

Distribution · 90 days

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

  • Early 6% · 2
  • On time 91% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 80% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 35 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
05:46on time on time
05:49≈ on time ≈ on time
05:52≈ on time ≈ on time
05:54 / 05:55≈ on time ≈ on time
05:56≈ on time ≈ +1 min
05:59 / 06:00≈ on time ≈ +1 min
06:03≈ on time ≈ +1 min
06:06on time +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 7 NovRorschach 06:070 min—
Fri 6 NovRorschach 06:070 min—
Thu 5 NovRorschach 06:08+1 min+1 min
Wed 4 NovRorschach 06:070 min—
Tue 3 NovRorschach 06:12+5 min+5 min
Mon 2 NovRorschach 06:09+2 min+2 min
Sun 1 NovRorschach 06:070 min—
Sat 31 OctRorschach 06:070 min—
Fri 30 OctRorschach 06:070 min—
Thu 29 OctRorschach 06:070 min—
Wed 28 OctRorschach 06:070 min—
Tue 27 OctRorschach 06:070 min—
Mon 26 OctRorschach 06:070 min—
Sun 25 OctRorschach 06:06−1 min—
Sat 24 OctRorschach 06:070 min—
Fri 23 OctRorschach 06:070 min—
Thu 22 OctRorschach 06:07+1 min—
Wed 21 OctRorschach 06:070 min—
Tue 20 OctRorschach 06:070 min—
Mon 19 OctRorschach 06:070 min—
Sun 18 OctRorschach 06:070 min—
Sat 17 OctRorschach 06:070 min—
Fri 16 OctRorschach 06:060 min—
Thu 15 OctRorschach 06:070 min—
Wed 14 OctRorschach 06:08+1 min+1 min
Tue 13 OctRorschach 06:070 min—
Mon 12 OctRorschach 06:09+2 min+2 min
Sun 11 OctRorschach 06:060 min—
Sat 10 OctRorschach 06:080 min—
Fri 9 OctRorschach 06:070 min—