S6 22716 Wolhusen – Langenthal

View line S6

Wolhusen 05:46 → Langenthal 06:38 Daily 0 h 52 min · 16 stops BLS

✓ Today’s run finished

Today it reached Langenthal at 06:38 0 min

  1. Wolhusen05:46
  2. Willisau05:58
  3. Zell LU06:05
  4. Rohrbach06:19
  5. Lindenholz06:23
  6. Lotzwil06:32
  7. Langenthal06:38

Next service: tomorrow 05:46 from Wolhusen · Wed 18 Nov

Next departure 05:46 tomorrow · Wolhusen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 1 no data
On-time · 90 days
100%
49/49 runs under 3 min
RT coverage: 49 full · 0 partial · 2 no data
Typical delay
0min
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 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

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

  • Early 6% · 3
  • On time 94% · 46
  • 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=8
  • 100% T n=7
  • 100% F n=8
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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