S3 17317 Delémont – Olten

View line S3

Delémont 05:07 → Olten 06:40 Daily 1 h 33 min · 20 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Olten at 06:40 −1 min

  1. Delémont05:07
  2. Grellingen05:30
  3. Dornach-Arlesheim05:39
  4. Muttenz06:06
  5. Liestal06:17
  6. Sissach06:25
  7. Olten06:40

Next service: tomorrow 05:07 from Delémont · Sat 14 Nov

Next departure 05:07 tomorrow · Delémont
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
65/66 runs under 3 min
RT coverage: 66 full · 0 partial · 2 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 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

  • Wed 11 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 66 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
05:07on time on time
05:20≈ on time ≈ on time
05:24≈ on time ≈ on time
05:30≈ on time ≈ on time
05:32≈ on time ≈ on time
05:36≈ on time ≈ on time
05:39≈ on time ≈ on time
05:42≈ on time ≈ on time
05:45≈ on time ≈ on time
05:49 / 06:00≈ on time ≈ on time
06:06≈ on time ≈ +1 min
06:10≈ on time ≈ +1 min
06:13≈ on time ≈ +1 min
06:17≈ on time ≈ +1 min
06:20≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:25≈ on time ≈ +1 min
06:28≈ on time ≈ +1 min
06:32≈ on time ≈ +1 min
06:40on 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
Fri 13 NovOlten 06:39−1 min—
Thu 12 NovOlten 06:39−1 min—
Wed 11 NovOlten 06:44+3 min+3 min
Tue 10 NovOlten 06:42+1 min—
Mon 9 NovOlten 06:42+1 min+1 min
Sun 8 NovOlten 06:390 min—
Sat 7 NovOlten 06:390 min—
Fri 6 NovOlten 06:420 min—
Thu 5 NovOlten 06:390 min—
Wed 4 NovOlten 06:390 min—
Tue 3 NovOlten 06:390 min—
Mon 2 NovOlten 06:42+1 min—
Sun 1 NovOlten 06:410 min—
Sat 31 OctOlten 06:42+1 min—
Fri 30 OctOlten 06:42+1 min+1 min
Thu 29 OctOlten 06:42+1 min—
Wed 28 OctOlten 06:42+1 min—
Tue 27 OctOlten 06:42+1 min+1 min
Mon 26 OctOlten 06:420 min—
Sun 25 OctOlten 06:410 min—
Sat 24 OctOlten 06:410 min—
Fri 23 OctOlten 06:410 min—
Thu 22 OctOlten 06:410 min—
Wed 21 OctOlten 06:42+1 min—
Tue 20 OctOlten 06:420 min—
Mon 19 OctOlten 06:410 min—
Sun 18 OctTecknau 06:330 min—
Sat 17 OctTecknau 06:330 min—
Fri 16 OctOlten 06:40−1 min—
Thu 15 OctOlten 06:42+1 min—