S1 21108 Sursee – Baar

View line S1

Sursee 04:47 → Baar 05:57 Daily 1 h 10 min · 23 stops SBB CFF FFS

Running now · updated 05:40

Position estimated from the timetable

Between Rotkreuz and Hünenberg Zythus 0 min

Estimated arrival at Baar 05:57 · 84 km/h

  1. Sursee04:47
  2. Rothenburg Station05:00
  3. Emmenbrücke05:07
  4. Root D405:32
  5. Rotkreuz05:38
  6. Hünenberg Zythus05:42
  7. Baar05:57

Today it is running no worse than usual: typical arrival delay is 0 min; 97% of the last 30 runs arrived on time.

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 46 full · 1 partial · 3 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 Baar, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 5 Sept Max en route +5 min · last fix heading to Baar Lindenpark +4 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 45
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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 10Today
04:47on time on timePassed
04:49≈ on time ≈ on timePassed
04:51≈ on time ≈ on timePassed
04:56≈ on time ≈ on timePassed
05:00≈ on time ≈ on timePassed
05:02≈ on time ≈ on timePassed
05:05≈ on time ≈ on timePassed
05:07≈ on time ≈ +1 minPassed
05:14 / 05:21≈ on time ≈ +1 minPassed
05:29≈ on time ≈ +1 minPassed
05:30≈ on time ≈ +1 minPassed
05:32≈ on time ≈ +1 minPassed
05:35≈ on time ≈ +1 minPassed
05:38 / 05:39≈ on time ≈ +1 minPassed
05:42≈ on time ≈ +1 minNext
05:44≈ on time ≈ +1 min
05:45≈ on time ≈ +1 min
05:47≈ on time ≈ +2 min
05:49≈ on time ≈ +2 min
05:51≈ on time ≈ +2 min
05:53≈ on time ≈ +2 min
05:54≈ on time ≈ +2 min
05:57on 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
Thu 12 NovHünenberg Zythus 05:39Partial coverage0 min—
Wed 11 NovBaar 05:59+1 min—
Tue 10 NovBaar 05:59+1 min—
Mon 9 NovBaar 05:59+2 min+2 min
Sun 8 NovBaar 05:580 min—
Sat 7 NovBaar 05:580 min—
Fri 6 NovBaar 05:580 min—
Thu 5 NovBaar 05:580 min—
Wed 4 NovBaar 05:580 min—
Tue 3 NovBaar 05:59+2 min+2 min
Mon 2 NovBaar 05:580 min—
Sun 1 NovBaar 05:57−1 min—
Sat 31 OctBaar 05:580 min—
Fri 30 OctBaar 05:580 min—
Thu 29 OctBaar 05:59+1 min+1 min
Wed 28 OctBaar 05:59+2 min+2 min
Tue 27 OctBaar 05:59+1 min+1 min
Mon 26 OctBaar 05:580 min—
Sun 25 OctBaar 06:00+2 min+2 min
Sat 24 OctBaar 05:59+1 min—
Fri 23 OctBaar 05:580 min—
Thu 22 OctBaar 05:59+1 min+1 min
Wed 21 OctBaar 05:59+1 min+1 min
Tue 20 OctBaar 05:580 min—
Mon 19 OctBaar 05:580 min—
Sun 18 OctBaar 05:58−1 min—
Sat 17 OctBaar 05:580 min—
Fri 16 OctBaar 05:580 min—
Thu 15 OctBaar 06:01+3 min+3 min
Wed 14 OctBaar 05:59+1 min—