S7 21775 Langenthal → Wolhusen

View line S7

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

S7 21775 Langenthal–Wolhusen: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:07 (GMT+1).

✓ Today’s run finished

Today it reached Wolhusen at 20:42 0 min

  1. Langenthal19:50
  2. Gutenburg19:55
  3. Lindenholz20:00
  4. Huttwil20:10
  5. Zell LU20:20
  6. Menznau20:35
  7. Wolhusen20:42

Next service: tomorrow 19:50 from Langenthal · Mon 23 Nov

Next departure 19: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%
54/54 runs under 3 min
RT coverage: 54 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

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

  • Early 2% · 1
  • On time 98% · 53
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 54 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:501 min early 1 min early
19:52≈ 1 min early ≈ 1 min early
19:54≈ 1 min early ≈ on time
19:55≈ 1 min early ≈ on time
19:59≈ 1 min early ≈ on time
20:00≈ 1 min early ≈ on time
20:01≈ 1 min early ≈ on time
20:04≈ 1 min early ≈ on time
20:10 / 20:13≈ on time ≈ on time
20:18≈ on time ≈ on time
20:20≈ on time ≈ on time
20:24≈ on time ≈ +1 min
20:29 / 20:30≈ on time ≈ +1 min
20:35≈ on time ≈ +1 min
20:38≈ on time ≈ +1 min
20:42on time +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
Sun 22 NovWolhusen 20:440 min—
Sat 21 NovWolhusen 20:420 min—
Fri 20 NovWolhusen 20:44+2 min+2 min
Thu 19 NovWolhusen 20:430 min—
Wed 18 NovWolhusen 20:430 min—
Tue 17 NovWolhusen 20:430 min—
Mon 16 NovWolhusen 20:430 min—
Sun 15 NovWolhusen 20:430 min—
Sat 14 NovWolhusen 20:44+2 min+2 min
Fri 13 NovWolhusen 20:44+1 min—
Thu 12 NovWolhusen 20:44+1 min+1 min
Wed 11 NovWolhusen 20:44+2 min+2 min
Tue 10 NovWolhusen 20:420 min—
Mon 9 NovWolhusen 20:430 min—
Sun 8 NovWolhusen 20:430 min—
Sat 7 NovWolhusen 20:42−1 min—
Fri 6 NovWolhusen 20:420 min—
Thu 5 NovWolhusen 20:42−1 min—
Wed 4 NovWolhusen 20:440 min—
Tue 3 NovWolhusen 20:430 min—
Mon 2 NovWolhusen 20:42−1 min—
Sun 1 NovWolhusen 20:430 min—
Sat 31 OctWolhusen 20:42−1 min—
Fri 30 OctWolhusen 20:42−1 min—
Thu 29 OctWolhusen 20:430 min—
Wed 28 OctWolhusen 20:430 min—
Tue 27 OctWolhusen 20:42−1 min—
Mon 26 OctWolhusen 20:430 min—
Sun 25 OctWolhusen 20:420 min—
Sat 24 OctWolhusen 20:430 min—