S1 21111 Zug – Sursee

View line S1

Zug 05:06 → Sursee 06:10 Daily 1 h 04 min · 20 stops SBB CFF FFS

Running now · updated 05:40

Position estimated from the timetable

Between Ebikon and Luzern 0 min

Estimated arrival at Sursee 06:10 · 18 km/h

  1. Zug05:06
  2. Cham Alpenblick05:11
  3. Rotkreuz05:19
  4. Ebikon05:29
  5. Luzern05:38
  6. Emmenbrücke Gersag05:51
  7. Sursee06:10

Today it is running no worse than usual: typical arrival delay is +2 min; 93% of the last 29 runs arrived on time.

On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 28 full · 1 partial · 1 no data
On-time · 90 days
96%
65/68 runs under 3 min
RT coverage: 67 full · 1 partial · 5 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Sursee, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 13 Oct Max en route +6 min · last fix heading to Sursee +6 min
  • Sat 17 Oct Max en route +3 min · last fix heading to Sursee +3 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Sursee +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 65
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 92% T n=12
  • 100% W n=10
  • 100% T n=9
  • 100% F n=10
  • 80% S n=10
  • 100% S n=7

Stops and timetable

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

Last 90 days, 68 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 10Today
05:06on time +1 minPassed
05:07≈ on time ≈ +1 minPassed
05:09≈ on time ≈ +1 minPassed
05:11≈ on time ≈ +1 minPassed
05:13≈ on time ≈ +1 minPassed
05:14≈ on time ≈ +1 minPassed
05:19≈ on time ≈ +1 minPassed
05:22≈ +1 min ≈ +1 minPassed
05:25≈ +1 min ≈ +1 minPassed
05:27≈ +1 min ≈ +1 minPassed
05:29≈ +1 min ≈ +1 minPassed
05:38 / 05:44≈ +1 min ≈ +1 minNext
05:49≈ +1 min ≈ +1 min
05:51 / 05:52≈ +1 min ≈ +2 min
05:54≈ +1 min ≈ +2 min
05:57≈ +1 min ≈ +2 min
06:01≈ +1 min ≈ +2 min
06:04≈ +1 min ≈ +2 min
06:07≈ +1 min ≈ +2 min
06:10+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
Thu 12 NovLuzern 05:39Partial coverage0 min—
Wed 11 NovSursee 06:090 min—
Tue 10 NovSursee 06:120 min—
Mon 9 NovSursee 06:13+2 min+2 min
Sun 8 NovSursee 06:12+1 min+1 min
Sat 7 NovSursee 06:14+3 min+3 min
Fri 6 NovSursee 06:13+1 min+1 min
Thu 5 NovSursee 06:13+2 min+2 min
Wed 4 NovSursee 06:13+2 min+2 min
Tue 3 NovSursee 06:120 min—
Mon 2 NovSursee 06:120 min—
Sun 1 NovSursee 06:11No data—
Sat 31 OctSursee 06:13+2 min+2 min
Fri 30 OctSursee 06:13+2 min+2 min
Thu 29 OctSursee 06:12+1 min—
Wed 28 OctSursee 06:13+2 min+2 min
Tue 27 OctSursee 06:13+2 min+2 min
Mon 26 OctSursee 06:12+1 min+1 min
Sun 25 OctSursee 06:12+1 min+1 min
Sat 24 OctSursee 06:12+1 min—
Fri 23 OctSursee 06:13+2 min+2 min
Thu 22 OctSursee 06:13+2 min+2 min
Wed 21 OctSursee 06:13+2 min+2 min
Tue 20 OctSursee 06:13+3 min+3 min
Mon 19 OctSursee 06:14+3 min+3 min
Sun 18 OctSursee 06:12+1 min+1 min
Sat 17 OctSursee 06:14+3 min+3 min
Fri 16 OctSursee 06:12+1 min+1 min
Thu 15 OctSursee 06:13+1 min+1 min
Wed 14 OctSursee 06:13+2 min+2 min