S1 21141 Baar – Sursee

View line S1

Baar 12:31 → Sursee 13:40 Daily 1 h 09 min · 23 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Sursee at 13:41 +1 min

  1. Baar12:31
  2. Zug Schutzengel12:37
  3. Cham12:43
  4. Root D412:54
  5. Emmenbrücke13:19
  6. Rothenburg Station13:27
  7. Sursee13:40

Next service: tomorrow 12:31 from Baar · Wed 11 Nov

Next departure 12:31 tomorrow · Baar
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
57/59 runs under 3 min
RT coverage: 59 full · 0 partial · 10 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: +2 min

Last 30 days

Arrival delay at Sursee, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 22 Aug Max en route +7 min · last fix heading to Nottwil +7 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Sursee +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 95% · 56
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=9
  • 100% T n=5
  • 100% F n=12
  • 91% S n=11
  • 88% S n=8

Stops and timetable

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

Last 90 days, 59 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
12:31+1 min +1 min
12:32≈ +1 min ≈ +1 min
12:34≈ +1 min ≈ +1 min
12:36≈ +1 min ≈ +1 min
12:37≈ +1 min ≈ +1 min
12:39≈ +1 min ≈ +1 min
12:41≈ +1 min ≈ +1 min
12:43≈ +1 min ≈ +1 min
12:44≈ +1 min ≈ +1 min
12:49≈ +1 min ≈ +1 min
12:52≈ +1 min ≈ +1 min
12:54≈ +1 min ≈ +1 min
12:56≈ +1 min ≈ +1 min
12:59≈ +1 min ≈ +1 min
13:07 / 13:14≈ +1 min ≈ +2 min
13:19≈ +1 min ≈ +2 min
13:21 / 13:22≈ +1 min ≈ +2 min
13:24≈ +1 min ≈ +2 min
13:27≈ +1 min ≈ +2 min
13:31≈ +1 min ≈ +2 min
13:34≈ +1 min ≈ +2 min
13:37≈ +1 min ≈ +2 min
13:40+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
Tue 10 NovSursee 13:42+1 min+1 min
Mon 9 NovSursee 13:39No data—
Sun 8 NovSursee 13:42+1 min—
Sat 7 NovSursee 13:42+1 min+1 min
Fri 6 NovSursee 13:44+3 min+3 min
Thu 5 NovSursee 13:39No data—
Wed 4 NovSursee 13:42+1 min—
Tue 3 NovSursee 13:39+1 min—
Mon 2 NovSursee 13:39No data—
Sun 1 NovSursee 13:43+2 min+2 min
Sat 31 OctSursee 13:43+2 min+2 min
Fri 30 OctSursee 13:42+1 min+1 min
Thu 29 OctSursee 13:41No data—
Wed 28 OctSursee 13:43+2 min+2 min
Tue 27 OctSursee 13:420 min—
Mon 26 OctSursee 13:41No data—
Sun 25 OctSursee 13:44+3 min+3 min
Sat 24 OctSursee 13:42+1 min+1 min
Fri 23 OctSursee 13:43+2 min+2 min
Thu 22 OctSursee 13:41No data—
Wed 21 OctSursee 13:43+2 min+2 min
Tue 20 OctSursee 13:43+1 min+1 min
Mon 19 OctSursee 13:41No data—
Sun 18 OctSursee 13:44+2 min+2 min
Sat 17 OctSursee 13:42+1 min+1 min
Fri 16 OctSursee 13:43+1 min+1 min
Thu 15 OctSursee 13:41No data—
Wed 14 OctSursee 13:42+1 min+1 min
Tue 13 OctSursee 13:42+1 min—
Mon 12 OctSursee 13:41No data—