S10 12031 Wil SG – Romanshorn

View line S10

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

✓ Today’s run finished

Today it reached Romanshorn at 08:53 0 min

  1. Wil SG08:02
  2. Bettwiesen08:08
  3. Tobel-Affeltrangen08:13
  4. Bussnang08:23
  5. Bürglen TG08:35
  6. Oberaach08:44
  7. Romanshorn08:53

Next service: Monday 08:02 from Wil SG · Mon 9 Nov

Next departure 08:02 Monday · Wil SG
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 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

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

  • Early 0% · 0
  • On time 100% · 25
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
08:02on time on time
08:05≈ on time ≈ on time
08:06≈ on time ≈ on time
08:08≈ on time ≈ on time
08:10≈ on time ≈ on time
08:13≈ on time ≈ on time
08:17≈ on time ≈ on time
08:20≈ on time ≈ on time
08:23≈ on time ≈ +1 min
08:30 / 08:32≈ on time ≈ +1 min
08:35≈ on time ≈ +1 min
08:38≈ on time ≈ +1 min
08:41≈ on time ≈ +1 min
08:44≈ on time ≈ +1 min
08:47≈ on time ≈ +1 min
08:53on 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
Fri 6 NovRomanshorn 08:540 min—
Thu 5 NovRomanshorn 08:540 min—
Wed 4 NovRomanshorn 08:540 min—
Tue 3 NovRomanshorn 08:54+1 min+1 min
Mon 2 NovRomanshorn 08:540 min—
Fri 30 OctRomanshorn 08:55+1 min—
Thu 29 OctRomanshorn 08:540 min—
Wed 28 OctRomanshorn 08:55+1 min—
Tue 27 OctRomanshorn 08:540 min—
Mon 26 OctRomanshorn 08:550 min—
Fri 23 OctRomanshorn 08:56+2 min+2 min
Thu 22 OctRomanshorn 08:55+1 min—
Wed 21 OctRomanshorn 08:550 min—
Tue 20 OctRomanshorn 08:54−1 min—
Mon 19 OctRomanshorn 08:55+1 min—
Fri 16 OctRomanshorn 08:54+1 min—
Thu 15 OctRomanshorn 08:540 min—
Wed 14 OctRomanshorn 08:540 min—
Tue 13 OctRomanshorn 08:55+1 min—
Mon 12 OctRomanshorn 08:540 min—
Fri 9 OctRomanshorn 08:56+2 min+2 min
Thu 8 OctRomanshorn 08:540 min—
Wed 7 OctRomanshorn 08:540 min—
Tue 6 OctRomanshorn 08:540 min—
Mon 5 OctRomanshorn 08:54−1 min—