S10 12032 Romanshorn → Wil SG

View line S10

Romanshorn 09:37 → Wil SG 10:27 Daily 0 h 50 min · 16 stops Thurbo

✓ Today’s run finished

Today it reached Wil SG at 10:27 −1 min

  1. Romanshorn09:37
  2. Erlen09:47
  3. Bürglen TG09:53
  4. Oppikon10:07
  5. Tobel-Affeltrangen10:15
  6. Bronschhofen AMP10:21
  7. Wil SG10:27

Next service: tomorrow 09:37 from Romanshorn · Sun 22 Nov

Next departure 09:37 tomorrow · Romanshorn
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 2 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 Wil SG, 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

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

  • Early 15% · 7
  • On time 85% · 41
  • 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=7
  • 100% T n=5
  • 100% F n=7
  • 100% S n=8
  • 100% S n=7

Stops and timetable

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

Last 90 days, 48 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:37on time on time
09:42≈ on time ≈ on time
09:44≈ on time ≈ on time
09:47≈ on time ≈ on time
09:51≈ on time ≈ on time
09:53≈ on time ≈ on time
10:00 / 10:02≈ on time ≈ on time
10:05≈ on time ≈ on time
10:07≈ on time ≈ on time
10:10≈ on time ≈ on time
10:15≈ on time ≈ on time
10:16≈ on time ≈ on time
10:18≈ on time ≈ on time
10:21≈ on time ≈ on time
10:22≈ on time ≈ on time
10:27on 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
Sat 21 NovWil SG 10:27−1 min—
Fri 20 NovWil SG 10:27−1 min—
Thu 19 NovWil SG 10:28No data—
Wed 18 NovWil SG 10:270 min—
Tue 17 NovWil SG 10:280 min—
Mon 16 NovWil SG 10:270 min—
Sun 15 NovWil SG 10:29+1 min—
Sat 14 NovWil SG 10:240 min—
Fri 13 NovWil SG 10:27−1 min—
Thu 12 NovWil SG 10:290 min—
Wed 11 NovWil SG 10:280 min—
Tue 10 NovWil SG 10:280 min—
Mon 9 NovWil SG 10:240 min—
Sun 8 NovWil SG 10:28−1 min—
Sat 7 NovWil SG 10:280 min—
Fri 6 NovWil SG 10:27−1 min—
Thu 5 NovWil SG 10:290 min—
Wed 4 NovWil SG 10:29+2 min+2 min
Tue 3 NovWil SG 10:27−1 min—
Mon 2 NovWil SG 10:28−1 min—
Sun 1 NovWil SG 10:27−1 min—
Sat 31 OctWil SG 10:280 min—
Fri 30 OctWil SG 10:280 min—
Thu 29 OctWil SG 10:28No data—
Wed 28 OctWil SG 10:290 min—
Tue 27 OctWil SG 10:290 min—
Mon 26 OctWil SG 10:27−1 min—
Sun 25 OctWil SG 10:28+1 min—
Sat 24 OctWil SG 10:28+1 min—
Fri 23 OctWil SG 10:280 min—