S10 12023 Wil SG – Romanshorn

View line S10

Wil SG 06:02 → Romanshorn 06:53 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 16 stops Thurbo

Running now · updated 06:52

Position estimated from the timetable

Between Amriswil and Romanshorn 0 min

Estimated arrival at Romanshorn 06:53 · 65 km/h

  1. Wil SG06:02
  2. Bettwiesen06:08
  3. Tobel-Affeltrangen06:13
  4. Bussnang06:23
  5. Bürglen TG06:35
  6. Amriswil06:47
  7. Romanshorn06:53

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 22 runs arrived on time.

On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 0 no data
Typical delay
+1min
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

Worst days

  • Tue 10 Nov Max en route +4 min · last fix heading to Romanshorn +4 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Romanshorn +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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 10Today
06:02on time on timePassed
06:05≈ on time ≈ on timePassed
06:06≈ on time ≈ on timePassed
06:08≈ on time ≈ on timePassed
06:10≈ on time ≈ on timePassed
06:13≈ on time ≈ on timePassed
06:17≈ on time ≈ +1 minPassed
06:20≈ on time ≈ +1 minPassed
06:23≈ on time ≈ +1 minPassed
06:30 / 06:32≈ on time ≈ +1 minPassed
06:35≈ on time ≈ +1 minPassed
06:38≈ on time ≈ +1 minPassed
06:41≈ on time ≈ +1 minPassed
06:44≈ on time ≈ +1 minPassed
06:47≈ on time ≈ +1 minPassed
06:53+1 min +1 minNext

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
Tue 17 NovRomanshorn 06:490 min—
Mon 16 NovRomanshorn 06:540 min—
Fri 13 NovRomanshorn 06:540 min—
Thu 12 NovRomanshorn 06:55+1 min—
Wed 11 NovRomanshorn 06:540 min—
Tue 10 NovRomanshorn 06:58+4 min+4 min
Mon 9 NovRomanshorn 06:540 min—
Fri 6 NovRomanshorn 06:540 min—
Thu 5 NovRomanshorn 06:54+1 min—
Wed 4 NovRomanshorn 06:540 min—
Tue 3 NovRomanshorn 06:540 min+1 min
Mon 2 NovRomanshorn 06:54+1 min+1 min
Fri 30 OctRomanshorn 06:540 min—
Thu 29 OctRomanshorn 06:56+2 min+2 min
Wed 28 OctRomanshorn 06:56+1 min+1 min
Tue 27 OctRomanshorn 06:550 min—
Mon 26 OctRomanshorn 06:540 min—
Fri 23 OctRomanshorn 06:55+1 min—
Thu 22 OctRomanshorn 06:550 min—
Wed 21 OctRomanshorn 06:55+1 min—
Tue 20 OctRomanshorn 06:55+1 min—
Mon 19 OctRomanshorn 06:540 min—
Fri 16 OctRomanshorn 06:54+1 min—
Thu 15 OctRomanshorn 06:57+3 min+3 min
Wed 14 OctRomanshorn 06:55+1 min+2 min
Tue 13 OctRomanshorn 06:540 min—
Mon 12 OctRomanshorn 06:55+1 min+1 min
Fri 9 OctRomanshorn 06:55+1 min—
Thu 8 OctRomanshorn 06:55+1 min—
Wed 7 OctRomanshorn 06:540 min—