S1 22149 Baar – Rotkreuz

View line S1

Baar 14:15 → Rotkreuz 14: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 14:34 No data

  1. Baar14:15
  2. Baar Lindenpark14:17
  3. Zug14:20
  4. Zug Chollermüli14:23
  5. Cham14:27
  6. Hünenberg Zythus14:28
  7. Rotkreuz14:34

Next service: tomorrow 14:15 from Baar · Fri 13 Nov

Next departure 14:15 tomorrow · Baar
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 8 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 13 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

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

  • Early 6% · 2
  • On time 94% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=8
  • 100% W n=9
  • 100% T n=2
  • 100% F n=7
  • 100% S n=6
  • 100% S n=1

Stops and timetable

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

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