IR70 2645 Zürich HB – Luzern

View line IR70

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

It has not run yet today

Last recorded run: Thursday 19 November +3 min

Next service: today 23:10 from Zürich HB · Fri 20 Nov

Next departure 23:10 today · Zürich HB
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
96%
49/51 runs under 3 min
RT coverage: 51 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 4 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Sun 8 Nov Max en route +3 min · last fix heading to Ebikon +3 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 92% · 47
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=6
  • 100% W n=10
  • 100% T n=9
  • 100% F n=5
  • 100% S n=7
  • 67% S n=6

Stops and timetable

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

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