S20 7719 Solothurn – Olten

View line S20

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

Running now · updated 11:40

Position estimated from the timetable

Between Egerkingen and Hägendorf No data

Estimated arrival at Olten 11:50 · 76 km/h

  1. Solothurn11:16
  2. Deitingen11:21
  3. Niederbipp11:29
  4. Oberbuchsiten11:35
  5. Egerkingen11:38
  6. Hägendorf11:41
  7. Olten11:50
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 10 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

Worst days

  • Tue 20 Oct Max en route +4 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 83% T n=6
  • 100% W n=6
  • 100% T n=1
  • 100% F n=5
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 33 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
11:16on time on timePassed
11:18 / 11:19≈ on time ≈ on timePassed
11:21 / 11:22≈ on time ≈ on timePassed
11:24≈ on time ≈ +1 minPassed
11:29≈ on time ≈ +1 minPassed
11:32≈ on time ≈ +1 minPassed
11:35≈ on time ≈ +1 minPassed
11:38≈ on time ≈ +1 minPassed
11:41≈ on time ≈ +1 minNext
11:44≈ on time ≈ +2 min
11:46≈ on time ≈ +2 min
11: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
Thu 12 NovHägendorf 11:39Partial coverageNo data—
Wed 11 NovOlten 11:49−1 min—
Tue 10 NovOlten 11:53+1 min+1 min
Mon 9 NovOlten 11:49No data—
Sun 8 NovOlten 11:52+1 min—
Sat 7 NovOensingen 11:320 min—
Fri 6 NovOensingen 11:330 min—
Thu 5 NovOensingen 11:33No data—
Wed 4 NovOensingen 11:34+1 min—
Tue 3 NovOensingen 11:34+2 min+2 min
Mon 2 NovOlten 11:49No data—
Sun 1 NovOlten 11:510 min—
Sat 31 OctOlten 11:510 min—
Fri 30 OctOlten 11:52+1 min—
Thu 29 OctOlten 11:51No data—
Wed 28 OctOlten 11:52+1 min—
Tue 27 OctOlten 11:520 min—
Mon 26 OctOlten 11:52No data—
Sun 25 OctOlten 11:51+1 min—
Sat 24 OctOlten 11:54+3 min+3 min
Fri 23 OctOlten 11:53+2 min+2 min
Thu 22 OctOlten 11:51No data—
Wed 21 OctOlten 11:52+1 min—
Tue 20 OctOlten 11:55+4 min+4 min
Mon 19 OctOlten 11:51No data—
Sun 18 OctOlten 11:520 min—
Sat 17 OctOlten 11:510 min—
Fri 16 OctOlten 11:510 min—
Thu 15 OctOlten 11:51No data—
Wed 14 OctOlten 11:510 min—