S20 7681 Grenchen Süd – Olten

View line S20

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

✓ Today’s run finished

Today it reached Olten at 18:25 +1 min

  1. Grenchen Süd17:36
  2. Bellach17:43
  3. Solothurn17:49
  4. Wangen an der Aare17:58
  5. Oensingen18:06
  6. Hägendorf18:15
  7. Olten18:24

Next service: tomorrow 17:36 from Grenchen Süd · Wed 18 Nov

Next departure 17:36 tomorrow · Grenchen Süd
On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
61/64 runs under 3 min
RT coverage: 64 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 30 Oct Max en route +6 min · last fix heading to Olten +6 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Olten +3 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 91% M n=11
  • 100% T n=10
  • 100% W n=8
  • 89% T n=9
  • 90% F n=10
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

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