S20 7614 Olten – Oensingen

View line S20

Olten 10:11 → Oensingen 10:28 Daily 0 h 17 min · 7 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Grenchen Süd at 08:53 0 min

  1. Olten10:11
  2. Olten Hammer10:13
  3. Wangen bei Olten10:16
  4. Hägendorf10:17
  5. Egerkingen10:21
  6. Oberbuchsiten10:24
  7. Oensingen10:28

Next service: tomorrow 10:11 from Olten · Fri 6 Nov

Next departure 10:11 tomorrow · Olten
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 27 full · 3 partial · 0 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 59 full · 3 partial · 3 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 Oensingen, in minutes. One bar per run.

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

Worst days

  • Sun 13 Sept Max en route +16 min · last fix heading to Biel/Bienne +16 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Biel/Bienne +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Grenchen Süd +4 min

Distribution · 90 days

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

  • Early 8% · 5
  • On time 87% · 54
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=9
  • 90% W n=10
  • 100% T n=10
  • 88% F n=8
  • 100% S n=7
  • 90% S n=10

Stops and timetable

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

Last 90 days, 62 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
10:11on time on time
10:13≈ on time ≈ on time
10:16≈ on time ≈ on time
10:17 / 10:18≈ on time ≈ +1 min
10:21 / 10:22≈ on time ≈ +1 min
10:24≈ on time ≈ +2 min
10:28on 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 5 NovGrenchen Süd 08:53Partial coverage0 min—
Wed 4 NovGrenchen Süd 08:57Partial coverage+4 min+4 min
Tue 3 NovGrenchen Süd 08:53Partial coverage+1 min—
Mon 2 NovBiel/Bienne 09:09+1 min+2 min
Sun 1 NovBiel/Bienne 09:09+1 min+2 min
Sat 31 OctBiel/Bienne 09:09+1 min+2 min
Fri 30 OctBiel/Bienne 09:11+2 min+2 min
Thu 29 OctBiel/Bienne 09:090 min+2 min
Wed 28 OctBiel/Bienne 09:10+1 min+3 min
Tue 27 OctBiel/Bienne 09:11+1 min+1 min
Mon 26 OctSolothurn 11:01+1 min+1 min
Sun 25 OctBiel/Bienne 09:08−1 min—
Sat 24 OctBiel/Bienne 09:08−1 min—
Fri 23 OctBiel/Bienne 09:09+1 min+2 min
Thu 22 OctBiel/Bienne 09:090 min+2 min
Wed 21 OctBiel/Bienne 09:09+2 min+2 min
Tue 20 OctBiel/Bienne 09:11+1 min+1 min
Mon 19 OctBiel/Bienne 09:090 min—
Sun 18 OctBiel/Bienne 09:12+3 min+3 min
Sat 17 OctBiel/Bienne 09:100 min—
Fri 16 OctBiel/Bienne 09:10+2 min+2 min
Thu 15 OctBiel/Bienne 09:090 min+6 min
Wed 14 OctBiel/Bienne 09:11+2 min+2 min
Tue 13 OctBiel/Bienne 09:100 min—
Mon 12 OctBiel/Bienne 09:090 min—
Sun 11 OctBiel/Bienne 09:090 min—
Sat 10 OctBiel/Bienne 09:11+2 min+2 min
Fri 9 OctBiel/Bienne 09:15+5 min+5 min
Thu 8 OctBiel/Bienne 09:090 min—
Wed 7 OctBiel/Bienne 09:090 min+1 min