S10 12073 Wil SG → Romanshorn

View line S10

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

S10 12073 Wil SG–Romanshorn: final delay under 3 min on 27 of its 30 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 19:44 (GMT+1).

✓ Today’s run finished

Today it reached Romanshorn at 19:23 0 min

  1. Wil SG18:32
  2. Bettwiesen18:38
  3. Tobel-Affeltrangen18:43
  4. Bussnang18:53
  5. Bürglen TG19:03
  6. Oberaach19:13
  7. Romanshorn19:23

Next service: tomorrow 18:32 from Wil SG · Mon 23 Nov

Next departure 18:32 tomorrow · Wil SG
On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
94%
47/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 9 Nov Max en route +5 min · last fix heading to Romanshorn +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Romanshorn +5 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Romanshorn +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=7
  • 86% T n=7
  • 86% F n=7
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

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