IR70 2631 Zürich HB – Luzern

View line IR70

Zürich HB 16:10 → Luzern 16:51 Daily 0 h 41 min · 3 stops SBB CFF FFS

It has not run yet today

Last recorded run: Monday 9 November +3 min

Next service: today 16:10 from Zürich HB · Tue 10 Nov

Next departure 16:10 today · Zürich HB
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 3 no data
On-time · 90 days
92%
33/36 runs under 3 min
RT coverage: 36 full · 0 partial · 3 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Mon 2 Nov Max en route +19 min · last fix heading to Luzern +19 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Luzern +3 min
  • Sun 4 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 33
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 100% T n=6
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 36 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:10on time on time
16:31 / 16:32≈ +1 min ≈ +1 min
16:51+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
Mon 9 NovLuzern 16:54+3 min+3 min
Sun 8 NovEbikon 16:440 min—
Sat 7 NovEbikon 16:440 min—
Fri 6 NovLuzern 16:52No data—
Thu 5 NovLuzern 16:520 min—
Wed 4 NovLuzern 16:530 min—
Tue 3 NovLuzern 16:54+2 min+2 min
Mon 2 NovLuzern 17:04+19 min+19 min
Sat 31 OctLuzern 16:53+1 min—
Fri 30 OctLuzern 16:53+1 min—
Thu 29 OctLuzern 16:53+1 min+1 min
Wed 28 OctLuzern 16:53+1 min—
Tue 27 OctLuzern 16:54+2 min+2 min
Mon 26 OctLuzern 16:54+2 min+2 min
Sun 25 OctLuzern 16:53+1 min+1 min
Sat 24 OctLuzern 16:54+2 min+2 min
Fri 23 OctLuzern 16:53No data—
Thu 22 OctLuzern 16:52No data—
Wed 21 OctLuzern 16:520 min—
Tue 20 OctLuzern 16:55+2 min+2 min
Mon 19 OctLuzern 16:52+1 min—
Sun 18 OctLuzern 16:520 min—
Sat 17 OctLuzern 16:53+2 min+2 min
Fri 16 OctLuzern 16:53+1 min—
Thu 15 OctLuzern 16:53+1 min—
Wed 14 OctLuzern 16:520 min—
Tue 13 OctLuzern 16:53+1 min—
Mon 12 OctLuzern 16:54+2 min+2 min
Sun 11 OctLuzern 16:520 min—
Sat 10 OctLuzern 16:54+1 min+1 min