S6 22752 Wolhusen – Langenthal

View line S6

Wolhusen 14:46 → Langenthal 15:38 Daily 0 h 52 min · 16 stops BLS

✓ Today’s run finished

Today it reached Langenthal at 15:38 0 min

  1. Wolhusen14:46
  2. Willisau14:58
  3. Zell LU15:05
  4. Rohrbach15:19
  5. Lindenholz15:23
  6. Lotzwil15:32
  7. Langenthal15:38

Next service: tomorrow 14:46 from Wolhusen · Mon 16 Nov

Next departure 14:46 tomorrow · Wolhusen
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%
51/51 runs under 3 min
RT coverage: 51 full · 0 partial · 2 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 Langenthal, 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

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

  • Early 24% · 12
  • On time 76% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=9
  • 100% W n=7
  • 100% T n=6
  • 100% F n=7
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

Last 90 days, 51 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
14:46on time on time
14:47≈ on time ≈ on time
14:51≈ on time ≈ on time
14:58≈ on time ≈ on time
15:01≈ on time ≈ on time
15:05≈ on time ≈ on time
15:07≈ on time ≈ on time
15:14 / 15:16≈ on time ≈ on time
15:19≈ on time ≈ on time
15:22≈ on time ≈ on time
15:23≈ on time ≈ +1 min
15:26 / 15:27≈ on time ≈ +1 min
15:28≈ on time ≈ +1 min
15:32≈ on time ≈ +1 min
15:34≈ on time ≈ +1 min
15:38on 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
Sun 15 NovLangenthal 15:390 min—
Sat 14 NovLangenthal 15:38−1 min—
Fri 13 NovLangenthal 15:39−1 min—
Thu 12 NovLangenthal 15:39+1 min—
Wed 11 NovLangenthal 15:390 min—
Tue 10 NovLangenthal 15:390 min—
Mon 9 NovLangenthal 15:390 min—
Sun 8 NovLangenthal 15:390 min—
Sat 7 NovLangenthal 15:39+1 min+1 min
Fri 6 NovLangenthal 15:390 min—
Thu 5 NovLangenthal 15:39No data—
Wed 4 NovLangenthal 15:390 min—
Tue 3 NovLangenthal 15:390 min—
Mon 2 NovLangenthal 15:390 min—
Sun 1 NovLangenthal 15:390 min—
Sat 31 OctLangenthal 15:390 min—
Fri 30 OctLangenthal 15:38−1 min—
Thu 29 OctLangenthal 15:390 min—
Wed 28 OctLangenthal 15:41+1 min+1 min
Tue 27 OctLangenthal 15:390 min—
Mon 26 OctLangenthal 15:39−1 min—
Sun 25 OctHuttwil 15:16+3 min+3 min
Sat 24 OctHuttwil 15:140 min—
Fri 23 OctHuttwil 15:13−1 min—
Thu 22 OctHuttwil 15:13−3 min—
Wed 21 OctHuttwil 15:15+1 min—
Tue 20 OctHuttwil 15:13−1 min—
Mon 19 OctHuttwil 15:13−2 min—
Sun 18 OctHuttwil 15:14−1 min—
Sat 17 OctHuttwil 15:13−2 min—