S1 21185 Baar – Luzern

View line S1

Baar 23:31 → Luzern 00:07 Daily 0 h 36 min · 15 stops SBB CFF FFS

Running now · updated 23:41

Position estimated from the timetable

Between Cham Alpenblick and Cham 0 min

Estimated arrival at Luzern 00:07 · 34 km/h

  1. Baar23:31
  2. Baar Lindenpark23:34
  3. Zug Chollermüli23:39
  4. Cham Alpenblick23:41
  5. Cham23:43
  6. Rotkreuz23:49
  7. Luzern00:07

Today it is running no worse than usual: typical arrival delay is +1 min; 87% of the last 30 runs arrived on time.

On-time · 30 days
87%
26/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
85%
55/65 runs under 3 min
RT coverage: 64 full · 1 partial · 7 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Luzern, 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 30 Oct Max en route +8 min · last fix heading to Luzern +8 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Sun 4 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Sat 14 Nov Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 83% · 54
  • 3–10 min 15% · 10
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 83% T n=12
  • 92% W n=13
  • 75% T n=8
  • 80% F n=10
  • 83% S n=6
  • 78% S n=9

Stops and timetable

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

Last 90 days, 65 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 10Today
23:31on time +1 minPassed
23:32≈ on time ≈ +1 minPassed
23:34≈ on time ≈ +1 minPassed
23:36≈ on time ≈ +1 minPassed
23:37≈ on time ≈ +1 minPassed
23:39≈ on time ≈ +1 minPassed
23:41≈ on time ≈ +1 minPassed
23:43≈ on time ≈ +1 minNext
23:44≈ on time ≈ +2 min
23:49≈ on time ≈ +2 min
23:52≈ on time ≈ +2 min
23:54≈ +1 min ≈ +3 min
23:56≈ +1 min ≈ +3 min
23:59≈ +1 min ≈ +3 min
00:07+1 min +4 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
Wed 18 NovCham Alpenblick 23:39Partial coverage0 min—
Tue 17 NovLuzern 00:080 min—
Mon 16 NovLuzern 00:09+1 min+3 min
Sun 15 NovLuzern 00:09+3 min+3 min
Sat 14 NovLuzern 00:13+4 min+4 min
Fri 13 NovLuzern 00:09+1 min—
Thu 12 NovLuzern 00:09+1 min—
Wed 11 NovLuzern 00:09+2 min+2 min
Tue 10 NovLuzern 00:08+3 min+3 min
Mon 9 NovEbikon 00:04+1 min—
Sun 8 NovEbikon 00:03−1 min—
Sat 7 NovEbikon 00:030 min—
Fri 6 NovLuzern 00:09+1 min+1 min
Thu 5 NovLuzern 00:080 min—
Wed 4 NovLuzern 00:09+3 min+3 min
Tue 3 NovEbikon 00:04+1 min—
Mon 2 NovEbikon 00:03−1 min—
Sun 1 NovLuzern 00:090 min—
Sat 31 OctLuzern 00:09+1 min+1 min
Fri 30 OctLuzern 00:16+8 min+8 min
Thu 29 OctEbikon 00:030 min—
Wed 28 OctEbikon 00:030 min—
Tue 27 OctEbikon 00:02−1 min—
Mon 26 OctEbikon 00:02−1 min—
Sun 25 OctEbikon 00:040 min—
Sat 24 OctLuzern 00:080 min—
Fri 23 OctLuzern 00:08+3 min+3 min
Thu 22 OctLuzern 00:13+5 min+5 min
Wed 21 OctLuzern 00:10+2 min+2 min
Tue 20 OctLuzern 00:10+2 min+2 min