S2 21244 Walchwil – Baar Lindenpark

View line S2

Walchwil 12:07 → Baar Lindenpark 12:26 Mon, Tue, Wed, Thu, Fri, Sat 0 h 19 min · 8 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 12:07 from Walchwil · Thu 19 Nov

Next departure 12:07 today · Walchwil
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 8 no data
On-time · 90 days
100%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Baar Lindenpark, 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

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

  • Early 0% · 0
  • On time 100% · 46
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=11
  • 100% W n=9
  • 100% T n=4
  • 100% F n=9
  • 100% S n=9
  • — S n=0

Stops and timetable

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

Last 90 days, 46 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
12:07on time on time
12:09≈ on time ≈ on time
12:14 / 12:15≈ on time ≈ on time
12:16≈ on time ≈ on time
12:18≈ on time ≈ on time
12:19≈ on time ≈ on time
12:23≈ on time ≈ on time
12:26on time on time

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 Lindenpark 12:29+2 min+2 min
Tue 17 NovBaar Lindenpark 12:230 min—
Mon 16 NovBaar Lindenpark 12:27No data—
Sat 14 NovBaar Lindenpark 12:270 min—
Fri 13 NovBaar Lindenpark 12:27−1 min—
Thu 12 NovBaar Lindenpark 12:27No data—
Wed 11 NovBaar Lindenpark 12:270 min—
Tue 10 NovBaar Lindenpark 12:27−1 min—
Mon 9 NovBaar Lindenpark 12:27No data—
Sat 7 NovBaar Lindenpark 12:270 min—
Fri 6 NovBaar Lindenpark 12:27−1 min—
Thu 5 NovBaar Lindenpark 12:27No data—
Wed 4 NovBaar Lindenpark 12:240 min—
Tue 3 NovBaar Lindenpark 12:27−1 min—
Mon 2 NovBaar Lindenpark 12:27No data—
Sat 31 OctBaar Lindenpark 12:26−1 min—
Fri 30 OctBaar Lindenpark 12:26−1 min—
Thu 29 OctBaar Lindenpark 12:27No data—
Wed 28 OctBaar Lindenpark 12:270 min—
Tue 27 OctBaar Lindenpark 12:27−1 min—
Mon 26 OctBaar Lindenpark 12:27No data—
Sat 24 OctBaar Lindenpark 12:26−1 min—
Fri 23 OctBaar Lindenpark 12:26−1 min—
Thu 22 OctBaar Lindenpark 12:27No data—
Wed 21 OctBaar Lindenpark 12:270 min—
Tue 20 OctBaar Lindenpark 12:27−1 min—
Mon 19 OctBaar Lindenpark 12:27No data—
Sat 17 OctBaar Lindenpark 12:270 min—
Fri 16 OctBaar Lindenpark 12:270 min—
Thu 15 OctBaar Lindenpark 12:27No data—