S1 22137 Baar – Rotkreuz

View line S1

Baar 11:15 → Rotkreuz 11:34 Mon, Tue, Wed, Thu, Fri, Sat 0 h 19 min · 11 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Rotkreuz at 11:34 No data

  1. Baar11:15
  2. Baar Lindenpark11:17
  3. Zug11:20
  4. Zug Chollermüli11:23
  5. Cham11:27
  6. Hünenberg Zythus11:28
  7. Rotkreuz11:34

Next service: tomorrow 11:15 from Baar · Fri 6 Nov

Next departure 11:15 tomorrow · Baar
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 7 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 8 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 Rotkreuz, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=6
  • 100% W n=7
  • 100% T n=2
  • 100% F n=4
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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:15on time on time
11:16≈ on time ≈ on time
11:17≈ on time ≈ on time
11:20≈ on time ≈ on time
11:21≈ on time ≈ on time
11:23≈ on time ≈ +1 min
11:25≈ on time ≈ +1 min
11:27≈ on time ≈ +1 min
11:28≈ on time ≈ +1 min
11:29≈ on time ≈ +1 min
11:34on 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 5 NovRotkreuz 11:34No data—
Wed 4 NovRotkreuz 11:34−1 min—
Tue 3 NovRotkreuz 11:34−1 min—
Mon 2 NovRotkreuz 11:340 min—
Sat 31 OctRotkreuz 11:34−1 min—
Fri 30 OctRotkreuz 11:350 min—
Thu 29 OctRotkreuz 11:35No data—
Wed 28 OctRotkreuz 11:37+2 min+2 min
Tue 27 OctRotkreuz 11:350 min—
Mon 26 OctRotkreuz 11:36No data—
Sat 24 OctRotkreuz 11:36+1 min+1 min
Fri 23 OctRotkreuz 11:34−1 min—
Thu 22 OctRotkreuz 11:35No data—
Wed 21 OctRotkreuz 11:36+1 min+1 min
Tue 20 OctRotkreuz 11:34−1 min—
Mon 19 OctRotkreuz 11:35No data—
Sat 17 OctRotkreuz 11:36+1 min—
Fri 16 OctRotkreuz 11:340 min—
Thu 15 OctRotkreuz 11:35No data—
Wed 14 OctRotkreuz 11:37+2 min+2 min
Tue 13 OctRotkreuz 11:360 min—
Mon 12 OctRotkreuz 11:35No data—
Sat 10 OctRotkreuz 11:35−1 min—
Fri 9 OctRotkreuz 11:350 min—
Thu 8 OctRotkreuz 11:350 min—
Wed 7 OctRotkreuz 11:34−1 min—
Tue 6 OctRotkreuz 11:35−1 min—
Mon 5 OctRotkreuz 11:360 min—
Sat 3 OctRotkreuz 11:34−1 min—
Thu 1 OctRotkreuz 08:340 min—