S10 12040 Romanshorn – Wil SG

View line S10

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

✓ Today’s run finished

Today, last fix heading to Wil SG at 12:28 No data

  1. Romanshorn11:37
  2. Erlen11:47
  3. Bürglen TG11:53
  4. Oppikon12:07
  5. Tobel-Affeltrangen12:15
  6. Bronschhofen AMP12:21
  7. Wil SG12:27

Next service: tomorrow 11:37 from Romanshorn · Fri 6 Nov

Next departure 11:37 tomorrow · Romanshorn
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 8 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

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

  • Early 11% · 3
  • On time 89% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=5
  • 100% T n=1
  • 100% F n=4
  • 100% S n=4
  • 100% S n=7

Stops and timetable

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

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