S7 25893 Romanshorn – Bregenz

View line S7

Romanshorn 17:16 → Bregenz 18:00 Daily 0 h 44 min · 10 stops Thurbo

✓ Today’s run finished

Today it reached Bregenz at 18:00 0 min

  1. Romanshorn17:16
  2. Arbon Seemoosriet17:22
  3. Arbon17:24
  4. Horn17:29
  5. Rorschach Hafen17:33
  6. St. Margrethen SG17:50
  7. Bregenz18:00

Next service: tomorrow 17:16 from Romanshorn · Sat 21 Nov

Next departure 17:16 tomorrow · Romanshorn
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
93%
42/45 runs under 3 min
RT coverage: 45 full · 0 partial · 3 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 Bregenz, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 16 Nov Max en route +6 min · last fix heading to Bregenz +6 min
  • Sat 17 Oct Max en route +4 min · last fix heading to Bregenz +4 min
  • Wed 18 Nov Max en route +3 min · last fix heading to Bregenz +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

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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
17:16on time on time
17:19≈ on time ≈ on time
17:22≈ on time ≈ on time
17:24 / 17:25≈ on time ≈ on time
17:26≈ on time ≈ on time
17:29 / 17:30≈ on time ≈ +1 min
17:33≈ on time ≈ +1 min
17:36 / 17:42≈ on time ≈ +1 min
17:50 / 17:51≈ on time ≈ +2 min
18:00on 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
Fri 20 NovBregenz 17:590 min—
Thu 19 NovBregenz 18:02+1 min—
Wed 18 NovBregenz 18:04+3 min+3 min
Tue 17 NovBregenz 18:04+2 min+2 min
Mon 16 NovBregenz 18:04+6 min+6 min
Sun 15 NovBregenz 17:59No data—
Sat 14 NovBregenz 17:590 min—
Fri 13 NovBregenz 18:020 min—
Thu 12 NovBregenz 17:59+1 min—
Wed 11 NovBregenz 17:59+1 min—
Tue 10 NovBregenz 17:590 min—
Mon 9 NovBregenz 17:590 min—
Sun 8 NovBregenz 17:590 min—
Sat 7 NovBregenz 17:590 min—
Fri 6 NovBregenz 17:590 min—
Thu 5 NovBregenz 18:03+2 min+2 min
Wed 4 NovBregenz 17:59−1 min—
Tue 3 NovBregenz 17:590 min—
Mon 2 NovBregenz 18:020 min—
Sun 1 NovBregenz 18:010 min—
Sat 31 OctBregenz 18:010 min—
Fri 30 OctBregenz 18:010 min—
Thu 29 OctBregenz 18:03+2 min+2 min
Wed 28 OctBregenz 18:01+3 min+3 min
Tue 27 OctBregenz 18:020 min—
Mon 26 OctBregenz 18:01No data—
Sun 25 OctBregenz 18:010 min—
Sat 24 OctBregenz 18:010 min—
Fri 23 OctBregenz 18:010 min—
Thu 22 OctBregenz 18:020 min—