S7 11754 Rorschach – Romanshorn

View line S7

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

✓ Today’s run finished

Today, last fix heading to Romanshorn at 14:44 No data

  1. Rorschach14:24
  2. Rorschach Hafen14:26
  3. Horn14:29
  4. Arbon14:33
  5. Arbon Seemoosriet14:36
  6. Egnach14:39
  7. Romanshorn14:43

Next service: tomorrow 14:24 from Rorschach · Tue 10 Nov

Next departure 14:24 tomorrow · Rorschach
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 8 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 8 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: +2 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

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