RE7 4461 Malters – Luzern

View line RE7

Malters 08:52 → Luzern 09:03 Daily 0 h 11 min · 2 stops BLS

✓ Today’s run finished

Today it reached Luzern at 09:04 +1 min

  1. Malters08:52
  2. Luzern09:03

Next service: tomorrow 08:52 from Malters · Sun 15 Nov

Next departure 08:52 tomorrow · Malters
On-time · 30 days
100%
30/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 · 3 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
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

  • Thu 10 Sept Max en route +5 min · last fix heading to Aarau +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Aarau +4 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 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (2 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
08:52on time on time
09:03+1 min +1 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 14 NovLuzern 09:04+1 min+1 min
Fri 13 NovAarau 20:19+1 min+1 min
Thu 12 NovAarau 20:200 min—
Wed 11 NovAarau 20:19+1 min+1 min
Tue 10 NovAarau 20:190 min+1 min
Mon 9 NovAarau 20:190 min—
Sun 8 NovAarau 20:19+1 min—
Sat 7 NovAarau 20:19+1 min+1 min
Fri 6 NovAarau 20:19+1 min—
Thu 5 NovAarau 20:180 min+4 min
Wed 4 NovAarau 20:19+1 min+3 min
Tue 3 NovAarau 20:19+1 min—
Mon 2 NovAarau 20:19+1 min+1 min
Sun 1 NovAarau 20:19+1 min—
Sat 31 OctAarau 20:200 min—
Fri 30 OctAarau 20:21+1 min+1 min
Thu 29 OctAarau 20:21+1 min—
Wed 28 OctAarau 20:200 min+2 min
Tue 27 OctAarau 20:200 min—
Mon 26 OctAarau 20:22+1 min+2 min
Sun 25 OctAarau 20:200 min—
Sat 24 OctAarau 20:20+1 min+5 min
Fri 23 OctAarau 20:200 min—
Thu 22 OctAarau 20:210 min+1 min
Wed 21 OctAarau 20:20+1 min+1 min
Tue 20 OctAarau 20:21+1 min—
Mon 19 OctAarau 20:21+1 min—
Sun 18 OctAarau 20:22+2 min+2 min
Sat 17 OctAarau 20:21+1 min+1 min
Fri 16 OctAarau 20:23+2 min+2 min