S1 21132 Sursee – Baar

View line S1

Sursee 10:18 → Baar 11:27 Daily 1 h 09 min · 23 stops SBB CFF FFS

Running now · updated 10:44

Position estimated from the timetable

Between Emmenbrücke and Luzern 0 min

Estimated arrival at Baar 11:27 · 39 km/h

  1. Sursee10:18
  2. Rothenburg Station10:31
  3. Emmenbrücke10:38
  4. Luzern10:45
  5. Root D411:02
  6. Cham11:14
  7. Baar11:27

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

On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 28 full · 1 partial · 1 no data
On-time · 90 days
95%
58/61 runs under 3 min
RT coverage: 60 full · 1 partial · 1 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: +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

  • Fri 6 Nov Max en route +3 min · last fix heading to Baar +3 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Baar +3 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 100% W n=9
  • 100% T n=7
  • 89% F n=9
  • 100% S n=7
  • 78% S n=9

Stops and timetable

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

Last 90 days, 61 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
10:18on time on timePassed
10:20≈ on time ≈ on timePassed
10:22≈ on time ≈ +1 minPassed
10:26 / 10:27≈ on time ≈ +1 minPassed
10:31≈ on time ≈ +1 minPassed
10:33≈ on time ≈ +1 minPassed
10:36≈ on time ≈ +1 minPassed
10:38≈ on time ≈ +1 minPassed
10:45 / 10:51≈ on time ≈ +1 minNext
10:58≈ on time ≈ +1 min
11:00≈ on time ≈ +1 min
11:02≈ on time ≈ +2 min
11:05≈ on time ≈ +2 min
11:08 / 11:09≈ on time ≈ +2 min
11:12≈ on time ≈ +2 min
11:14≈ on time ≈ +2 min
11:15≈ on time ≈ +2 min
11:17≈ on time ≈ +2 min
11:19≈ on time ≈ +2 min
11:21≈ on time ≈ +2 min
11:23≈ on time ≈ +2 min
11:24≈ on time ≈ +2 min
11:27on 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
Wed 18 NovLuzern 10:44Partial coverage0 min—
Tue 17 NovBaar 11:30+1 min+1 min
Mon 16 NovBaar 11:280 min—
Sun 15 NovBaar 11:29+3 min+3 min
Sat 14 NovBaar 11:280 min—
Fri 13 NovBaar 11:29+1 min—
Thu 12 NovBaar 11:280 min—
Wed 11 NovBaar 11:280 min—
Tue 10 NovBaar 11:280 min—
Mon 9 NovBaar 11:280 min—
Sun 8 NovLuzern 10:44−1 min—
Sat 7 NovLuzern 10:44−1 min—
Fri 6 NovBaar 11:32+3 min+3 min
Thu 5 NovBaar 11:280 min—
Wed 4 NovBaar 11:27−1 min—
Tue 3 NovBaar 11:290 min—
Mon 2 NovBaar 11:280 min—
Sun 1 NovBaar 11:30+2 min+2 min
Sat 31 OctBaar 11:29+1 min+1 min
Fri 30 OctBaar 11:29+1 min+1 min
Thu 29 OctBaar 11:28No data—
Wed 28 OctBaar 11:29+1 min+1 min
Tue 27 OctBaar 11:29+1 min+1 min
Mon 26 OctBaar 11:290 min—
Sun 25 OctBaar 11:31+3 min+3 min
Sat 24 OctBaar 11:30+2 min+2 min
Fri 23 OctBaar 11:27−1 min—
Thu 22 OctBaar 11:280 min—
Wed 21 OctBaar 11:31+3 min+3 min
Tue 20 OctBaar 11:29+1 min—