S1 21138 Sursee – Baar

View line S1

Sursee 11:48 → Baar 13:11 Daily 1 h 23 min · 24 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Baar at 13:12 No data

  1. Sursee11:48
  2. Rothenburg Station12:01
  3. Luzern12:15
  4. Gisikon-Root12:37
  5. Hünenberg Zythus12:56
  6. Zug Schutzengel13:02
  7. Baar13:11

Next service: tomorrow 11:48 from Sursee · Fri 13 Nov

Next departure 11:48 tomorrow · Sursee
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
94%
51/54 runs under 3 min
RT coverage: 54 full · 0 partial · 12 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

  • Mon 31 Aug Max en route +4 min · last fix heading to Zug +4 min
  • Sat 29 Aug Max en route +3 min · last fix heading to Zug Schutzengel +3 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 89% · 48
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=8
  • 100% W n=10
  • 100% T n=4
  • 100% F n=9
  • 90% S n=10
  • 86% S n=7

Stops and timetable

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

Last 90 days, 54 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
11:48on time +1 min
11:50≈ on time ≈ +1 min
11:52≈ on time ≈ +1 min
11:57≈ on time ≈ +1 min
12:01≈ on time ≈ +1 min
12:03≈ on time ≈ +1 min
12:06≈ on time ≈ +1 min
12:08≈ on time ≈ +1 min
12:15 / 12:21≈ on time ≈ +1 min
12:31≈ on time ≈ +1 min
12:33≈ on time ≈ +1 min
12:35≈ on time ≈ +1 min
12:37≈ on time ≈ +2 min
12:42 / 12:51≈ on time ≈ +2 min
12:54≈ on time ≈ +2 min
12:56≈ on time ≈ +2 min
12:57≈ on time ≈ +2 min
12:58≈ on time ≈ +2 min
13:00≈ on time ≈ +2 min
13:02≈ on time ≈ +2 min
13:05≈ on time ≈ +2 min
13:07≈ on time ≈ +2 min
13:08≈ +1 min ≈ +2 min
13:11+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
Thu 12 NovBaar 13:12No data—
Wed 11 NovBaar 13:13+1 min+1 min
Tue 10 NovBaar 13:130 min—
Mon 9 NovBaar 13:12No data—
Sun 8 NovLuzern 12:17+1 min—
Sat 7 NovLuzern 12:140 min—
Fri 6 NovBaar 13:14+2 min+2 min
Thu 5 NovBaar 13:12No data—
Wed 4 NovBaar 13:120 min—
Tue 3 NovBaar 13:090 min—
Mon 2 NovBaar 13:12No data—
Sun 1 NovBaar 13:01+3 min+3 min
Sat 31 OctBaar 13:120 min—
Fri 30 OctBaar 13:11−1 min—
Thu 29 OctBaar 13:12No data—
Wed 28 OctBaar 13:14+2 min+2 min
Tue 27 OctBaar 13:13+1 min—
Mon 26 OctBaar 13:12No data—
Sun 25 OctBaar 13:01+3 min+3 min
Sat 24 OctBaar 13:14+2 min+2 min
Fri 23 OctBaar 13:13+1 min+1 min
Thu 22 OctBaar 13:12No data—
Wed 21 OctBaar 13:15+3 min+3 min
Tue 20 OctBaar 13:130 min—
Mon 19 OctBaar 13:12No data—
Sun 18 OctBaar 13:00+1 min+1 min
Sat 17 OctBaar 13:13+1 min—
Fri 16 OctBaar 13:13+1 min+1 min
Thu 15 OctBaar 13:12No data—
Wed 14 OctBaar 13:120 min—