S1 21150 Sursee – Baar

View line S1

Sursee 14:48 → Baar 15:57 Daily 1 h 09 min · 24 stops SBB CFF FFS

Running now · updated 15:29

Position estimated from the timetable

Between Luzern and Ebikon +1 min

Estimated arrival at Baar 15:58 · 66 km/h

  1. Sursee14:48
  2. Rothenburg Station15:01
  3. Luzern15:15
  4. Ebikon15:29
  5. Gisikon-Root15:35
  6. Hünenberg Zythus15:42
  7. Baar15:57

Today it is running no worse than usual: typical arrival delay is +1 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
95%
62/65 runs under 3 min
RT coverage: 64 full · 1 partial · 3 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Thu 24 Sept Max en route +9 min · last fix heading to Baar +8 min
  • Thu 29 Oct Max en route +7 min · last fix heading to Baar +7 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Baar +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 62
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 88% T n=8
  • 100% W n=9
  • 80% T n=10
  • 100% F n=7
  • 100% S n=9
  • 100% S n=13

Stops and timetable

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

Last 90 days, 65 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
14:48on time +1 minPassed
14:50≈ on time ≈ +1 minPassed
14:52≈ on time ≈ +1 minPassed
14:57≈ on time ≈ +1 minPassed
15:01≈ on time ≈ +1 minPassed
15:03≈ on time ≈ +1 minPassed
15:06≈ on time ≈ +1 minPassed
15:08≈ on time ≈ +1 minPassed
15:15 / 15:21≈ on time ≈ +1 minPassed
15:29≈ +1 min ≈ +1 minNext
15:30≈ +1 min ≈ +2 min
15:32≈ +1 min ≈ +2 min
15:35≈ +1 min ≈ +2 min
15:38 / 15:39≈ +1 min ≈ +2 min
15:41≈ +1 min ≈ +2 min
15:42≈ +1 min ≈ +2 min
15:44≈ +1 min ≈ +2 min
15:45≈ +1 min ≈ +2 min
15:47≈ +1 min ≈ +2 min
15:49≈ +1 min ≈ +2 min
15:51≈ +1 min ≈ +2 min
15:53≈ +1 min ≈ +2 min
15:54≈ +1 min ≈ +2 min
15:57+1 min +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 15 NovEbikon 15:24Partial coverage+1 min—
Sat 14 NovBaar 16:13+1 min—
Fri 13 NovBaar 16:13+1 min—
Thu 12 NovBaar 16:120 min—
Wed 11 NovBaar 16:13+1 min—
Tue 10 NovBaar 16:120 min—
Mon 9 NovBaar 16:14+2 min+2 min
Sun 8 NovLuzern 15:18+2 min+2 min
Sat 7 NovLuzern 15:14−1 min—
Fri 6 NovBaar 16:14+2 min+2 min
Thu 5 NovBaar 16:120 min—
Wed 4 NovBaar 16:120 min—
Tue 3 NovBaar 16:130 min—
Mon 2 NovBaar 16:130 min—
Sun 1 NovBaar 16:00+3 min+3 min
Sat 31 OctBaar 16:13+2 min+2 min
Fri 30 OctBaar 16:120 min—
Thu 29 OctBaar 16:19+7 min+7 min
Wed 28 OctBaar 16:14+2 min+2 min
Tue 27 OctBaar 16:120 min—
Mon 26 OctBaar 16:13+1 min—
Sun 25 OctBaar 16:00+3 min+3 min
Sat 24 OctBaar 16:120 min—
Fri 23 OctBaar 16:12+1 min—
Thu 22 OctBaar 16:12−1 min—
Wed 21 OctBaar 16:14+2 min+2 min
Tue 20 OctBaar 16:15+3 min+3 min
Mon 19 OctBaar 16:120 min—
Sun 18 OctBaar 15:580 min—
Sat 17 OctBaar 16:14+2 min+2 min