S4 11411 Buchs SG → Sargans

View line S4

Buchs SG 05:45 → Sargans 05:58 Mon, Tue, Wed, Thu, Fri 0 h 13 min · 3 stops SOB

S4 11411 Buchs SG–Sargans: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: −1 min. TrainsRadar data as of 21 Nov 2026, 11:47 (GMT+1).

It does not run today

Last recorded run: Friday 20 November −1 min

Next service: Monday 05:45 from Buchs SG · Mon 23 Nov

Next departure 05:45 Monday · Buchs SG
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Sargans, 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

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

  • Early 60% · 21
  • On time 40% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
05:45on time on time
05:48≈ on time ≈ on time
05:581 min early on time

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 20 NovSargans 05:58−1 min—
Thu 19 NovSargans 05:590 min—
Wed 18 NovSargans 05:58−1 min—
Tue 17 NovSargans 05:580 min—
Mon 16 NovSargans 05:590 min—
Fri 13 NovSargans 05:58−1 min—
Thu 12 NovSargans 05:57−1 min—
Wed 11 NovSargans 05:58−2 min—
Tue 10 NovSargans 05:58−1 min—
Mon 9 NovSargans 05:58−1 min—
Fri 6 NovSargans 05:58−2 min—
Thu 5 NovSargans 05:58−1 min—
Wed 4 NovSargans 05:58−1 min—
Tue 3 NovSargans 05:58−2 min—
Mon 2 NovSargans 05:59+1 min—
Fri 30 OctSargans 05:58−1 min—
Thu 29 OctSargans 05:590 min—
Wed 28 OctSargans 05:58−1 min—
Tue 27 OctSargans 05:58−1 min—
Mon 26 OctSargans 05:57−1 min—
Fri 23 OctSargans 05:58−1 min—
Thu 22 OctSargans 05:58−1 min—
Wed 21 OctSargans 05:590 min—
Tue 20 OctSargans 05:57−1 min—
Mon 19 OctSargans 05:58−1 min—
Fri 16 OctSargans 05:58−1 min—
Thu 15 OctSargans 05:58−1 min—
Wed 14 OctSargans 05:58−2 min—
Tue 13 OctSargans 05:57−1 min—
Mon 12 OctSargans 05:58−1 min—