S20 7662 Olten – Oberdorf SO

View line S20

Olten 17:08 → Oberdorf SO 17:58 Daily 0 h 50 min · 15 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Grenchen Süd at 09:24 +1 min

  1. Olten17:08
  2. Wangen bei Olten17:13
  3. Oberbuchsiten17:24
  4. Niederbipp17:30
  5. Deitingen17:38
  6. Solothurn West17:47
  7. Oberdorf SO17:58

Next service: tomorrow 17:08 from Olten · Tue 10 Nov

Next departure 17:08 tomorrow · Olten
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
96%
72/75 runs under 3 min
RT coverage: 74 full · 1 partial · 2 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Oberdorf SO, in minutes. One bar per run.

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

Worst days

  • Wed 9 Sept Max en route +4 min · last fix heading to Biel/Bienne +4 min
  • Fri 28 Aug Max en route +3 min · last fix heading to Wohlen Oberdorf +3 min
  • Tue 1 Sept Max en route +3 min · last fix heading to Biel/Bienne +3 min

Distribution · 90 days

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

  • Early 40% · 30
  • On time 56% · 42
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 92% T n=12
  • 92% W n=12
  • 100% T n=11
  • 89% F n=9
  • 100% S n=12
  • 100% S n=11

Stops and timetable

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

Last 90 days, 75 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
17:08on time +1 min
17:10≈ on time ≈ +1 min
17:13≈ on time ≈ +1 min
17:17 / 17:18≈ on time ≈ +1 min
17:21 / 17:22≈ on time ≈ +1 min
17:24≈ on time ≈ +1 min
17:28≈ on time ≈ +1 min
17:30≈ on time ≈ +1 min
17:35 / 17:36≈ on time ≈ +1 min
17:38≈ on time ≈ +1 min
17:41≈ on time ≈ +1 min
17:45 / 17:46≈ on time ≈ +1 min
17:47 / 17:48≈ on time ≈ +1 min
17:51≈ 1 min early ≈ +1 min
17:581 min early +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
Mon 9 NovGrenchen Süd 09:24Partial coverage+1 min+1 min
Sun 8 NovWohlen AG 20:08−2 min+1 min
Sat 7 NovWohlen AG 20:07−2 min+3 min
Fri 6 NovWohlen AG 20:08−1 min+4 min
Thu 5 NovWohlen AG 20:040 min+1 min
Wed 4 NovWohlen AG 20:070 min+1 min
Tue 3 NovWohlen AG 20:070 min—
Mon 2 NovWohlen AG 20:07−2 min+3 min
Sun 1 NovWohlen AG 20:08−2 min+1 min
Sat 31 OctWohlen AG 20:060 min+1 min
Fri 30 OctWohlen AG 20:07−2 min+1 min
Thu 29 OctWohlen AG 20:060 min—
Wed 28 OctWohlen AG 20:09−1 min+2 min
Tue 27 OctWohlen AG 20:08−1 min+3 min
Mon 26 OctWohlen AG 20:07−3 min+1 min
Sun 25 OctWohlen AG 20:07−2 min—
Sat 24 OctWohlen AG 20:08−1 min+5 min
Fri 23 OctWohlen AG 20:08−1 min+3 min
Thu 22 OctWohlen AG 20:09−1 min—
Wed 21 OctWohlen AG 20:08+2 min+2 min
Tue 20 OctWohlen AG 20:08−1 min+1 min
Mon 19 OctWohlen AG 20:06−2 min+2 min
Sun 18 OctWohlen AG 20:07−2 min—
Sat 17 OctWohlen AG 20:08−1 min—
Fri 16 OctWohlen AG 20:08−2 min—
Thu 15 OctWohlen AG 20:07−2 min—
Wed 14 OctWohlen AG 20:07−2 min+3 min
Tue 13 OctWohlen AG 20:08−1 min+1 min
Mon 12 OctWohlen AG 20:08−1 min—
Sun 11 OctWohlen AG 20:07−2 min—