IR75 2126 Konstanz → Luzern

View line IR75

Konstanz 15:09 → Luzern 17:25 Daily 2 h 16 min · 12 stops SBB CFF FFS

IR75 2126 Konstanz–Luzern: final delay under 3 min on 24 of its 27 runs with data in the last 30 days (89%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 19:58 (GMT+1).

✓ Today’s run finished

Today it reached Luzern at 17:26 +1 min

  1. Konstanz15:09
  2. Weinfelden15:35
  3. Winterthur15:59
  4. Zürich HB16:26
  5. Thalwil16:45
  6. Zug17:02
  7. Luzern17:25

Next service: tomorrow 15:09 from Konstanz · Sun 22 Nov

Next departure 15:09 tomorrow · Konstanz
On-time · 30 days
89%
24/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
90%
47/52 runs under 3 min
RT coverage: 52 full · 0 partial · 9 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

  • Fri 6 Nov Max en route +6 min · last fix heading to Luzern +6 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Fri 4 Sept Max en route +3 min · last fix heading to Zürich HB +3 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 12% · 6
  • On time 79% · 41
  • 3–10 min 10% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 88% T n=8
  • 100% W n=8
  • 100% T n=5
  • 56% F n=9
  • 100% S n=9
  • 100% S n=7

Stops and timetable

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

Last 90 days, 52 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
15:091 min early on time
15:12 / 15:16≈ 1 min early ≈ on time
15:35 / 15:36≈ on time ≈ on time
15:47 / 15:48≈ on time ≈ on time
15:59 / 16:01≈ on time ≈ +1 min
16:14 / 16:15≈ on time ≈ +1 min
16:26 / 16:35≈ on time ≈ +1 min
16:45≈ on time ≈ +2 min
16:58≈ +1 min ≈ +2 min
17:02 / 17:03≈ +1 min ≈ +2 min
17:11≈ +1 min ≈ +2 min
17:25+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
Sat 21 NovLuzern 17:24+1 min+1 min
Fri 20 NovLuzern 17:240 min—
Thu 19 NovLuzern 17:24No data—
Wed 18 NovLuzern 17:24+2 min+2 min
Tue 17 NovLuzern 17:24−1 min—
Mon 16 NovLuzern 17:24−1 min—
Sun 15 NovLuzern 17:240 min—
Sat 14 NovLuzern 17:24+2 min+2 min
Fri 13 NovLuzern 17:24−2 min—
Thu 12 NovLuzern 17:24No data—
Wed 11 NovLuzern 17:240 min—
Tue 10 NovLuzern 17:24−1 min—
Mon 9 NovLuzern 17:24No data—
Sun 8 NovEbikon 17:190 min—
Sat 7 NovEbikon 17:190 min—
Fri 6 NovLuzern 17:32+6 min+6 min
Thu 5 NovLuzern 17:240 min—
Wed 4 NovLuzern 17:27+1 min—
Tue 3 NovLuzern 17:28+2 min+2 min
Mon 2 NovLuzern 17:29+3 min+3 min
Sun 1 NovLuzern 17:27+1 min+1 min
Sat 31 OctLuzern 17:260 min—
Fri 30 OctLuzern 17:29+3 min+3 min
Thu 29 OctLuzern 17:28+2 min+2 min
Wed 28 OctLuzern 17:28+2 min+2 min
Tue 27 OctLuzern 17:29+3 min+3 min
Mon 26 OctLuzern 17:28+2 min+2 min
Sun 25 OctLuzern 17:28+3 min+3 min
Sat 24 OctLuzern 17:27+1 min+1 min
Fri 23 OctLuzern 17:31+5 min+5 min