S6 22749 Langenthal – Wolhusen

View line S6

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

✓ Today’s run finished

Today it reached Wolhusen at 14:12 −1 min

  1. Langenthal13:20
  2. Gutenburg13:25
  3. Lindenholz13:30
  4. Huttwil13:40
  5. Zell LU13:50
  6. Menznau14:05
  7. Wolhusen14:12

Next service: tomorrow 13:20 from Langenthal · Wed 18 Nov

Next departure 13:20 tomorrow · Langenthal
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 · 10 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 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

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

  • Early 8% · 3
  • On time 92% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=6
  • 100% T n=2
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

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