S1 21126 Sursee – Baar

View line S1

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

✓ Today’s run finished

Today it reached Baar at 10:12 +1 min

  1. Sursee08:48
  2. Rothenburg Station09:01
  3. Luzern09:15
  4. Gisikon-Root09:37
  5. Hünenberg Zythus09:56
  6. Zug Schutzengel10:02
  7. Baar10:11

Next service: tomorrow 08:48 from Sursee · Thu 19 Nov

Next departure 08:48 tomorrow · Sursee
On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
91%
62/68 runs under 3 min
RT coverage: 68 full · 0 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
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 22 Oct Max en route +5 min · last fix heading to Baar +5 min
  • Fri 11 Sept Max en route +4 min · last fix heading to Baar Lindenpark +4 min
  • Fri 6 Nov Max en route +3 min · last fix heading to Baar +3 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Baar +3 min
  • Tue 20 Oct Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 62
  • 3–10 min 9% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 90% T n=10
  • 100% W n=9
  • 78% T n=9
  • 75% F n=8
  • 100% S n=11
  • 100% S n=9

Stops and timetable

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

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