S42 6606 Thun – Hasle-Rüegsau

View line S42

Thun 05:03 → Hasle-Rüegsau 05:55 Mon, Tue, Wed, Thu, Fri, Sat 0 h 52 min · 15 stops BLS

✓ Today’s run finished

Today it reached Hasle-Rüegsau at 05:55 −1 min

  1. Thun05:03
  2. Steffisburg05:06
  3. Brenzikofen05:14
  4. Stalden i.E.05:20
  5. Grosshöchstetten05:36
  6. Bigenthal05:46
  7. Hasle-Rüegsau05:55

Next service: Monday 05:03 from Thun · Mon 9 Nov

Next departure 05:03 Monday · Thun
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 full · 0 partial · 0 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 Hasle-Rüegsau, 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

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

  • Early 42% · 13
  • On time 58% · 18
  • 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=6
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 31 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
05:03on time on time
05:04≈ on time ≈ on time
05:06≈ on time ≈ on time
05:08≈ on time ≈ on time
05:10 / 05:11≈ on time ≈ on time
05:14≈ on time ≈ on time
05:17≈ on time ≈ on time
05:20≈ on time ≈ on time
05:24 / 05:32≈ on time ≈ on time
05:36≈ on time ≈ on time
05:40≈ 1 min early ≈ on time
05:44≈ 1 min early ≈ on time
05:46≈ 1 min early ≈ on time
05:49≈ 1 min early ≈ on time
05:551 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 NovHasle-Rüegsau 05:54−1 min—
Fri 6 NovHasle-Rüegsau 05:540 min—
Thu 5 NovHasle-Rüegsau 05:540 min—
Wed 4 NovHasle-Rüegsau 05:54−2 min—
Tue 3 NovHasle-Rüegsau 05:540 min—
Mon 2 NovHasle-Rüegsau 05:570 min—
Sat 31 OctHasle-Rüegsau 05:53−3 min—
Fri 30 OctHasle-Rüegsau 05:55−1 min—
Thu 29 OctHasle-Rüegsau 05:54−2 min—
Wed 28 OctHasle-Rüegsau 05:560 min—
Tue 27 OctHasle-Rüegsau 05:55−1 min—
Mon 26 OctHasle-Rüegsau 05:55−1 min—
Sat 24 OctHasle-Rüegsau 05:54−2 min—
Fri 23 OctHasle-Rüegsau 05:560 min—
Thu 22 OctHasle-Rüegsau 05:55−1 min—
Wed 21 OctHasle-Rüegsau 05:55−1 min—
Tue 20 OctHasle-Rüegsau 05:54−2 min—
Mon 19 OctHasle-Rüegsau 05:560 min—
Sat 17 OctHasle-Rüegsau 05:53−3 min—
Fri 16 OctHasle-Rüegsau 05:560 min—
Thu 15 OctHasle-Rüegsau 05:57+1 min—
Wed 14 OctHasle-Rüegsau 05:57+1 min+1 min
Tue 13 OctHasle-Rüegsau 05:54−2 min—
Mon 12 OctHasle-Rüegsau 05:560 min—
Sat 10 OctHasle-Rüegsau 05:54−3 min—
Fri 9 OctHasle-Rüegsau 05:55−1 min—
Thu 8 OctHasle-Rüegsau 05:55−1 min—
Wed 7 OctHasle-Rüegsau 05:55−1 min—
Tue 6 OctHasle-Rüegsau 05:560 min—
Mon 5 OctHasle-Rüegsau 05:560 min—