S22 26065 Oensingen – Balsthal

View line S22

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

✓ Today’s run finished

Today it reached Balsthal at 17:27 0 min

  1. Oensingen17:19
  2. Klus17:23
  3. Thalbrücke17:25
  4. Balsthal17:27

Next service: tomorrow 17:19 from Oensingen · Sat 21 Nov

Next departure 17:19 tomorrow · Oensingen
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 Balsthal, 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:19on time on time
17:23≈ on time ≈ on time
17:25≈ on time ≈ on time
17:27on 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 NovBalsthal 17:280 min—
Thu 19 NovBalsthal 17:280 min—
Wed 18 NovBalsthal 17:280 min—
Tue 17 NovBalsthal 17:280 min—
Mon 16 NovBalsthal 17:280 min—
Sun 15 NovBalsthal 17:280 min—
Sat 14 NovBalsthal 17:280 min—
Fri 13 NovBalsthal 17:280 min—
Thu 12 NovBalsthal 17:280 min—
Wed 11 NovBalsthal 17:280 min—
Tue 10 NovBalsthal 17:280 min—
Mon 9 NovBalsthal 17:280 min—
Sun 8 NovBalsthal 17:280 min—
Sat 7 NovBalsthal 17:280 min—
Fri 6 NovBalsthal 17:280 min—
Thu 5 NovBalsthal 17:280 min—
Wed 4 NovBalsthal 17:280 min—
Tue 3 NovBalsthal 17:280 min—
Mon 2 NovBalsthal 17:280 min—
Sun 1 NovBalsthal 17:280 min—
Sat 31 OctBalsthal 17:280 min—
Fri 30 OctBalsthal 17:280 min—
Thu 29 OctBalsthal 17:280 min—
Wed 28 OctBalsthal 17:280 min—
Tue 27 OctBalsthal 17:29+1 min+1 min
Mon 26 OctBalsthal 17:280 min—
Sun 25 OctBalsthal 17:280 min—
Sat 24 OctBalsthal 17:280 min—
Fri 23 OctBalsthal 17:280 min—
Thu 22 OctBalsthal 17:280 min—