S42 6605 Konolfingen – Hasle-Rüegsau

View line S42

Konolfingen 06:35 → Hasle-Rüegsau 06:56 Mon, Tue, Wed, Thu, Fri, Sat 0 h 21 min · 7 stops BLS

✓ Today’s run finished

Today, last fix heading to Thun at 05:59 +1 min

  1. Konolfingen06:35
  2. Grosshöchstetten06:39
  3. Biglen06:43
  4. Walkringen06:47
  5. Bigenthal06:49
  6. Schafhausen i.E.06:52
  7. Hasle-Rüegsau06:56

Next service: tomorrow 06:35 from Konolfingen · Fri 20 Nov

Next departure 06:35 tomorrow · Konolfingen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 17 full · 9 partial · 2 no data
On-time · 90 days
98%
54/55 runs under 3 min
RT coverage: 45 full · 10 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 8 Sept Max en route +33 min · last fix heading to Thun +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 54
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 92% T n=12
  • 100% W n=12
  • 100% T n=12
  • 100% F n=6
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 55 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
06:35on time on time
06:39≈ on time ≈ on time
06:43≈ on time ≈ +1 min
06:47≈ on time ≈ +1 min
06:49≈ on time ≈ +1 min
06:52≈ on time ≈ +2 min
06:56on time +2 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
Thu 19 NovThun 05:59Partial coverage+1 min—
Wed 18 NovThun 05:58Partial coverage0 min—
Tue 17 NovThun 05:58Partial coverage0 min—
Mon 16 NovThun 05:58+1 min—
Sun 15 NovLyon Perrache 10:09No data—
Sat 14 NovLyon Perrache 10:090 min—
Fri 13 NovThun 05:590 min—
Thu 12 NovThun 05:58Partial coverage+1 min—
Wed 11 NovThun 05:59Partial coverage+1 min+1 min
Tue 10 NovThun 05:59Partial coverage+1 min+1 min
Mon 9 NovThun 05:59+1 min—
Sun 8 NovLyon Perrache 10:09No data—
Sat 7 NovLyon Perrache 10:090 min—
Fri 6 NovThun 05:580 min—
Thu 5 NovThun 05:59Partial coverage+1 min—
Wed 4 NovThun 05:58Partial coverage0 min—
Tue 3 NovThun 05:59Partial coverage+1 min+1 min
Mon 2 NovThun 05:590 min—
Sat 31 OctThun 05:580 min—
Fri 30 OctThun 05:59+1 min—
Thu 29 OctThun 05:57−1 min—
Wed 28 OctThun 05:59+1 min+1 min
Tue 27 OctThun 05:59+1 min—
Mon 26 OctThun 06:00+2 min+2 min
Sat 24 OctThun 06:00+2 min+2 min
Fri 23 OctThun 05:580 min—
Thu 22 OctThun 05:59+1 min—
Wed 21 OctThun 06:00+2 min+2 min
Tue 20 OctThun 05:580 min—
Mon 19 OctThun 05:59+1 min—