S7 11736 Rorschach – Weinfelden

View line S7

Rorschach 09:54 → Weinfelden 10:33 Daily 0 h 39 min · 10 stops Thurbo

✓ Today’s run finished

Today it reached Weinfelden at 10:34 +1 min

  1. Rorschach09:54
  2. Horn09:59
  3. Steinach10:01
  4. Arbon Seemoosriet10:06
  5. Egnach10:09
  6. Amriswil10:22
  7. Weinfelden10:33

Next service: tomorrow 09:54 from Rorschach · Tue 17 Nov

Next departure 09:54 tomorrow · Rorschach
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 44 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 Weinfelden, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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
09:54on time on time
09:56≈ on time ≈ on time
09:59≈ on time ≈ on time
10:01≈ on time ≈ on time
10:03 / 10:04≈ on time ≈ on time
10:06≈ on time ≈ +1 min
10:09≈ on time ≈ +1 min
10:13 / 10:17≈ on time ≈ +1 min
10:22≈ on time ≈ +1 min
10:33on 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 NovWeinfelden 10:34+1 min+1 min
Sun 15 NovWeinfelden 10:33−1 min—
Sat 14 NovWeinfelden 10:33−1 min—
Fri 13 NovWeinfelden 10:340 min—
Thu 12 NovWeinfelden 10:340 min—
Wed 11 NovWeinfelden 10:340 min—
Tue 10 NovWeinfelden 10:33−1 min—
Mon 9 NovWeinfelden 10:340 min—
Sun 8 NovWeinfelden 10:340 min—
Sat 7 NovWeinfelden 10:330 min—
Fri 6 NovWeinfelden 10:34+1 min—
Thu 5 NovWeinfelden 10:34+1 min—
Wed 4 NovWeinfelden 10:340 min—
Tue 3 NovWeinfelden 10:340 min—
Mon 2 NovWeinfelden 10:340 min—
Sun 1 NovWeinfelden 10:340 min—
Sat 31 OctWeinfelden 10:340 min—
Fri 30 OctWeinfelden 10:36+2 min+2 min
Thu 29 OctWeinfelden 10:34No data—
Wed 28 OctWeinfelden 10:36+2 min+2 min
Tue 27 OctWeinfelden 10:340 min—
Mon 26 OctWeinfelden 10:350 min—
Sun 25 OctWeinfelden 10:340 min—
Sat 24 OctWeinfelden 10:36+3 min+3 min
Fri 23 OctWeinfelden 10:340 min—
Thu 22 OctWeinfelden 10:350 min—
Wed 21 OctWeinfelden 10:35+1 min+1 min
Tue 20 OctWeinfelden 10:350 min—
Mon 19 OctWeinfelden 10:35+1 min+1 min
Sun 18 OctWeinfelden 10:340 min—