S41 6423 Solothurn → Thun

View line S41

Solothurn 12:46 → Thun 14:19 Daily 1 h 33 min · 23 stops BLS

S41 6423 Solothurn–Thun: final delay under 3 min on 23 of its 23 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:38 (GMT+1).

Running now · updated 13:38

Position estimated from the timetable

Between Hasle-Rüegsau and Schafhausen i.E. No data

Estimated arrival at Thun 14:19 · 1 km/h

  1. Solothurn12:46
  2. Utzenstorf12:58
  3. Burgdorf Buchmatt13:07
  4. Hasle-Rüegsau13:34
  5. Schafhausen i.E.13:40
  6. Biglen13:51
  7. Thun14:19
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 40 full · 1 partial · 11 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 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

  • Tue 20 Oct Max en route +8 min · last fix heading to Thun +8 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 86% T n=7
  • 100% W n=8
  • 100% T n=1
  • 100% F n=7
  • 100% S n=7
  • 100% S n=9

Stops and timetable

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

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