S7 11718 Rorschach – Romanshorn

View line S7

Rorschach 05:24 → Romanshorn 05:42 Daily 0 h 18 min · 8 stops Thurbo

✓ Today’s run finished

Today it reached Romanshorn at 05:43 +1 min

  1. Rorschach05:24
  2. Rorschach Hafen05:26
  3. Horn05:29
  4. Arbon05:33
  5. Arbon Seemoosriet05:36
  6. Egnach05:39
  7. Romanshorn05:42

Next service: tomorrow 05:24 from Rorschach · Sun 8 Nov

Next departure 05: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
94%
32/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 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

  • Tue 3 Nov Max en route +6 min · last fix heading to Romanshorn +6 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Romanshorn +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 60% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 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, 34 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:24+1 min +1 min
05:26≈ +1 min ≈ +1 min
05:29≈ +1 min ≈ +1 min
05:31≈ +1 min ≈ +1 min
05:33 / 05:34≈ +1 min ≈ +2 min
05:36≈ +1 min ≈ +2 min
05:39≈ +2 min ≈ +2 min
05:42+2 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
Sat 7 NovRomanshorn 05:44+1 min+1 min
Fri 6 NovRomanshorn 05:43No data—
Thu 5 NovRomanshorn 05:44+2 min+2 min
Wed 4 NovRomanshorn 05:44+1 min+1 min
Tue 3 NovRomanshorn 05:49+6 min+6 min
Mon 2 NovRomanshorn 05:44+2 min+2 min
Sun 1 NovRomanshorn 05:44+1 min+1 min
Sat 31 OctRomanshorn 05:44+1 min+1 min
Fri 30 OctRomanshorn 05:45+2 min+2 min
Thu 29 OctRomanshorn 05:45+2 min+2 min
Wed 28 OctRomanshorn 05:45+2 min+2 min
Tue 27 OctRomanshorn 05:45+2 min+2 min
Mon 26 OctRomanshorn 05:46+3 min+3 min
Sun 25 OctRomanshorn 05:44+1 min+1 min
Sat 24 OctRomanshorn 05:45+2 min+2 min
Fri 23 OctRomanshorn 05:45+2 min+2 min
Thu 22 OctRomanshorn 05:45+2 min+2 min
Wed 21 OctRomanshorn 05:44+1 min—
Tue 20 OctRomanshorn 05:45+2 min+2 min
Mon 19 OctRomanshorn 05:45+2 min+2 min
Sun 18 OctRomanshorn 05:44+1 min—
Sat 17 OctRomanshorn 05:44+1 min—
Fri 16 OctRomanshorn 05:46+3 min+3 min
Thu 15 OctRomanshorn 05:46+3 min+3 min
Wed 14 OctRomanshorn 05:45+2 min+2 min
Tue 13 OctRomanshorn 05:45+2 min+2 min
Mon 12 OctRomanshorn 05:44+2 min+2 min
Sun 11 OctRomanshorn 05:430 min—
Sat 10 OctRomanshorn 05:440 min—
Fri 9 OctRomanshorn 05:44+1 min+1 min