S7 11792 Rorschach – Romanshorn

View line S7

Rorschach 23:54 → Romanshorn 00:13 Daily 0 h 19 min · 8 stops Thurbo

Running now · updated 00:10

Between Egnach and Romanshorn +1 min

Estimated arrival at Romanshorn 00:14 · 52 km/h

  1. Rorschach23:54
  2. Rorschach Hafen23:56
  3. Horn23:59
  4. Arbon00:03
  5. Arbon Seemoosriet00:06
  6. Egnach00:09
  7. Romanshorn00:13

Today it is running no worse than usual: typical arrival delay is +1 min; 100% of the last 29 runs arrived on time.

On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 28 full · 1 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 34 full · 1 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Romanshorn, 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

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

  • Early 0% · 0
  • On time 100% · 35
  • 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=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 10Today
23:54+1 min +1 minPassed
23:56≈ +1 min ≈ +1 minPassed
23:59≈ +1 min ≈ +1 minPassed
00:01≈ +1 min ≈ +1 minPassed
00:03 / 00:04≈ +1 min ≈ +1 minPassed
00:06≈ +1 min ≈ +1 minPassed
00:09≈ +1 min ≈ +1 minPassed
00:13+1 min +2 minNext

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 NovEgnach 00:09Partial coverage+1 min—
Thu 5 NovRomanshorn 00:140 min—
Wed 4 NovRomanshorn 00:14+1 min—
Tue 3 NovRomanshorn 00:140 min—
Mon 2 NovRomanshorn 00:14+1 min—
Sun 1 NovRomanshorn 00:140 min—
Sat 31 OctRomanshorn 00:15+1 min—
Fri 30 OctRomanshorn 00:140 min—
Thu 29 OctRomanshorn 00:16+2 min+2 min
Wed 28 OctRomanshorn 00:15+1 min+1 min
Tue 27 OctRomanshorn 00:140 min—
Mon 26 OctRomanshorn 00:15+1 min+1 min
Sun 25 OctRomanshorn 00:14+1 min—
Sat 24 OctRomanshorn 00:140 min—
Fri 23 OctRomanshorn 00:15+1 min—
Thu 22 OctRomanshorn 00:140 min—
Wed 21 OctRomanshorn 00:15+2 min+2 min
Tue 20 OctRomanshorn 00:150 min—
Mon 19 OctRomanshorn 00:15+1 min+1 min
Sun 18 OctRomanshorn 00:16+1 min+1 min
Sat 17 OctRomanshorn 00:14+1 min—
Fri 16 OctRomanshorn 00:15+1 min—
Thu 15 OctRomanshorn 00:15+1 min—
Wed 14 OctRomanshorn 00:140 min—
Tue 13 OctRomanshorn 00:16+2 min+2 min
Mon 12 OctRomanshorn 00:14+1 min—
Sun 11 OctRomanshorn 00:140 min—
Sat 10 OctRomanshorn 00:140 min—
Fri 9 OctRomanshorn 00:140 min—
Thu 8 OctRomanshorn 00:150 min—