S3 21337 Luzern – Brunnen

View line S3

Luzern 06:06 → Brunnen 06:52 Daily 0 h 46 min · 11 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November −1 min

Next service: today 06:06 from Luzern · Fri 6 Nov

Next departure 06:06 today · Luzern
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 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: 0 min

Last 30 days

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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 34 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
06:06on time on time
06:13≈ on time ≈ on time
06:17≈ on time ≈ on time
06:19≈ on time ≈ on time
06:22≈ on time ≈ on time
06:25 / 06:26≈ on time ≈ on time
06:29 / 06:30≈ on time ≈ on time
06:38 / 06:39≈ on time ≈ on time
06:43≈ on time ≈ on time
06:48≈ on time ≈ +1 min
06:52on 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
Thu 5 NovBrunnen 10:53−1 min—
Wed 4 NovBrunnen 10:540 min—
Tue 3 NovBrunnen 10:530 min—
Mon 2 NovBrunnen 10:53−1 min—
Sun 1 NovBrunnen 10:53+1 min—
Sat 31 OctBrunnen 10:520 min—
Fri 30 OctBrunnen 10:530 min—
Thu 29 OctBrunnen 10:53No data—
Wed 28 OctBrunnen 10:52−1 min—
Tue 27 OctBrunnen 10:52−1 min—
Mon 26 OctLuzern 11:01+2 min+2 min
Sun 25 OctBrunnen 10:520 min—
Sat 24 OctBrunnen 10:520 min—
Fri 23 OctBrunnen 10:52−1 min—
Thu 22 OctBrunnen 10:53−1 min—
Wed 21 OctBrunnen 10:530 min+1 min
Tue 20 OctBrunnen 10:530 min—
Mon 19 OctBrunnen 10:530 min—
Sun 18 OctBrunnen 10:530 min—
Sat 17 OctBrunnen 10:530 min—
Fri 16 OctBrunnen 10:52−1 min—
Thu 15 OctBrunnen 10:52−1 min—
Wed 14 OctBrunnen 10:52−1 min—
Tue 13 OctBrunnen 10:530 min—
Mon 12 OctBrunnen 10:520 min—
Sun 11 OctBrunnen 10:530 min—
Sat 10 OctBrunnen 10:530 min—
Fri 9 OctBrunnen 10:520 min—
Thu 8 OctBrunnen 10:530 min—
Wed 7 OctBrunnen 10:52−1 min—