S7 11758 Rorschach – Romanshorn

View line S7

Rorschach 15:24 → Romanshorn 15:43 Daily 0 h 19 min · 8 stops Thurbo

✓ Today’s run finished

Today it reached Romanshorn at 15:44 +1 min

  1. Rorschach15:24
  2. Rorschach Hafen15:26
  3. Horn15:29
  4. Arbon15:33
  5. Arbon Seemoosriet15:36
  6. Egnach15:39
  7. Romanshorn15:43

Next service: tomorrow 15:24 from Rorschach · Thu 19 Nov

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

Worst days

  • Thu 15 Oct Max en route +8 min · last fix heading to Romanshorn +7 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Romanshorn +4 min
  • Fri 30 Oct Max en route +3 min · last fix heading to Romanshorn +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 42
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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
15:24+1 min +1 min
15:26≈ +1 min ≈ +1 min
15:29≈ +1 min ≈ +1 min
15:31≈ +1 min ≈ +2 min
15:33 / 15:34≈ +1 min ≈ +2 min
15:36≈ +1 min ≈ +2 min
15:39≈ +1 min ≈ +2 min
15:43+1 min +3 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
Wed 18 NovRomanshorn 15:44+1 min+1 min
Tue 17 NovRomanshorn 15:47+3 min+3 min
Mon 16 NovRomanshorn 15:44+1 min+1 min
Sun 15 NovRomanshorn 15:430 min—
Sat 14 NovRomanshorn 15:440 min—
Fri 13 NovRomanshorn 15:44+1 min+1 min
Thu 12 NovRomanshorn 15:44+1 min+1 min
Wed 11 NovRomanshorn 15:47+3 min+3 min
Tue 10 NovRomanshorn 15:44+1 min—
Mon 9 NovRomanshorn 15:440 min—
Sun 8 NovRomanshorn 15:47+3 min+3 min
Sat 7 NovRomanshorn 15:440 min—
Fri 6 NovRomanshorn 15:44+1 min—
Thu 5 NovRomanshorn 15:47+2 min+2 min
Wed 4 NovRomanshorn 15:44+1 min+1 min
Tue 3 NovRomanshorn 15:440 min—
Mon 2 NovRomanshorn 15:440 min—
Sun 1 NovRomanshorn 15:47+3 min+5 min
Sat 31 OctRomanshorn 15:44+1 min—
Fri 30 OctRomanshorn 15:47+3 min+3 min
Thu 29 OctRomanshorn 15:45+1 min—
Wed 28 OctRomanshorn 15:45+1 min—
Tue 27 OctRomanshorn 15:440 min—
Mon 26 OctRomanshorn 15:440 min—
Sun 25 OctRomanshorn 15:46+2 min+2 min
Sat 24 OctRomanshorn 15:440 min—
Fri 23 OctRomanshorn 15:44+1 min—
Thu 22 OctRomanshorn 15:44No data—
Wed 21 OctRomanshorn 15:440 min—
Tue 20 OctRomanshorn 15:45+1 min—