S20 7683 Grenchen Süd – Olten

View line S20

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

✓ Today’s run finished

Today it reached Olten at 19:24 0 min

  1. Grenchen Süd18:36
  2. Bellach18:43
  3. Solothurn18:49
  4. Wangen an der Aare18:58
  5. Oensingen19:06
  6. Hägendorf19:15
  7. Olten19:24

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

Next departure 18:36 tomorrow · Grenchen Süd
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
62/64 runs under 3 min
RT coverage: 64 full · 0 partial · 0 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: +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

  • Fri 6 Nov Max en route +10 min · last fix heading to Olten +10 min
  • Wed 14 Oct Max en route +7 min · last fix heading to Olten +7 min

Distribution · 90 days

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

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

On-time by weekday

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

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