S6 22761 Langenthal – Wolhusen

View line S6

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

✓ Today’s run finished

Today it reached Wolhusen at 17:12 −1 min

  1. Langenthal16:20
  2. Gutenburg16:25
  3. Lindenholz16:30
  4. Huttwil16:40
  5. Zell LU16:50
  6. Menznau17:05
  7. Wolhusen17:12

Next service: tomorrow 16:20 from Langenthal · Fri 13 Nov

Next departure 16: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%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 7% · 3
  • On time 93% · 43
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
16:201 min early on time
16:22≈ 1 min early ≈ on time
16:24≈ 1 min early ≈ on time
16:25≈ 1 min early ≈ on time
16:29≈ 1 min early ≈ on time
16:30≈ 1 min early ≈ on time
16:31≈ 1 min early ≈ on time
16:34≈ 1 min early ≈ on time
16:40 / 16:43≈ 1 min early ≈ on time
16:47≈ 1 min early ≈ on time
16:50≈ 1 min early ≈ on time
16:54≈ on time ≈ on time
16:59 / 17:00≈ on time ≈ on time
17:05≈ on time ≈ on time
17:08≈ on time ≈ on time
17:12on time on time

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 12 NovWolhusen 17:12−1 min—
Wed 11 NovWolhusen 17:12−1 min—
Tue 10 NovWolhusen 17:120 min—
Mon 9 NovWolhusen 17:130 min—
Sun 8 NovWolhusen 17:130 min—
Sat 7 NovWolhusen 17:12−1 min—
Fri 6 NovWolhusen 17:130 min—
Thu 5 NovWolhusen 17:130 min—
Wed 4 NovWolhusen 17:130 min—
Tue 3 NovWolhusen 17:140 min—
Mon 2 NovWolhusen 17:130 min—
Sun 1 NovWolhusen 17:120 min—
Sat 31 OctWolhusen 17:130 min—
Fri 30 OctWolhusen 17:130 min—
Thu 29 OctWolhusen 17:130 min—
Wed 28 OctWolhusen 17:13−1 min—
Tue 27 OctWolhusen 17:130 min—
Mon 26 OctWolhusen 17:130 min—
Sun 25 OctWolhusen 17:15+2 min+2 min
Sat 24 OctWolhusen 17:12−1 min—
Fri 23 OctWolhusen 17:12−1 min—
Thu 22 OctWolhusen 17:130 min—
Wed 21 OctWolhusen 17:130 min—
Tue 20 OctWolhusen 17:130 min—
Mon 19 OctWolhusen 17:130 min—
Sun 18 OctWolhusen 17:12−1 min—
Sat 17 OctWolhusen 17:130 min—
Fri 16 OctWolhusen 17:140 min—
Thu 15 OctWolhusen 17:12−1 min—
Wed 14 OctWolhusen 17:130 min—