S20 7663 Grenchen Süd – Olten

View line S20

Grenchen Süd 08:36 → Olten 09:24 Daily 0 h 48 min · 18 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Olten at 09:24 0 min

  1. Grenchen Süd08:36
  2. Bellach08:43
  3. Solothurn08:49
  4. Wangen an der Aare08:58
  5. Oensingen09:06
  6. Hägendorf09:15
  7. Olten09:24

Next service: tomorrow 08:36 from Grenchen Süd · Fri 6 Nov

Next departure 08:36 tomorrow · Grenchen Süd
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
63/66 runs under 3 min
RT coverage: 66 full · 0 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 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

  • Wed 16 Sept Max en route +9 min · last fix heading to Hägendorf +9 min
  • Wed 9 Sept Max en route +16 min · last fix heading to Olten Hammer +3 min
  • Wed 23 Sept Max en route +3 min · last fix heading to Dietikon +3 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 92% · 61
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 73% W n=11
  • 100% T n=8
  • 100% F n=8
  • 100% S n=12
  • 100% S n=8

Stops and timetable

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

Last 90 days, 66 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:36on time on time
08:38≈ on time ≈ on time
08:41≈ on time ≈ on time
08:43≈ on time ≈ on time
08:45≈ on time ≈ on time
08:47≈ on time ≈ on time
08:49 / 08:50≈ on time ≈ on time
08:52 / 08:53≈ on time ≈ +1 min
08:55≈ on time ≈ +1 min
08:58≈ on time ≈ +1 min
09:03≈ on time ≈ +1 min
09:06≈ on time ≈ +1 min
09:10≈ on time ≈ +1 min
09:12≈ on time ≈ +1 min
09:15≈ on time ≈ +1 min
09:18≈ on time ≈ +2 min
09:21≈ on time ≈ +2 min
09:24on 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 NovOlten 09:240 min—
Wed 4 NovDietikon 20:29+1 min—
Tue 3 NovDietikon 20:28−1 min—
Mon 2 NovDietikon 20:29+1 min+1 min
Sun 1 NovDietikon 20:29+1 min—
Sat 31 OctDietikon 20:29+1 min—
Fri 30 OctDietikon 20:29+1 min+1 min
Thu 29 OctDietikon 20:29+1 min—
Wed 28 OctDietikon 20:29+1 min+1 min
Tue 27 OctDietikon 20:27−1 min—
Mon 26 OctDietikon 20:290 min+1 min
Sun 25 OctDietikon 20:30+1 min+1 min
Sat 24 OctDietikon 20:30+2 min+2 min
Fri 23 OctDietikon 20:30+2 min+2 min
Thu 22 OctDietikon 20:270 min+3 min
Wed 21 OctDietikon 20:27−1 min—
Tue 20 OctDietikon 20:29+1 min—
Mon 19 OctDietikon 20:280 min—
Sun 18 OctDietikon 20:28−1 min—
Sat 17 OctDietikon 20:280 min+1 min
Fri 16 OctDietikon 20:280 min—
Thu 15 OctDietikon 20:280 min+2 min
Wed 14 OctDietikon 20:29+1 min+1 min
Tue 13 OctDietikon 20:28−1 min—
Mon 12 OctDietikon 20:29+1 min+1 min
Sun 11 OctDietikon 20:30+2 min+2 min
Sat 10 OctDietikon 20:28−1 min+3 min
Fri 9 OctDietikon 20:30+2 min+2 min
Thu 8 OctDietikon 20:28−1 min+1 min
Wed 7 OctDietikon 20:30+1 min+1 min