S7 25891 Romanshorn – Bregenz

View line S7

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

✓ Today’s run finished

Today it reached Bregenz at 16:00 0 min

  1. Romanshorn15:16
  2. Arbon Seemoosriet15:22
  3. Arbon15:24
  4. Horn15:29
  5. Rorschach Hafen15:33
  6. St. Margrethen SG15:50
  7. Bregenz16:00

Next service: tomorrow 15:16 from Romanshorn · Thu 19 Nov

Next departure 15:16 tomorrow · Romanshorn
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=3
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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:16on time on time
15:19≈ on time ≈ on time
15:22≈ on time ≈ on time
15:24 / 15:25≈ on time ≈ on time
15:26≈ on time ≈ on time
15:29 / 15:30≈ on time ≈ on time
15:33≈ on time ≈ on time
15:36 / 15:42≈ on time ≈ on time
15:50 / 15:51≈ on time ≈ +1 min
16:00on time +1 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 NovBregenz 15:590 min—
Tue 17 NovBregenz 16:02+1 min—
Mon 16 NovBregenz 15:590 min—
Sun 15 NovBregenz 15:590 min—
Sat 14 NovBregenz 16:03+2 min+2 min
Fri 13 NovBregenz 16:02+1 min—
Thu 12 NovBregenz 16:000 min—
Wed 11 NovBregenz 15:590 min—
Tue 10 NovBregenz 15:590 min—
Mon 9 NovBregenz 16:03+2 min+2 min
Sun 8 NovBregenz 15:590 min—
Sat 7 NovBregenz 16:02+1 min+1 min
Fri 6 NovBregenz 16:02+1 min—
Thu 5 NovBregenz 15:590 min—
Wed 4 NovBregenz 15:590 min—
Tue 3 NovBregenz 16:02+1 min—
Mon 2 NovBregenz 15:590 min—
Sun 1 NovBregenz 16:010 min—
Sat 31 OctBregenz 16:00−1 min—
Fri 30 OctBregenz 16:010 min—
Thu 29 OctBregenz 16:01No data—
Wed 28 OctBregenz 16:01No data—
Tue 27 OctBregenz 16:010 min—
Mon 26 OctBregenz 16:01No data—
Sun 25 OctBregenz 16:000 min—
Sat 24 OctBregenz 16:010 min—
Fri 23 OctBregenz 16:010 min—
Thu 22 OctBregenz 16:01No data—
Wed 21 OctBregenz 16:01+1 min—
Tue 20 OctBregenz 16:01−1 min—