S7 21751 Langenthal – Wolhusen

View line S7

Langenthal 13:50 → Wolhusen 14:42 Daily 0 h 52 min · 15 stops BLS

✓ Today’s run finished

Today, last fix heading to Wolhusen at 14:43 No data

  1. Langenthal13:50
  2. Lotzwil13:54
  3. Lindenholz14:00
  4. Rohrbach14:04
  5. Zell LU14:20
  6. Menznau14:35
  7. Wolhusen14:42

Next service: tomorrow 13:50 from Langenthal · Fri 6 Nov

Next departure 13:50 tomorrow · Langenthal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Wolhusen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=5
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 31 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
13:501 min early on time
13:52≈ 1 min early ≈ on time
13:54≈ 1 min early ≈ on time
13:55≈ 1 min early ≈ on time
13:59≈ 1 min early ≈ on time
14:00≈ 1 min early ≈ on time
14:01≈ 1 min early ≈ on time
14:04≈ 1 min early ≈ on time
14:10 / 14:13≈ on time ≈ on time
14:20≈ on time ≈ on time
14:24≈ on time ≈ on time
14:29 / 14:30≈ on time ≈ on time
14:35≈ on time ≈ +1 min
14:38≈ on time ≈ +1 min
14:42on time +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
Thu 5 NovWolhusen 14:43No data—
Wed 4 NovWolhusen 14:430 min—
Tue 3 NovWolhusen 14:430 min—
Mon 2 NovWolhusen 14:43No data—
Sun 1 NovWolhusen 14:43+1 min—
Sat 31 OctWolhusen 14:430 min—
Fri 30 OctWolhusen 14:430 min—
Thu 29 OctWolhusen 14:43No data—
Wed 28 OctWolhusen 14:43−1 min—
Tue 27 OctWolhusen 14:430 min—
Mon 26 OctWolhusen 14:43No data—
Sun 25 OctWolhusen 14:43+1 min—
Sat 24 OctWolhusen 14:44+1 min+1 min
Fri 23 OctWolhusen 14:42−1 min—
Thu 22 OctWolhusen 14:43No data—
Wed 21 OctWolhusen 14:430 min—
Tue 20 OctWolhusen 14:430 min—
Mon 19 OctWolhusen 14:43No data—
Sun 18 OctWolhusen 14:430 min—
Sat 17 OctWolhusen 14:44+1 min—
Fri 16 OctWolhusen 14:430 min—
Thu 15 OctWolhusen 14:43No data—
Wed 14 OctWolhusen 14:42−1 min—
Tue 13 OctWolhusen 14:430 min—
Mon 12 OctWolhusen 14:43No data—
Sun 11 OctWolhusen 14:430 min—
Sat 10 OctWolhusen 14:430 min—
Fri 9 OctWolhusen 14:420 min—
Thu 8 OctWolhusen 14:430 min—
Wed 7 OctWolhusen 14:420 min—