S6 22748 Wolhusen – Langenthal

View line S6

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

✓ Today’s run finished

Today, last fix heading to Langenthal at 14:39 No data

  1. Wolhusen13:46
  2. Willisau13:58
  3. Zell LU14:05
  4. Rohrbach14:19
  5. Lindenholz14:23
  6. Lotzwil14:32
  7. Langenthal14:38

Next service: tomorrow 13:46 from Wolhusen · Fri 6 Nov

Next departure 13:46 tomorrow · Wolhusen
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%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 9 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

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

  • Early 17% · 6
  • On time 83% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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