S1 21184 Sursee – Baar

View line S1

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

It has not run yet today

Last recorded run: Wednesday 11 November +1 min

Next service: today 22:48 from Sursee · Thu 12 Nov

Next departure 22:48 today · Sursee
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
94%
67/71 runs under 3 min
RT coverage: 71 full · 0 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 25 Sept Max en route +5 min · last fix heading to Baar Lindenpark +5 min
  • Wed 21 Oct Max en route +5 min · last fix heading to Baar +5 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Baar +5 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 78% W n=9
  • 100% T n=9
  • 91% F n=11
  • 91% S n=11
  • 100% S n=10

Stops and timetable

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

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