S42 6640 Thun → Hasle-Rüegsau

View line S42

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

S42 6640 Thun–Hasle-Rüegsau: final delay under 3 min on 29 of its 29 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 00:47 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 22:10 from Thun · Sun 22 Nov

Next departure 22:10 today · Thun
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 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 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

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

  • Early 17% · 9
  • On time 83% · 45
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=7
  • 100% T n=7
  • 100% F n=8
  • 100% S n=8
  • 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
22:10on time +1 min
22:11≈ on time ≈ +1 min
22:14 / 22:15≈ on time ≈ +1 min
22:17≈ on time ≈ +1 min
22:19≈ on time ≈ +1 min
22:22≈ on time ≈ +1 min
22:25≈ on time ≈ +1 min
22:28≈ on time ≈ +1 min
22:32 / 22:35≈ on time ≈ +1 min
22:39≈ on time ≈ on time
22:43≈ on time ≈ on time
22:47≈ on time ≈ on time
22: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
Sat 21 NovHasle-Rüegsau 22:570 min—
Fri 20 NovHasle-Rüegsau 22:570 min—
Thu 19 NovHasle-Rüegsau 22:570 min—
Wed 18 NovHasle-Rüegsau 22:540 min—
Tue 17 NovHasle-Rüegsau 22:540 min—
Mon 16 NovHasle-Rüegsau 22:54−1 min—
Sun 15 NovHasle-Rüegsau 22:570 min—
Sat 14 NovHasle-Rüegsau 22:570 min+3 min
Fri 13 NovHasle-Rüegsau 22:58+1 min+1 min
Thu 12 NovHasle-Rüegsau 22:58+1 min—
Wed 11 NovHasle-Rüegsau 22:570 min—
Tue 10 NovHasle-Rüegsau 22:58+1 min—
Mon 9 NovHasle-Rüegsau 22:580 min—
Sun 8 NovHasle-Rüegsau 22:570 min—
Sat 7 NovHasle-Rüegsau 22:540 min—
Fri 6 NovHasle-Rüegsau 22:540 min—
Thu 5 NovHasle-Rüegsau 22:540 min—
Wed 4 NovHasle-Rüegsau 22:54−1 min—
Tue 3 NovHasle-Rüegsau 22:540 min—
Mon 2 NovHasle-Rüegsau 22:57−1 min—
Sun 1 NovHasle-Rüegsau 22:59+1 min+1 min
Sat 31 OctHasle-Rüegsau 22:570 min+2 min
Fri 30 OctHasle-Rüegsau 22:56−1 min—
Thu 29 OctHasle-Rüegsau 22:56−1 min—
Wed 28 OctHasle-Rüegsau 22:56−1 min—
Tue 27 OctHasle-Rüegsau 22:58+1 min—
Mon 26 OctHasle-Rüegsau 22:570 min—
Sun 25 OctHasle-Rüegsau 22:55−1 min—
Sat 24 OctHasle-Rüegsau 22:560 min—
Fri 23 OctHasle-Rüegsau 22:570 min—