RE7 4469 Wolhusen – Luzern

View line RE7

Wolhusen 12:45 → Luzern 13:03 Daily 0 h 18 min · 3 stops BLS

✓ Today’s run finished

Today it reached Luzern at 13:03 0 min

  1. Wolhusen12:45
  2. Malters12:52
  3. Luzern13:03

Next service: tomorrow 12:45 from Wolhusen · Sun 8 Nov

Next departure 12:45 tomorrow · Wolhusen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
63/65 runs under 3 min
RT coverage: 65 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 22 Aug Max en route +24 min · last fix heading to Werthenstein +24 min
  • Sat 31 Oct Max en route +6 min · last fix heading to Aarau +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 63
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=8
  • 100% T n=8
  • 100% F n=11
  • 82% S n=11
  • 100% S n=8

Stops and timetable

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

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