S2 21260 Walchwil → Baar Lindenpark

View line S2

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

S2 21260 Walchwil–Baar Lindenpark: final delay under 3 min on 26 of its 26 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 22:33 (GMT+1).

✓ Today’s run finished

Today it reached Baar Lindenpark at 16:26 0 min

  1. Walchwil16:07
  2. Walchwil Hörndli16:09
  3. Zug Oberwil16:14
  4. Zug Casino16:18
  5. Zug Postplatz16:19
  6. Zug16:23
  7. Baar Lindenpark16:26

Next service: Monday 16:07 from Walchwil · Mon 23 Nov

Next departure 16:07 Monday · Walchwil
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
100%
42/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 42
  • 3–10 min 0% · 0
  • 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
  • 100% 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 (8 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
16:07on time on time
16:09≈ on time ≈ on time
16:14 / 16:15≈ on time ≈ on time
16:16≈ on time ≈ on time
16:18≈ on time ≈ on time
16:19≈ on time ≈ on time
16:23≈ on time ≈ on time
16:261 min early 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
Sat 21 NovBaar Lindenpark 16:240 min—
Fri 20 NovBaar Lindenpark 16:270 min—
Thu 19 NovBaar Lindenpark 16:240 min—
Wed 18 NovBaar Lindenpark 16:240 min—
Tue 17 NovBaar Lindenpark 16:27−1 min—
Mon 16 NovBaar Lindenpark 16:240 min—
Sat 14 NovBaar Lindenpark 16:240 min—
Fri 13 NovBaar Lindenpark 16:27−1 min—
Thu 12 NovBaar Lindenpark 16:240 min—
Wed 11 NovBaar Lindenpark 16:240 min—
Tue 10 NovBaar Lindenpark 16:240 min—
Mon 9 NovBaar Lindenpark 16:240 min—
Sat 7 NovBaar Lindenpark 16:240 min—
Fri 6 NovBaar Lindenpark 16:240 min—
Thu 5 NovBaar Lindenpark 16:270 min—
Wed 4 NovBaar Lindenpark 16:240 min—
Tue 3 NovBaar Lindenpark 16:27−1 min—
Mon 2 NovBaar Lindenpark 16:27−1 min—
Sat 31 OctBaar Lindenpark 16:260 min—
Fri 30 OctBaar Lindenpark 16:26−1 min—
Thu 29 OctBaar Lindenpark 16:27−1 min—
Wed 28 OctBaar Lindenpark 16:27−1 min—
Tue 27 OctBaar Lindenpark 16:270 min—
Mon 26 OctBaar Lindenpark 16:27−1 min—
Sat 24 OctBaar Lindenpark 16:26−1 min—
Fri 23 OctBaar Lindenpark 16:260 min—
Thu 22 OctBaar Lindenpark 16:27−1 min—
Wed 21 OctBaar Lindenpark 16:26−1 min—
Tue 20 OctBaar Lindenpark 16:27−1 min—
Mon 19 OctBaar Lindenpark 16:260 min—