S1 21145 Baar – Sursee

View line S1

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

✓ Today’s run finished

Today, last fix heading to Sursee at 14:39 No data

  1. Baar13:31
  2. Zug Schutzengel13:37
  3. Cham13:43
  4. Root D413:54
  5. Emmenbrücke14:19
  6. Rothenburg Station14:27
  7. Sursee14:40

Next service: tomorrow 13:31 from Baar · Tue 17 Nov

Next departure 13:31 tomorrow · Baar
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
59/61 runs under 3 min
RT coverage: 61 full · 0 partial · 13 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

  • Fri 6 Nov Max en route +8 min · last fix heading to Sursee +8 min
  • Wed 21 Oct Max en route +4 min · last fix heading to Sursee +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 59
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=11
  • 90% W n=10
  • 100% T n=5
  • 91% F n=11
  • 100% S n=10
  • 100% S n=10

Stops and timetable

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

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