S1 21021 Emmenbrücke – Sursee

View line S1

Emmenbrücke 04:26 → Sursee 04:50 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 8 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: Monday 04:26 from Emmenbrücke · Mon 9 Nov

Next departure 04:26 Monday · Emmenbrücke
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 19 full · 2 partial · 0 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 26 full · 2 partial · 0 no data
Typical delay
−1min
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 Sursee, 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

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

  • Early 36% · 10
  • On time 64% · 18
  • 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=6
  • 100% W n=6
  • 100% T n=7
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
04:26on time on time
04:28≈ on time ≈ on time
04:31≈ on time ≈ on time
04:34≈ on time ≈ on time
04:39≈ on time ≈ on time
04:43≈ 1 min early ≈ on time
04:46≈ 1 min early ≈ on time
04:501 min early +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 NovRotkreuz 07:58Partial coverage0 min—
Wed 4 NovRotkreuz 07:57Partial coverage−1 min—
Tue 3 NovRotkreuz 07:57−2 min—
Mon 2 NovRotkreuz 07:57−1 min—
Fri 30 OctRotkreuz 07:56−2 min—
Thu 29 OctRotkreuz 07:57−1 min—
Wed 28 OctRotkreuz 07:57−1 min—
Tue 27 OctRotkreuz 07:57−1 min—
Mon 26 OctRotkreuz 07:580 min—
Fri 23 OctRotkreuz 07:57−1 min—
Thu 22 OctRotkreuz 07:58−1 min—
Wed 21 OctRotkreuz 07:59+1 min+1 min
Tue 20 OctRotkreuz 07:58−1 min—
Mon 19 OctRotkreuz 07:580 min—
Fri 16 OctRotkreuz 07:56−2 min—
Thu 15 OctRotkreuz 07:580 min—
Wed 14 OctRotkreuz 07:57−1 min—
Tue 13 OctRotkreuz 07:590 min—
Mon 12 OctRotkreuz 07:56−2 min—
Fri 9 OctRotkreuz 07:56−2 min—
Thu 8 OctRotkreuz 07:57−1 min—
Wed 7 OctRotkreuz 07:56−2 min—
Tue 6 OctRotkreuz 07:56−2 min—
Mon 5 OctRotkreuz 07:57−2 min—
Thu 1 OctRotkreuz 16:57+1 min+1 min
Wed 30 SeptRotkreuz 16:56−1 min—
Thu 24 SeptSursee 00:54+1 min—
Tue 22 SeptSursee 00:540 min—