S20 7706 Olten – Lommiswil

View line S20

Olten 18:11 → Lommiswil 18:54 Daily 0 h 43 min · 14 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Langendorf at 05:49 0 min

  1. Olten18:11
  2. Wangen bei Olten18:16
  3. Egerkingen18:21
  4. Niederbipp18:30
  5. Deitingen18:38
  6. Langendorf18:51
  7. Lommiswil18:54

Next service: tomorrow 18:11 from Olten · Tue 10 Nov

Next departure 18:11 tomorrow · Olten
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 26 full · 3 partial · 1 no data
On-time · 90 days
100%
65/65 runs under 3 min
RT coverage: 62 full · 3 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Lommiswil, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 2% · 1
  • On time 98% · 64
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=7
  • 100% W n=8
  • 100% T n=7
  • 100% F n=11
  • 100% S n=10
  • 100% S n=11

Stops and timetable

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

Last 90 days, 65 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:11on time +1 min
18:13≈ on time ≈ on time
18:16≈ on time ≈ on time
18:17 / 18:18≈ on time ≈ on time
18:21 / 18:22≈ on time ≈ on time
18:24≈ on time ≈ on time
18:28≈ on time ≈ +1 min
18:30≈ on time ≈ +1 min
18:35 / 18:36≈ on time ≈ +1 min
18:38≈ on time ≈ +1 min
18:45 / 18:46≈ on time ≈ +1 min
18:47 / 18:48≈ on time ≈ +1 min
18:51≈ on time ≈ +1 min
18:54on time +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 NovLangendorf 05:49Partial coverage0 min—
Sun 8 NovLangendorf 05:490 min—
Sat 7 NovLangendorf 05:52Partial coverage0 min—
Fri 6 NovLangendorf 05:52Partial coverage0 min—
Thu 5 NovLangendorf 05:520 min—
Wed 4 NovLangendorf 05:520 min—
Tue 3 NovLangendorf 05:52No data—
Mon 2 NovLangendorf 05:520 min—
Sun 1 NovLangendorf 05:51−1 min—
Sat 31 OctLangendorf 05:51−1 min—
Fri 30 OctLangendorf 05:520 min—
Thu 29 OctLangendorf 05:53+1 min+1 min
Wed 28 OctLangendorf 05:520 min—
Tue 27 OctLangendorf 05:520 min—
Mon 26 OctLangendorf 05:510 min—
Sun 25 OctLangendorf 05:51−1 min—
Sat 24 OctLangendorf 05:51−1 min—
Fri 23 OctLangendorf 05:54+2 min+2 min
Thu 22 OctLangendorf 05:520 min—
Wed 21 OctLangendorf 05:53+1 min—
Tue 20 OctLangendorf 05:510 min—
Mon 19 OctLangendorf 05:53+1 min—
Sun 18 OctLangendorf 05:54+1 min+1 min
Sat 17 OctLangendorf 05:520 min—
Fri 16 OctLangendorf 05:54+2 min+2 min
Thu 15 OctLangendorf 05:520 min—
Wed 14 OctLangendorf 05:51−1 min—
Tue 13 OctLangendorf 05:520 min—
Mon 12 OctLangendorf 05:510 min—
Sun 11 OctLangendorf 05:53+1 min—