S1 22112 Rotkreuz – Baar

View line S1

Rotkreuz 06:23 → Baar 06:42 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 11 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Baar at 06:43 +1 min

  1. Rotkreuz06:23
  2. Hünenberg Zythus06:27
  3. Cham06:29
  4. Zug Chollermüli06:32
  5. Zug06:37
  6. Baar Lindenpark06:38
  7. Baar06:42

Next service: tomorrow 06:23 from Rotkreuz · Fri 20 Nov

Next departure 06:23 tomorrow · Rotkreuz
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
89%
31/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 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: +1 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

  • Wed 18 Nov Max en route +4 min · last fix heading to Baar +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Baar +3 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Baar +3 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 31
  • 3–10 min 11% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 100% T n=8
  • 86% W n=7
  • 100% T n=7
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
06:23on time on time
06:26≈ on time ≈ +1 min
06:27≈ on time ≈ +1 min
06:29≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06:32≈ on time ≈ +2 min
06:34≈ on time ≈ +2 min
06:37≈ +1 min ≈ +2 min
06:38≈ +1 min ≈ +2 min
06:40≈ +1 min ≈ +3 min
06:42+1 min +3 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 19 NovBaar 06:44+1 min+1 min
Wed 18 NovBaar 06:47+4 min+4 min
Tue 17 NovBaar 06:44+1 min+1 min
Mon 16 NovBaar 06:430 min—
Fri 13 NovBaar 06:47+3 min+3 min
Thu 12 NovBaar 06:440 min—
Wed 11 NovBaar 06:44+1 min—
Tue 10 NovBaar 06:44+1 min—
Mon 9 NovBaar 06:430 min—
Fri 6 NovBaar 06:44+1 min—
Thu 5 NovBaar 06:44+1 min—
Wed 4 NovBaar 06:44+1 min—
Tue 3 NovBaar 06:440 min—
Mon 2 NovBaar 06:44+1 min—
Fri 30 OctBaar 06:430 min—
Thu 29 OctBaar 06:430 min—
Wed 28 OctBaar 06:44+1 min—
Tue 27 OctBaar 06:440 min—
Mon 26 OctBaar 06:45+2 min+2 min
Fri 23 OctBaar 06:430 min—
Thu 22 OctBaar 06:430 min—
Wed 21 OctBaar 06:430 min—
Tue 20 OctBaar 06:440 min—
Mon 19 OctBaar 06:44+1 min+1 min
Fri 16 OctBaar 06:430 min—
Thu 15 OctBaar 06:45+2 min+2 min
Wed 14 OctBaar 06:45+2 min+2 min
Tue 13 OctBaar 06:43+1 min—
Mon 12 OctBaar 06:46+3 min+3 min
Fri 9 OctBaar 06:45+2 min+2 min