RE7 4483 Wolhusen – Luzern

View line RE7

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

It has not run yet today

Last recorded run: Friday 6 November +4 min

Next service: today 19:45 from Wolhusen · Sat 7 Nov

Next departure 19:45 today · Wolhusen
On-time · 30 days
76%
22/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
77%
34/44 runs under 3 min
RT coverage: 44 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 +10 min · last fix heading to Luzern +10 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Luzern +4 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Luzern +4 min
  • Thu 22 Oct Max en route +4 min · last fix heading to Luzern +4 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 34
  • 3–10 min 23% · 10
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 57% T n=7
  • 100% W n=6
  • 67% T n=6
  • 57% F n=7
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

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