S7 21735 Langenthal – Wolhusen

View line S7

Langenthal 09:50 → Wolhusen 10:42 Daily 0 h 52 min · 15 stops BLS

✓ Today’s run finished

Today it reached Wolhusen at 10:42 −1 min

  1. Langenthal09:50
  2. Lotzwil09:54
  3. Lindenholz10:00
  4. Rohrbach10:04
  5. Zell LU10:20
  6. Menznau10:35
  7. Wolhusen10:42

Next service: tomorrow 09:50 from Langenthal · Sun 8 Nov

Next departure 09:50 tomorrow · Langenthal
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 2 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 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

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

  • Early 6% · 2
  • On time 94% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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