S7 11738 Rorschach – Romanshorn

View line S7

Rorschach 23:24 → Romanshorn 23:43 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 8 stops Thurbo

✓ Today’s run finished

Today it reached Romanshorn at 23:43 −1 min

  1. Rorschach23:24
  2. Rorschach Hafen23:26
  3. Horn23:29
  4. Arbon23:33
  5. Arbon Seemoosriet23:36
  6. Egnach23:39
  7. Romanshorn23:43

Next service: tomorrow 23:24 from Rorschach · Tue 17 Nov

Next departure 23:24 tomorrow · Rorschach
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 32 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

Worst days

  • Wed 28 Oct Max en route +5 min · last fix heading to Romanshorn +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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