S6 22773 Langenthal – Wolhusen

View line S6

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

It has not run yet today

Last recorded run: Thursday 5 November −1 min

Next service: today 19:20 from Langenthal · Fri 6 Nov

Next departure 19:20 today · Langenthal
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Mon 5 Oct Max en route +4 min · last fix heading to Wolhusen +4 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 92% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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