S1 22133 Baar – Luzern

View line S1

Baar 23:31 → Luzern 00:07 Mon, Tue, Wed, Thu, Fri, Sat 0 h 36 min · 15 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 23:31 from Baar · Fri 13 Nov

Next departure 23:31 today · Baar
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 1 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 36 full · 3 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 13% · 5
  • On time 87% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 100% W n=7
  • 100% T n=6
  • 100% F n=7
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
23:31on time on time
23:32≈ on time ≈ on time
23:34≈ on time ≈ on time
23:36≈ on time ≈ on time
23:37≈ on time ≈ on time
23:39≈ on time ≈ on time
23:41≈ on time ≈ on time
23:43≈ on time ≈ on time
23:44≈ on time ≈ on time
23:49≈ on time ≈ +1 min
23:52≈ on time ≈ +1 min
23:54≈ on time ≈ +1 min
23:56≈ on time ≈ +1 min
23:59≈ on time ≈ +1 min
00:07on time +1 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
Thu 12 NovRotkreuz 10:34Partial coverage0 min—
Wed 11 NovRotkreuz 10:33Partial coverage−1 min—
Tue 10 NovRotkreuz 10:34Partial coverage0 min—
Mon 9 NovRotkreuz 10:340 min—
Sat 7 NovRotkreuz 10:340 min—
Fri 6 NovRotkreuz 10:340 min—
Thu 5 NovRotkreuz 10:34−1 min—
Wed 4 NovRotkreuz 10:340 min—
Tue 3 NovRotkreuz 10:340 min—
Mon 2 NovRotkreuz 10:340 min—
Sat 31 OctRotkreuz 10:34−1 min—
Fri 30 OctRotkreuz 10:34−1 min—
Thu 29 OctRotkreuz 10:35No data—
Wed 28 OctRotkreuz 10:37+2 min+2 min
Tue 27 OctRotkreuz 10:34−1 min—
Mon 26 OctBaar 11:010 min—
Sat 24 OctRotkreuz 10:38+3 min+3 min
Fri 23 OctRotkreuz 10:34−1 min—
Thu 22 OctRotkreuz 10:350 min+1 min
Wed 21 OctRotkreuz 10:350 min—
Tue 20 OctRotkreuz 10:36+1 min—
Mon 19 OctRotkreuz 10:34−1 min—
Sat 17 OctRotkreuz 10:35−1 min—
Fri 16 OctRotkreuz 10:350 min—
Thu 15 OctRotkreuz 10:34−1 min—
Wed 14 OctRotkreuz 10:34−1 min—
Tue 13 OctRotkreuz 10:35−1 min—
Mon 12 OctRotkreuz 10:36+1 min—
Sat 10 OctRotkreuz 10:360 min—
Fri 9 OctRotkreuz 10:34−1 min—