S42 6636 Thun – Hasle-Rüegsau

View line S42

Thun 20:10 → Hasle-Rüegsau 20:56 Daily 0 h 46 min · 13 stops BLS

✓ Today’s run finished

Today it reached Hasle-Rüegsau at 20:56 0 min

  1. Thun20:10
  2. Steffisburg20:14
  3. Heimberg20:19
  4. Oberdiessbach20:25
  5. Konolfingen20:32
  6. Biglen20:43
  7. Hasle-Rüegsau20:56

Next service: tomorrow 20:10 from Thun · Sat 21 Nov

Next departure 20:10 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
98%
53/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
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

Worst days

  • Wed 23 Sept Max en route +4 min · last fix heading to Areuse Littorail +4 min

Distribution · 90 days

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

  • Early 17% · 9
  • On time 81% · 44
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
20:10on time +1 min
20:11≈ on time ≈ +1 min
20:14 / 20:15≈ on time ≈ +1 min
20:17≈ on time ≈ +1 min
20:19≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:25≈ on time ≈ +1 min
20:28≈ on time ≈ on time
20:32 / 20:35≈ on time ≈ on time
20:39≈ on time ≈ on time
20:43≈ on time ≈ on time
20:47≈ on time ≈ on time
20:56on time 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
Fri 20 NovHasle-Rüegsau 20:570 min—
Thu 19 NovHasle-Rüegsau 20:540 min—
Wed 18 NovHasle-Rüegsau 20:58+1 min+1 min
Tue 17 NovHasle-Rüegsau 20:570 min—
Mon 16 NovHasle-Rüegsau 20:570 min—
Sun 15 NovHasle-Rüegsau 20:570 min—
Sat 14 NovHasle-Rüegsau 20:550 min—
Fri 13 NovHasle-Rüegsau 20:540 min—
Thu 12 NovHasle-Rüegsau 20:550 min—
Wed 11 NovHasle-Rüegsau 20:540 min—
Tue 10 NovHasle-Rüegsau 20:540 min—
Mon 9 NovHasle-Rüegsau 20:530 min—
Sun 8 NovHasle-Rüegsau 20:54−1 min—
Sat 7 NovHasle-Rüegsau 20:570 min—
Fri 6 NovHasle-Rüegsau 20:540 min—
Thu 5 NovHasle-Rüegsau 20:54−1 min—
Wed 4 NovHasle-Rüegsau 20:57−1 min—
Tue 3 NovHasle-Rüegsau 20:57−1 min—
Mon 2 NovHasle-Rüegsau 20:57−1 min—
Sun 1 NovHasle-Rüegsau 20:57−1 min—
Sat 31 OctHasle-Rüegsau 20:56−1 min—
Fri 30 OctHasle-Rüegsau 20:570 min—
Thu 29 OctHasle-Rüegsau 20:570 min—
Wed 28 OctHasle-Rüegsau 20:57−1 min—
Tue 27 OctHasle-Rüegsau 20:570 min—
Mon 26 OctHasle-Rüegsau 20:570 min—
Sun 25 OctHasle-Rüegsau 20:56−1 min—
Sat 24 OctHasle-Rüegsau 20:55−2 min—
Fri 23 OctHasle-Rüegsau 20:570 min—
Thu 22 OctHasle-Rüegsau 20:56−1 min—