S6 22617 Langnau i.E. – Wolhusen
Alerts for train 22617
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S6.
✓ Today’s run finished
Today it reached Wolhusen at 06:14 0 min
- Langnau i.E.05:37
- Trubschachen05:43
- Escholzmatt05:51
- Schüpfheim05:58
- Hasle LU06:03
- Entlebuch06:05
- Wolhusen06:14
Next service: tomorrow 05:37 from Langnau i.E. · Sun 8 Nov
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
- Sat 22 Aug Max en route +23 min · last fix heading to Wolhusen +23 min
- Sat 5 Sept Max en route +7 min · last fix heading to Luzern +7 min
- Tue 13 Oct Max en route +3 min · last fix heading to Wolhusen +3 min
- Fri 25 Sept Max en route +14 min · last fix heading to Wolhusen +3 min
- Fri 6 Nov Max en route +3 min · last fix heading to Wolhusen +3 min
Distribution · 90 days
48 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 6% · 3
- On time 83% · 40
- 3–10 min 8% · 4
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 80% T n=5
- 100% W n=8
- 100% T n=8
- 71% F n=7
- 71% S n=7
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 48 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 05:37 | on time | +1 min | |
| 05:43 / 05:44 | ≈ on time | ≈ +1 min | |
| 05:51 | ≈ on time | ≈ +1 min | |
| 05:58 / 05:59 | ≈ on time | ≈ +2 min | |
| 06:03 | ≈ +1 min | ≈ +2 min | |
| 06:05 | ≈ +1 min | ≈ +2 min | |
| 06:14 | +1 min | +3 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Wolhusen 06:14 | 0 min | — |
| Fri 6 Nov | Wolhusen 06:19 | +3 min | +3 min |
| Thu 5 Nov | Wolhusen 06:14 | +1 min | — |
| Wed 4 Nov | Wolhusen 06:14 | 0 min | — |
| Tue 3 Nov | Wolhusen 06:14 | 0 min | — |
| Mon 2 Nov | Wolhusen 06:17 | +2 min | +2 min |
| Sun 1 Nov | Wolhusen 06:15 | 0 min | — |
| Sat 31 Oct | Wolhusen 06:15 | 0 min | — |
| Fri 30 Oct | Wolhusen 06:15 | 0 min | — |
| Thu 29 Oct | Wolhusen 06:15 | 0 min | — |
| Wed 28 Oct | Wolhusen 06:16 | +1 min | +1 min |
| Tue 27 Oct | Wolhusen 06:16 | +1 min | — |
| Mon 26 Oct | Wolhusen 06:17 | +1 min | — |
| Sun 25 Oct | Wolhusen 06:15 | 0 min | — |
| Sat 24 Oct | Wolhusen 06:16 | +1 min | +1 min |
| Fri 23 Oct | Wolhusen 06:15 | 0 min | — |
| Thu 22 Oct | Wolhusen 06:15 | 0 min | — |
| Wed 21 Oct | Wolhusen 06:18 | +3 min | +3 min |
| Tue 20 Oct | Wolhusen 06:18 | +3 min | +3 min |
| Mon 19 Oct | Wolhusen 06:15 | 0 min | — |
| Sun 18 Oct | Wolhusen 06:16 | 0 min | — |
| Sat 17 Oct | Wolhusen 06:15 | 0 min | — |
| Fri 16 Oct | Wolhusen 06:16 | +1 min | +1 min |
| Thu 15 Oct | Wolhusen 06:17 | +2 min | +2 min |
| Wed 14 Oct | Wolhusen 06:17 | +1 min | +1 min |
| Tue 13 Oct | Wolhusen 06:18 | +3 min | +3 min |
| Mon 12 Oct | Wolhusen 06:17 | +2 min | +2 min |
| Sun 11 Oct | Wolhusen 06:15 | 0 min | — |
| Sat 10 Oct | Wolhusen 06:16 | +1 min | — |
| Fri 9 Oct | Wolhusen 06:16 | +1 min | +1 min |