S9 11953 Wattwil – Wil SG

View line S9

Wattwil 13:35 → Wil SG 13:58 Daily 0 h 23 min · 7 stops Thurbo

✓ Today’s run finished

Today it reached Wil SG at 13:58 0 min

  1. Wattwil13:35
  2. Lichtensteig13:37
  3. Dietfurt13:41
  4. Bütschwil13:44
  5. Lütisburg13:47
  6. Bazenheid13:51
  7. Wil SG13:58

Next service: tomorrow 13:35 from Wattwil · Wed 11 Nov

Next departure 13:35 tomorrow · Wattwil
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 7 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: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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
13:35on time on time
13:37≈ on time ≈ on time
13:41≈ on time ≈ on time
13:44≈ on time ≈ on time
13:47≈ on time ≈ on time
13:51≈ on time ≈ +1 min
13:58on 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
Tue 10 NovWil SG 13:590 min—
Mon 9 NovWil SG 13:59No data—
Sun 8 NovWil SG 13:58−1 min—
Sat 7 NovWil SG 13:580 min—
Fri 6 NovWil SG 13:58−1 min—
Thu 5 NovWil SG 13:59No data—
Wed 4 NovWil SG 13:590 min—
Tue 3 NovWil SG 13:58−1 min—
Mon 2 NovWil SG 13:59No data—
Sun 1 NovWil SG 13:590 min—
Sat 31 OctWil SG 13:58−1 min—
Fri 30 OctWil SG 13:590 min—
Thu 29 OctWil SG 13:59No data—
Wed 28 OctWil SG 13:590 min—
Tue 27 OctWil SG 13:590 min—
Mon 26 OctWil SG 13:590 min—
Sun 25 OctWil SG 13:58−1 min—
Sat 24 OctWil SG 13:58−1 min—
Fri 23 OctWil SG 13:58−1 min—
Thu 22 OctWil SG 13:59No data—
Wed 21 OctWil SG 13:58−1 min—
Tue 20 OctWil SG 13:590 min—
Mon 19 OctWil SG 13:59No data—
Sun 18 OctWil SG 13:58−1 min—
Sat 17 OctWil SG 13:590 min—
Fri 16 OctWil SG 13:580 min—
Thu 15 OctWil SG 13:59No data—
Wed 14 OctWil SG 13:590 min—
Tue 13 OctWil SG 14:01+1 min+1 min
Mon 12 OctWil SG 14:00+1 min+1 min