RE7 4485 Wolhusen – Luzern

View line RE7

Wolhusen 20:45 → Luzern 21:03 Daily 0 h 18 min · 3 stops BLS

It has not run yet today

Last recorded run: Thursday 12 November +1 min

Next service: today 20:45 from Wolhusen · Fri 13 Nov

Next departure 20:45 today · Wolhusen
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
46/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 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 5 Oct Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 46
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=8
  • 100% F n=5
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 47 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
20:45on time on time
20:52≈ on time ≈ +1 min
21:03+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 21:04+1 min+1 min
Wed 11 NovLuzern 21:07+3 min+3 min
Tue 10 NovLuzern 21:04+1 min—
Mon 9 NovLuzern 21:04+2 min+2 min
Sun 8 NovLuzern 21:04+2 min+2 min
Sat 7 NovLuzern 21:04+2 min+2 min
Fri 6 NovLuzern 21:04+1 min—
Thu 5 NovLuzern 21:040 min—
Wed 4 NovLuzern 21:04+2 min+2 min
Tue 3 NovLuzern 21:04+1 min+1 min
Mon 2 NovLuzern 21:04+1 min—
Sun 1 NovLuzern 21:07+2 min+2 min
Sat 31 OctLuzern 21:040 min—
Fri 30 OctLuzern 21:07+3 min+3 min
Thu 29 OctLuzern 21:05+1 min+1 min
Wed 28 OctLuzern 21:06+2 min+2 min
Tue 27 OctLuzern 21:05+1 min—
Mon 26 OctLuzern 21:05+1 min—
Sun 25 OctLuzern 21:06+2 min+2 min
Sat 24 OctLuzern 21:05+1 min+1 min
Fri 23 OctLuzern 21:07+3 min+3 min
Thu 22 OctLuzern 21:05+1 min+1 min
Wed 21 OctLuzern 21:05+1 min—
Tue 20 OctLuzern 21:050 min—
Mon 19 OctLuzern 21:05+1 min—
Sun 18 OctLuzern 21:05+1 min+1 min
Sat 17 OctLuzern 21:05+1 min+1 min
Fri 16 OctLuzern 21:05+1 min+1 min
Thu 15 OctLuzern 21:06+2 min+2 min
Wed 14 OctLuzern 21:06+2 min+2 min