S1 22140 Rotkreuz – Baar

View line S1

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

✓ Today’s run finished

Today it reached Baar at 13:43 +1 min

  1. Rotkreuz13:23
  2. Hünenberg Zythus13:27
  3. Cham13:29
  4. Zug Chollermüli13:32
  5. Zug13:37
  6. Baar Lindenpark13:38
  7. Baar13:42

Next service: tomorrow 13:23 from Rotkreuz · Thu 19 Nov

Next departure 13:23 tomorrow · Rotkreuz
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 6 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 9 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 Baar, 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

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

  • Early 0% · 0
  • On time 100% · 30
  • 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=7
  • 100% W n=7
  • 100% T n=2
  • 100% F n=6
  • 100% S n=6
  • — S n=0

Stops and timetable

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

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