S1 21136 Sursee → Baar

View line S1

Sursee 11:18 → Baar 12:27 Daily 1 h 09 min · 24 stops SBB CFF FFS

S1 21136 Sursee–Baar: final delay under 3 min on 22 of its 23 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:12 (GMT+1).

✓ Today’s run finished

Today it reached Baar at 12:29 +2 min

  1. Sursee11:18
  2. Rothenburg Station11:31
  3. Luzern11:45
  4. Gisikon-Root12:05
  5. Hünenberg Zythus12:12
  6. Zug Schutzengel12:19
  7. Baar12:27

Next service: tomorrow 11:18 from Sursee · Mon 23 Nov

Next departure 11:18 tomorrow · Sursee
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 full · 0 partial · 11 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 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

  • Sun 25 Oct Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 96% · 43
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=8
  • 100% W n=10
  • 100% T n=3
  • 100% F n=7
  • 100% S n=7
  • 88% S n=8

Stops and timetable

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

Last 90 days, 45 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
11:18on time on time
11:20≈ on time ≈ on time
11:22≈ on time ≈ +1 min
11:26 / 11:27≈ on time ≈ +1 min
11:31≈ on time ≈ +1 min
11:33≈ on time ≈ +1 min
11:36≈ on time ≈ +1 min
11:38≈ on time ≈ +1 min
11:45 / 11:51≈ on time ≈ +1 min
11:58≈ on time ≈ +1 min
12:00≈ on time ≈ +1 min
12:02≈ on time ≈ +1 min
12:05≈ on time ≈ +1 min
12:08 / 12:09≈ on time ≈ +2 min
12:11≈ on time ≈ +2 min
12:12≈ on time ≈ +2 min
12:14≈ on time ≈ +2 min
12:15≈ on time ≈ +2 min
12:17≈ on time ≈ +2 min
12:19≈ on time ≈ +2 min
12:21≈ on time ≈ +2 min
12:23≈ on time ≈ +2 min
12:24≈ on time ≈ +2 min
12:27on 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
Sun 22 NovBaar 12:29+2 min+2 min
Sat 21 NovBaar 12:27−1 min—
Fri 20 NovBaar 12:27−1 min—
Thu 19 NovBaar 12:28No data—
Wed 18 NovBaar 12:29+3 min+3 min
Tue 17 NovBaar 12:290 min—
Mon 16 NovBaar 12:28No data—
Sun 15 NovBaar 12:280 min—
Sat 14 NovBaar 12:27−1 min—
Fri 13 NovBaar 12:280 min—
Thu 12 NovBaar 12:28No data—
Wed 11 NovBaar 12:280 min—
Tue 10 NovBaar 12:29+1 min—
Mon 9 NovBaar 12:28No data—
Sun 8 NovLuzern 11:44−1 min—
Sat 7 NovLuzern 11:44−1 min—
Fri 6 NovBaar 12:29+2 min+2 min
Thu 5 NovBaar 12:28No data—
Wed 4 NovBaar 12:29+1 min+1 min
Tue 3 NovBaar 12:28−1 min—
Mon 2 NovBaar 12:28No data—
Sun 1 NovBaar 12:29+1 min+1 min
Sat 31 OctBaar 12:280 min—
Fri 30 OctBaar 12:280 min—
Thu 29 OctBaar 12:290 min—
Wed 28 OctBaar 12:290 min—
Tue 27 OctBaar 12:31+2 min+2 min
Mon 26 OctBaar 12:28No data—
Sun 25 OctBaar 12:31+3 min+3 min
Sat 24 OctBaar 12:280 min—