S20 30756 Olten – Solothurn

View line S20

Olten 00:38 → Solothurn 01:12 Fri, Sat, Sun 0 h 34 min · 12 stops SBB CFF FFS

It does not run today

Last recorded run: Sunday 18 October No data

On-time · 30 days
—
Too little data (0/3 runs with data)
RT coverage: 0 full · 0 partial · 3 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Solothurn, 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

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

  • Early 0% · 0
  • On time 100% · 9
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • — W n=0
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 9 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
00:38on time +1 min
00:40≈ on time ≈ +1 min
00:42 / 00:43≈ on time ≈ on time
00:45≈ on time ≈ +1 min
00:48 / 00:49≈ on time ≈ +1 min
00:51≈ on time ≈ +1 min
00:55≈ on time ≈ +1 min
00:57≈ on time ≈ +1 min
01:02 / 01:03≈ on time ≈ +1 min
01:05 / 01:06≈ on time ≈ +1 min
01:08≈ on time ≈ +1 min
01:12on 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
Sun 18 OctBiel/Bienne 06:39Partial coverageNo data—
Sat 17 OctBiel/Bienne 06:39Partial coverageNo data—
Fri 16 OctBiel/Bienne 06:39Partial coverageNo data—
Mon 14 SeptLangenthal 19:38No data—
Sun 13 SeptLangenthal 19:37−1 min—
Sat 12 SeptLangenthal 19:370 min—
Tue 8 SeptLangenthal 10:370 min—
Thu 3 SeptLangenthal 11:37+1 min+1 min
Sun 30 AugLangenthal 00:37+3 min+4 min
Sat 22 AugBellinzona 23:120 min+2 min
Fri 21 AugBellinzona 23:120 min+2 min
Mon 17 AugBellinzona 22:120 min+3 min
Sat 15 AugBellinzona 22:120 min—