S20 7729 Solothurn – Olten

View line S20

Solothurn 08:16 → Olten 08:50 Daily 0 h 34 min · 12 stops SBB CFF FFS

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: tomorrow 08:16 from Solothurn · Tue 10 Nov

Next departure 08:16 tomorrow · Solothurn
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%
51/51 runs under 3 min
RT coverage: 51 full · 0 partial · 0 no data
Typical delay
0min
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 Olten, 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=9
  • 100% T n=7
  • 100% F n=5
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 51 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
08:16on time on time
08:18 / 08:19≈ on time ≈ on time
08:21 / 08:22≈ on time ≈ on time
08:24≈ on time ≈ on time
08:29≈ on time ≈ +1 min
08:32≈ on time ≈ +1 min
08:35≈ on time ≈ +1 min
08:38≈ on time ≈ +1 min
08:41≈ on time ≈ +1 min
08:44≈ on time ≈ +1 min
08:46≈ on time ≈ +1 min
08:50on 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 8 NovOlten 16:490 min—
Sat 7 NovOlten 16:49−1 min—
Fri 6 NovOlten 16:52+1 min+1 min
Thu 5 NovOlten 16:52+1 min+1 min
Wed 4 NovOlten 16:52+1 min—
Tue 3 NovOlten 16:53+2 min+2 min
Mon 2 NovOlten 16:490 min—
Sun 1 NovOlten 16:500 min—
Sat 31 OctOlten 16:54+3 min+3 min
Fri 30 OctOlten 16:510 min—
Thu 29 OctOlten 16:52+1 min—
Wed 28 OctOlten 16:50−1 min—
Tue 27 OctOlten 16:52+1 min—
Mon 26 OctOlten 16:52+1 min+1 min
Sun 25 OctOlten 16:52+1 min+1 min
Sat 24 OctOlten 16:53+2 min+2 min
Fri 23 OctOlten 16:510 min—
Thu 22 OctOlten 16:52+1 min—
Wed 21 OctOlten 16:53+2 min+2 min
Tue 20 OctOlten 16:510 min—
Mon 19 OctOlten 16:52+1 min—
Sun 18 OctOlten 16:510 min—
Sat 17 OctOlten 16:510 min—
Fri 16 OctOlten 16:520 min—
Thu 15 OctOlten 16:52+1 min+1 min
Wed 14 OctOlten 16:50−1 min+1 min
Tue 13 OctOlten 16:53+2 min+2 min
Mon 12 OctOlten 16:510 min—
Sun 11 OctOlten 16:50−1 min—
Sat 10 OctOlten 16:54+2 min+2 min