S2 21264 Walchwil – Baar Lindenpark

View line S2

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

✓ Today’s run finished

Today it reached Baar Lindenpark at 17:26 0 min

  1. Walchwil17:07
  2. Walchwil Hörndli17:09
  3. Zug Oberwil17:14
  4. Zug Casino17:18
  5. Zug Postplatz17:19
  6. Zug17:23
  7. Baar Lindenpark17:26

Next service: tomorrow 17:07 from Walchwil · Wed 18 Nov

Next departure 17:07 tomorrow · 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%
45/45 runs under 3 min
RT coverage: 45 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=6
  • 100% T n=6
  • 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, 45 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
17:07on time on time
17:09≈ on time ≈ on time
17:14 / 17:15≈ on time ≈ on time
17:16≈ on time ≈ on time
17:18≈ on time ≈ on time
17:19≈ on time ≈ on time
17:23≈ on time ≈ on time
17: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
Tue 17 NovBaar Lindenpark 17:270 min—
Mon 16 NovBaar Lindenpark 17:270 min—
Sat 14 NovBaar Lindenpark 17:240 min—
Fri 13 NovBaar Lindenpark 17:27−1 min—
Thu 12 NovBaar Lindenpark 17:29+2 min+2 min
Wed 11 NovBaar Lindenpark 17:270 min—
Tue 10 NovBaar Lindenpark 17:270 min—
Mon 9 NovBaar Lindenpark 17:240 min—
Sat 7 NovBaar Lindenpark 17:240 min—
Fri 6 NovBaar Lindenpark 17:270 min—
Thu 5 NovBaar Lindenpark 17:28+1 min+1 min
Wed 4 NovBaar Lindenpark 17:27−1 min—
Tue 3 NovBaar Lindenpark 17:270 min—
Mon 2 NovBaar Lindenpark 17:280 min—
Sat 31 OctBaar Lindenpark 17:260 min—
Fri 30 OctBaar Lindenpark 17:26−1 min—
Thu 29 OctBaar Lindenpark 17:29+2 min+2 min
Wed 28 OctBaar Lindenpark 17:27−1 min—
Tue 27 OctBaar Lindenpark 17:27−1 min—
Mon 26 OctBaar Lindenpark 17:27−1 min—
Sat 24 OctBaar Lindenpark 17:26−1 min—
Fri 23 OctBaar Lindenpark 17:270 min—
Thu 22 OctBaar Lindenpark 17:29+2 min+2 min
Wed 21 OctBaar Lindenpark 17:270 min—
Tue 20 OctBaar Lindenpark 17:270 min—
Mon 19 OctBaar Lindenpark 17:270 min—
Sat 17 OctBaar Lindenpark 17:26−1 min—
Fri 16 OctBaar Lindenpark 17:280 min—
Thu 15 OctBaar Lindenpark 17:270 min—
Wed 14 OctBaar Lindenpark 17:270 min—