S1 21135 Baar – Sursee

View line S1

Baar 10:47 → Sursee 12:10 Daily 1 h 23 min · 24 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Sursee at 12:10 0 min

  1. Baar10:47
  2. Zug Schutzengel10:53
  3. Hünenberg Zythus11:00
  4. Root D411:21
  5. Luzern11:38
  6. Rothenburg Station11:57
  7. Sursee12:10

Next service: tomorrow 10:47 from Baar · Sat 14 Nov

Next departure 10:47 tomorrow · Baar
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
95%
52/55 runs under 3 min
RT coverage: 55 full · 0 partial · 7 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: +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

  • Mon 5 Oct Max en route +9 min · last fix heading to Sursee +9 min
  • Sun 25 Oct Max en route +4 min · last fix heading to Sursee +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Sursee +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 86% M n=7
  • 100% T n=10
  • 100% W n=8
  • 100% T n=6
  • 88% F n=8
  • 100% S n=7
  • 89% S n=9

Stops and timetable

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

Last 90 days, 55 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
10:47on time on time
10:48≈ on time ≈ on time
10:49≈ on time ≈ on time
10:52≈ on time ≈ on time
10:53≈ on time ≈ on time
10:55≈ on time ≈ on time
10:57≈ on time ≈ +1 min
10:59≈ on time ≈ +1 min
11:00≈ on time ≈ +1 min
11:01≈ on time ≈ +1 min
11:07 / 11:16≈ on time ≈ +1 min
11:19≈ on time ≈ +1 min
11:21≈ on time ≈ +1 min
11:24≈ on time ≈ +1 min
11:26 / 11:27≈ on time ≈ +1 min
11:38 / 11:44≈ on time ≈ +1 min
11:49≈ on time ≈ +1 min
11:51 / 11:52≈ on time ≈ +1 min
11:54≈ on time ≈ +1 min
11:57≈ on time ≈ +1 min
12:01≈ on time ≈ +1 min
12:04≈ on time ≈ +1 min
12:07≈ on time ≈ +2 min
12:10on 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
Fri 13 NovSursee 12:120 min—
Thu 12 NovSursee 12:090 min—
Wed 11 NovSursee 12:090 min—
Tue 10 NovSursee 12:090 min—
Mon 9 NovSursee 12:090 min—
Sun 8 NovSursee 12:12+1 min—
Sat 7 NovSursee 12:090 min—
Fri 6 NovSursee 12:12+1 min+1 min
Thu 5 NovSursee 12:090 min—
Wed 4 NovSursee 12:090 min—
Tue 3 NovSursee 12:120 min—
Mon 2 NovSursee 12:090 min—
Sun 1 NovSursee 12:12+1 min+1 min
Sat 31 OctSursee 12:110 min—
Fri 30 OctSursee 12:110 min—
Thu 29 OctSursee 12:11No data—
Wed 28 OctSursee 12:13+2 min+2 min
Tue 27 OctSursee 12:110 min—
Mon 26 OctSursee 12:120 min—
Sun 25 OctSursee 12:15+4 min+4 min
Sat 24 OctSursee 12:12+1 min+1 min
Fri 23 OctSursee 12:14+3 min+3 min
Thu 22 OctSursee 12:110 min—
Wed 21 OctSursee 12:110 min—
Tue 20 OctSursee 12:120 min—
Mon 19 OctSursee 12:110 min—
Sun 18 OctSursee 12:12+1 min—
Sat 17 OctSursee 12:13+2 min+2 min
Fri 16 OctSursee 12:110 min—
Thu 15 OctSursee 12:110 min—