S42 6610 Thun – Hasle-Rüegsau

View line S42

Thun 07:03 → Hasle-Rüegsau 07:56 Daily 0 h 53 min · 13 stops BLS

✓ Today’s run finished

Today it reached Hasle-Rüegsau at 07:56 −1 min

  1. Thun07:03
  2. Steffisburg07:06
  3. Heimberg07:10
  4. Oberdiessbach07:17
  5. Konolfingen07:24
  6. Biglen07:43
  7. Hasle-Rüegsau07:56

Next service: tomorrow 07:03 from Thun · Sat 14 Nov

Next departure 07:03 tomorrow · Thun
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%
43/43 runs under 3 min
RT coverage: 43 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 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

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

  • Early 12% · 5
  • On time 88% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=7
  • 100% T n=7
  • 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 (13 stops).

Last 90 days, 43 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
07:03on time on time
07:04≈ on time ≈ on time
07:06≈ on time ≈ on time
07:08≈ on time ≈ on time
07:10 / 07:11≈ on time ≈ on time
07:14≈ on time ≈ on time
07:17≈ on time ≈ on time
07:20≈ on time ≈ on time
07:24 / 07:35≈ on time ≈ +1 min
07:39≈ on time ≈ +1 min
07:43≈ on time ≈ +1 min
07:47≈ on time ≈ +1 min
07:56on 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
Fri 13 NovHasle-Rüegsau 07:57−1 min—
Thu 12 NovHasle-Rüegsau 07:570 min—
Wed 11 NovHasle-Rüegsau 07:58+1 min+1 min
Tue 10 NovHasle-Rüegsau 07:59+3 min+3 min
Mon 9 NovHasle-Rüegsau 07:570 min—
Sun 8 NovKonolfingen 07:24−1 min—
Sat 7 NovHasle-Rüegsau 07:540 min—
Fri 6 NovHasle-Rüegsau 07:58+1 min+1 min
Thu 5 NovHasle-Rüegsau 07:54−1 min—
Wed 4 NovHasle-Rüegsau 07:540 min—
Tue 3 NovHasle-Rüegsau 07:58+1 min—
Mon 2 NovHasle-Rüegsau 07:580 min—
Sun 1 NovKonolfingen 07:23−1 min—
Sat 31 OctHasle-Rüegsau 07:570 min—
Fri 30 OctHasle-Rüegsau 07:56−1 min—
Thu 29 OctHasle-Rüegsau 07:570 min—
Wed 28 OctHasle-Rüegsau 07:58+1 min—
Tue 27 OctHasle-Rüegsau 07:59+2 min+2 min
Mon 26 OctHasle-Rüegsau 07:57−1 min—
Sun 25 OctKonolfingen 07:23−2 min—
Sat 24 OctHasle-Rüegsau 07:56−1 min—
Fri 23 OctHasle-Rüegsau 07:56−1 min—
Thu 22 OctHasle-Rüegsau 07:570 min—
Wed 21 OctHasle-Rüegsau 07:58+1 min—
Tue 20 OctHasle-Rüegsau 07:580 min—
Mon 19 OctHasle-Rüegsau 07:58+1 min+1 min
Sun 18 OctKonolfingen 07:23−2 min—
Sat 17 OctHasle-Rüegsau 07:570 min—
Fri 16 OctHasle-Rüegsau 07:58+2 min+2 min
Thu 15 OctHasle-Rüegsau 07:58+1 min—