S41 6431 Solothurn – Thun

View line S41

Solothurn 16:46 → Thun 18:19 Daily 1 h 33 min · 23 stops BLS

✓ Today’s run finished

Today it reached Thun at 18:22 +3 min

  1. Solothurn16:46
  2. Utzenstorf16:58
  3. Burgdorf Buchmatt17:07
  4. Hasle-Rüegsau17:34
  5. Biglen17:51
  6. Oberdiessbach18:05
  7. Thun18:19

Next service: tomorrow 16:46 from Solothurn · Sat 7 Nov

Next departure 16:46 tomorrow · Solothurn
On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
89%
33/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Thun, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 12 Oct Max en route +14 min · last fix heading to Steffisburg +14 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Thun +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Thun +4 min
  • Fri 6 Nov Max en route +3 min · last fix heading to Thun +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 33
  • 3–10 min 8% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 86% T n=7
  • 100% W n=5
  • 100% T n=5
  • 60% F n=5
  • 100% S n=4
  • 100% S n=6

Stops and timetable

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

Last 90 days, 37 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
16:46on time on time
16:50≈ on time ≈ on time
16:52≈ on time ≈ on time
16:55≈ on time ≈ on time
16:58 / 16:59≈ on time ≈ on time
17:02≈ on time ≈ +1 min
17:05≈ on time ≈ +1 min
17:07≈ on time ≈ +1 min
17:12 / 17:25≈ on time ≈ +1 min
17:28≈ on time ≈ +1 min
17:29≈ on time ≈ +1 min
17:34 / 17:38≈ on time ≈ +2 min
17:40≈ on time ≈ +2 min
17:43≈ on time ≈ +2 min
17:47≈ +1 min ≈ +2 min
17:51≈ +1 min ≈ +2 min
17:54≈ +1 min ≈ +2 min
17:59 / 18:00≈ +1 min ≈ +2 min
18:05≈ +1 min ≈ +3 min
18:11≈ +1 min ≈ +3 min
18:13≈ +1 min ≈ +3 min
18:15≈ +1 min ≈ +3 min
18:19+1 min +3 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 6 NovThun 18:23+3 min+3 min
Thu 5 NovThun 18:190 min—
Wed 4 NovThun 18:190 min—
Tue 3 NovThun 18:190 min—
Mon 2 NovThun 18:22+2 min+2 min
Sun 1 NovThun 18:190 min—
Sat 31 OctThun 18:22+2 min+2 min
Fri 30 OctThun 18:21+1 min—
Thu 29 OctThun 18:22+2 min+2 min
Wed 28 OctThun 18:23+2 min+2 min
Tue 27 OctThun 18:23+2 min+2 min
Mon 26 OctThun 18:21+1 min+1 min
Sun 25 OctThun 18:22+2 min+2 min
Sat 24 OctThun 18:200 min—
Fri 23 OctThun 18:24+4 min+4 min
Thu 22 OctThun 18:22+2 min+2 min
Wed 21 OctThun 18:21+1 min+1 min
Tue 20 OctThun 18:210 min—
Mon 19 OctThun 18:21+2 min+2 min
Sun 18 OctThun 18:190 min—
Sat 17 OctThun 18:200 min—
Fri 16 OctThun 18:210 min—
Thu 15 OctThun 18:21+1 min—
Wed 14 OctThun 18:190 min—
Tue 13 OctThun 18:200 min—
Mon 12 OctSteffisburg 18:28+14 min+14 min
Sun 11 OctThun 18:200 min—
Sat 10 OctThun 18:200 min—
Fri 9 OctThun 18:22+1 min+1 min
Thu 8 OctThun 18:23+3 min+3 min