S20 7735 Langendorf → Olten

View line S20

Langendorf 19:09 → Olten 19:50 Daily 0 h 41 min · 13 stops SBB CFF FFS

S20 7735 Langendorf–Olten: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 20:10 (GMT+1).

✓ Today’s run finished

Today it reached Olten at 19:50 0 min

  1. Langendorf19:09
  2. Solothurn19:14
  3. Deitingen19:21
  4. Niederbipp19:29
  5. Oberbuchsiten19:35
  6. Hägendorf19:41
  7. Olten19:50

Next service: tomorrow 19:09 from Langendorf · Mon 23 Nov

Next departure 19:09 tomorrow · Langendorf
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
56/58 runs under 3 min
RT coverage: 58 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

  • Thu 8 Oct Max en route +6 min · last fix heading to Olten +6 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 91% · 53
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=7
  • 86% T n=7
  • 90% F n=10
  • 100% S n=10
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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
19:09on time on time
19:11≈ on time ≈ on time
19:14 / 19:16≈ on time ≈ on time
19:18 / 19:19≈ on time ≈ on time
19:21 / 19:22≈ on time ≈ +1 min
19:24≈ on time ≈ +1 min
19:29≈ on time ≈ +1 min
19:32≈ on time ≈ +1 min
19:35≈ on time ≈ +1 min
19:38≈ on time ≈ +1 min
19:41≈ on time ≈ +1 min
19:44≈ on time ≈ +1 min
19:50on 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
Sun 22 NovOlten 19:520 min—
Sat 21 NovOlten 19:52+2 min+2 min
Fri 20 NovOlten 19:490 min—
Thu 19 NovOlten 19:490 min—
Wed 18 NovOlten 19:49−1 min—
Tue 17 NovOlten 19:490 min—
Mon 16 NovOlten 19:490 min—
Sun 15 NovOlten 19:52+1 min+1 min
Sat 14 NovOlten 19:49−1 min—
Fri 13 NovOlten 19:490 min—
Thu 12 NovOlten 19:500 min—
Wed 11 NovOlten 19:490 min—
Tue 10 NovOlten 19:49−1 min—
Mon 9 NovOlten 19:53+2 min+4 min
Sun 8 NovOlten 19:490 min—
Sat 7 NovOlten 19:49−1 min—
Fri 6 NovOlten 19:53+2 min+2 min
Thu 5 NovOlten 19:53+2 min+2 min
Wed 4 NovOlten 19:49−1 min—
Tue 3 NovOlten 19:490 min—
Mon 2 NovOlten 19:490 min—
Sun 1 NovOlten 19:490 min—
Sat 31 OctOlten 19:510 min—
Fri 30 OctOlten 19:50−1 min—
Thu 29 OctOlten 19:510 min—
Wed 28 OctOlten 19:510 min—
Tue 27 OctOlten 19:510 min—
Mon 26 OctOlten 19:51−1 min—
Sun 25 OctOlten 19:53+3 min+3 min
Sat 24 OctOlten 19:510 min—