S1 22162 Rotkreuz → Baar

View line S1

Rotkreuz 18:39 → Baar 18:57 Mon, Tue, Wed, Thu, Fri, Sat 0 h 18 min · 10 stops SBB CFF FFS

S1 22162 Rotkreuz–Baar: final delay under 3 min on 24 of its 25 runs with data in the last 30 days (96%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 18:31 (GMT+1).

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 18:39 from Rotkreuz · Sat 21 Nov

Next departure 18:39 today · Rotkreuz
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 19 Nov Max en route +3 min · last fix heading to Baar +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 93% · 39
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 42 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
18:39on time on time
18:42≈ on time ≈ +1 min
18:44≈ on time ≈ +1 min
18:45≈ on time ≈ +1 min
18:47≈ +1 min ≈ +1 min
18:49≈ +1 min ≈ +1 min
18:51≈ +1 min ≈ +1 min
18:53≈ +1 min ≈ +2 min
18:54≈ +1 min ≈ +2 min
18:57+1 min +2 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
Fri 20 NovBaar 18:59+1 min+1 min
Thu 19 NovBaar 18:59+3 min+3 min
Wed 18 NovBaar 18:580 min—
Tue 17 NovBaar 18:59+1 min—
Mon 16 NovBaar 18:57−1 min—
Sat 14 NovBaar 18:58−1 min—
Fri 13 NovBaar 18:58−1 min—
Thu 12 NovBaar 18:59+2 min+2 min
Wed 11 NovBaar 18:59+2 min+2 min
Tue 10 NovBaar 18:59+2 min+2 min
Mon 9 NovBaar 18:59+1 min+1 min
Sat 7 NovBaar 18:570 min—
Fri 6 NovBaar 18:58+1 min—
Thu 5 NovBaar 18:580 min—
Wed 4 NovBaar 18:59+3 min+3 min
Tue 3 NovBaar 18:59+1 min—
Mon 2 NovBaar 18:59+2 min+2 min
Sat 31 OctBaar 18:59+1 min+1 min
Fri 30 OctBaar 19:00+2 min+2 min
Thu 29 OctBaar 18:59+1 min—
Wed 28 OctBaar 18:580 min—
Tue 27 OctBaar 18:590 min—
Mon 26 OctBaar 18:59+1 min+1 min
Sat 24 OctBaar 18:580 min—
Fri 23 OctBaar 18:59+1 min+1 min
Thu 22 OctBaar 18:57−1 min—
Wed 21 OctBaar 19:00+2 min+2 min
Tue 20 OctBaar 19:00+2 min+2 min
Mon 19 OctBaar 18:59+2 min+2 min
Sat 17 OctBaar 18:580 min—