S7 21767 Langenthal – Wolhusen

View line S7

Langenthal 17:50 → Wolhusen 18:42 Daily 0 h 52 min · 15 stops BLS

✓ Today’s run finished

Today it reached Wolhusen at 18:42 0 min

  1. Langenthal17:50
  2. Lotzwil17:54
  3. Lindenholz18:00
  4. Rohrbach18:04
  5. Zell LU18:20
  6. Menznau18:35
  7. Wolhusen18:42

Next service: tomorrow 17:50 from Langenthal · Sun 8 Nov

Next departure 17:50 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%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 0 no data
Typical delay
−1min
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

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

  • Early 14% · 5
  • On time 86% · 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=6
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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
17:501 min early 1 min early
17:52≈ 1 min early ≈ 1 min early
17:54≈ 1 min early ≈ 1 min early
17:55≈ 1 min early ≈ 1 min early
17:59≈ 1 min early ≈ 1 min early
18:00≈ 1 min early ≈ 1 min early
18:01≈ 1 min early ≈ 1 min early
18:04≈ 1 min early ≈ on time
18:10 / 18:13≈ 1 min early ≈ on time
18:20≈ 1 min early ≈ on time
18:24≈ 1 min early ≈ on time
18:29 / 18:30≈ 1 min early ≈ on time
18:35≈ 1 min early ≈ on time
18:38≈ 1 min early ≈ on time
18:421 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
Sat 7 NovWolhusen 18:430 min—
Fri 6 NovWolhusen 18:430 min—
Thu 5 NovWolhusen 18:420 min—
Wed 4 NovWolhusen 18:42−1 min—
Tue 3 NovWolhusen 18:430 min—
Mon 2 NovWolhusen 18:43−1 min—
Sun 1 NovWolhusen 18:430 min—
Sat 31 OctWolhusen 18:430 min—
Fri 30 OctWolhusen 18:42−1 min—
Thu 29 OctWolhusen 18:430 min—
Wed 28 OctWolhusen 18:43−1 min—
Tue 27 OctWolhusen 18:42−1 min—
Mon 26 OctWolhusen 18:430 min—
Sun 25 OctWolhusen 18:420 min—
Sat 24 OctWolhusen 18:42−1 min—
Fri 23 OctWolhusen 18:42−1 min—
Thu 22 OctWolhusen 18:430 min—
Wed 21 OctWolhusen 18:420 min—
Tue 20 OctWolhusen 18:43−1 min—
Mon 19 OctWolhusen 18:42−1 min—
Sun 18 OctWolhusen 18:42−1 min—
Sat 17 OctWolhusen 18:45+2 min+2 min
Fri 16 OctWolhusen 18:430 min—
Thu 15 OctWolhusen 18:42−1 min—
Wed 14 OctWolhusen 18:420 min—
Tue 13 OctWolhusen 18:42−1 min—
Mon 12 OctWolhusen 18:42−1 min—
Sun 11 OctWolhusen 18:41−2 min—
Sat 10 OctWolhusen 18:430 min—
Fri 9 OctWolhusen 18:430 min—