S10 12085 Wil SG – Romanshorn

View line S10

Wil SG 21:32 → Romanshorn 22:23 Daily 0 h 51 min · 16 stops Thurbo

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 21:32 from Wil SG · Sun 8 Nov

Next departure 21:32 today · Wil SG
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 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 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

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

  • Early 3% · 1
  • On time 97% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
21:32on time on time
21:35≈ on time ≈ on time
21:36≈ on time ≈ on time
21:38≈ on time ≈ on time
21:40≈ on time ≈ on time
21:43≈ on time ≈ on time
21:47≈ on time ≈ on time
21:50≈ on time ≈ on time
21:53≈ on time ≈ on time
21:59 / 22:00≈ on time ≈ on time
22:03≈ on time ≈ on time
22:06 / 22:07≈ on time ≈ on time
22:10≈ on time ≈ on time
22:13≈ on time ≈ +1 min
22:16 / 22:17≈ on time ≈ +1 min
22:23on 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 7 NovRomanshorn 22:240 min—
Fri 6 NovRomanshorn 22:250 min—
Thu 5 NovRomanshorn 22:230 min—
Wed 4 NovRomanshorn 22:240 min—
Tue 3 NovRomanshorn 22:240 min—
Mon 2 NovRomanshorn 22:240 min—
Sun 1 NovRomanshorn 22:240 min—
Sat 31 OctRomanshorn 22:240 min—
Fri 30 OctRomanshorn 22:240 min—
Thu 29 OctRomanshorn 22:240 min—
Wed 28 OctRomanshorn 22:240 min—
Tue 27 OctRomanshorn 22:240 min—
Mon 26 OctRomanshorn 22:26+1 min+1 min
Sun 25 OctRomanshorn 22:240 min—
Sat 24 OctRomanshorn 22:23−1 min—
Fri 23 OctRomanshorn 22:240 min—
Thu 22 OctRomanshorn 22:24−1 min—
Wed 21 OctRomanshorn 22:230 min—
Tue 20 OctRomanshorn 22:240 min—
Mon 19 OctRomanshorn 22:240 min—
Sun 18 OctRomanshorn 22:240 min—
Sat 17 OctRomanshorn 22:26+2 min+2 min
Fri 16 OctRomanshorn 22:240 min—
Thu 15 OctRomanshorn 22:240 min—
Wed 14 OctRomanshorn 22:240 min—
Tue 13 OctRomanshorn 22:240 min—
Mon 12 OctRomanshorn 22:37+2 min+2 min
Sun 11 OctRomanshorn 22:36+1 min—
Sat 10 OctRomanshorn 22:240 min—
Fri 9 OctRomanshorn 22:240 min—