S1 21171 Baar – Sursee

View line S1

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

✓ Today’s run finished

Today it reached Sursee at 21:11 +1 min

  1. Baar19:47
  2. Zug Schutzengel19:53
  3. Hünenberg Zythus20:00
  4. Root D420:21
  5. Luzern20:38
  6. Rothenburg Station20:57
  7. Sursee21:10

Next service: tomorrow 19:47 from Baar · Tue 10 Nov

Next departure 19:47 tomorrow · Baar
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
93%
53/57 runs under 3 min
RT coverage: 57 full · 0 partial · 3 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 3 Oct Max en route +6 min · last fix heading to Nottwil +6 min
  • Wed 12 Aug Max en route +4 min · last fix heading to Oberkirch LU +4 min
  • Sun 4 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

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

  • Early 0% · 0
  • On time 93% · 53
  • 3–10 min 7% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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