S6 22729 Langenthal – Wolhusen

View line S6

Langenthal 08:20 → Wolhusen 09:12 Daily 0 h 52 min · 16 stops BLS

✓ Today’s run finished

Today it reached Wolhusen at 09:12 0 min

  1. Langenthal08:20
  2. Gutenburg08:25
  3. Lindenholz08:30
  4. Huttwil08:40
  5. Zell LU08:50
  6. Menznau09:05
  7. Wolhusen09:12

Next service: tomorrow 08:20 from Langenthal · Sat 7 Nov

Next departure 08:20 tomorrow · Langenthal
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 0 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

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

  • Early 9% · 3
  • On time 91% · 31
  • 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=5
  • 100% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 34 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
08:201 min early 1 min early
08:22≈ 1 min early ≈ 1 min early
08:24≈ 1 min early ≈ 1 min early
08:25≈ 1 min early ≈ 1 min early
08:29≈ 1 min early ≈ on time
08:30≈ 1 min early ≈ on time
08:31≈ 1 min early ≈ on time
08:34≈ 1 min early ≈ on time
08:40 / 08:43≈ 1 min early ≈ on time
08:47≈ 1 min early ≈ on time
08:50≈ 1 min early ≈ on time
08:54≈ 1 min early ≈ on time
08:59 / 09:00≈ 1 min early ≈ on time
09:05≈ 1 min early ≈ +1 min
09:08≈ 1 min early ≈ +1 min
09:121 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
Fri 6 NovWolhusen 09:120 min—
Thu 5 NovWolhusen 09:12−1 min—
Wed 4 NovWolhusen 09:130 min—
Tue 3 NovWolhusen 09:13−1 min—
Mon 2 NovWolhusen 09:13−1 min—
Sun 1 NovWolhusen 09:130 min—
Sat 31 OctWolhusen 09:130 min—
Fri 30 OctWolhusen 09:130 min—
Thu 29 OctWolhusen 09:13−1 min—
Wed 28 OctWolhusen 09:15+1 min+1 min
Tue 27 OctWolhusen 09:14+1 min—
Mon 26 OctLangenthal 11:01−1 min—
Sun 25 OctWolhusen 09:12−1 min—
Sat 24 OctWolhusen 09:12−1 min—
Fri 23 OctWolhusen 09:130 min—
Thu 22 OctWolhusen 09:13−1 min—
Wed 21 OctWolhusen 09:12−1 min—
Tue 20 OctWolhusen 09:13−1 min—
Mon 19 OctWolhusen 09:14+1 min—
Sun 18 OctWolhusen 09:12−1 min—
Sat 17 OctWolhusen 09:130 min—
Fri 16 OctWolhusen 09:11−1 min—
Thu 15 OctWolhusen 09:130 min—
Wed 14 OctWolhusen 09:12−1 min—
Tue 13 OctWolhusen 09:14+1 min—
Mon 12 OctWolhusen 09:12−1 min—
Sun 11 OctWolhusen 09:12−1 min—
Sat 10 OctWolhusen 09:130 min—
Fri 9 OctWolhusen 09:120 min—
Thu 8 OctWolhusen 09:130 min—