S22 26066 Balsthal – Oensingen

View line S22

Balsthal 17:32 → Oensingen 17:40 Daily 0 h 08 min · 4 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Oensingen at 17:40 0 min

  1. Balsthal17:32
  2. Thalbrücke17:34
  3. Klus17:36
  4. Oensingen17:40

Next service: tomorrow 17:32 from Balsthal · Sat 21 Nov

Next departure 17:32 tomorrow · Balsthal
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Oensingen, 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

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

  • Early 0% · 0
  • On time 100% · 48
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 48 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:32on time on time
17:34≈ on time ≈ on time
17:36≈ on time ≈ on time
17:40on time on time

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
Fri 20 NovOensingen 17:390 min—
Thu 19 NovOensingen 17:390 min—
Wed 18 NovOensingen 17:390 min—
Tue 17 NovOensingen 17:390 min—
Mon 16 NovOensingen 17:390 min—
Sun 15 NovOensingen 17:390 min—
Sat 14 NovOensingen 17:390 min—
Fri 13 NovOensingen 17:390 min—
Thu 12 NovOensingen 17:390 min—
Wed 11 NovOensingen 17:390 min—
Tue 10 NovOensingen 17:390 min—
Mon 9 NovOensingen 17:390 min—
Sun 8 NovOensingen 17:390 min—
Sat 7 NovOensingen 17:390 min—
Fri 6 NovOensingen 17:390 min—
Thu 5 NovOensingen 17:390 min—
Wed 4 NovOensingen 17:390 min—
Tue 3 NovOensingen 17:390 min—
Mon 2 NovOensingen 17:390 min—
Sun 1 NovOensingen 17:410 min—
Sat 31 OctOensingen 17:410 min—
Fri 30 OctOensingen 17:410 min—
Thu 29 OctOensingen 17:410 min—
Wed 28 OctOensingen 17:410 min—
Tue 27 OctOensingen 17:410 min—
Mon 26 OctOensingen 17:410 min—
Sun 25 OctOensingen 17:410 min—
Sat 24 OctOensingen 17:410 min—
Fri 23 OctOensingen 17:410 min—
Thu 22 OctOensingen 17:410 min—