S3 17315 Delémont – Olten

View line S3

Delémont 04:37 → Olten 06:10 Daily 1 h 33 min · 20 stops SBB CFF FFS

Running now · updated 05:00

Between Grellingen and Duggingen 0 min

Estimated arrival at Olten 06:10 · 50 km/h

  1. Delémont04:37
  2. Grellingen05:00
  3. Duggingen05:02
  4. Dornach-Arlesheim05:08
  5. Muttenz05:36
  6. Liestal05:47
  7. Olten06:10

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
97%
71/73 runs under 3 min
RT coverage: 72 full · 1 partial · 1 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: +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

  • Fri 14 Aug Max en route +7 min · last fix heading to Olten +7 min
  • Wed 9 Sept Max en route +3 min · last fix heading to Chur +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 71
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=11
  • 92% W n=12
  • 100% T n=11
  • 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 (20 stops).

Last 90 days, 73 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 10Today
04:37on time on timePassed
04:50≈ on time ≈ on timePassed
04:54≈ on time ≈ on timePassed
05:00≈ on time ≈ on timePassed
05:02≈ on time ≈ on timeNext
05:05≈ on time ≈ on time
05:08≈ on time ≈ on time
05:11≈ on time ≈ on time
05:14≈ on time ≈ on time
05:18 / 05:30≈ on time ≈ on time
05:36≈ on time ≈ +1 min
05:40≈ on time ≈ +1 min
05:43≈ on time ≈ +1 min
05:47≈ on time ≈ +1 min
05:50≈ on time ≈ +1 min
05:52≈ on time ≈ +1 min
05:55≈ on time ≈ +1 min
05:58≈ on time ≈ +1 min
06:02≈ on time ≈ +1 min
06:10on 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
Thu 5 NovGrellingen 04:59Partial coverage0 min—
Wed 4 NovOlten 06:090 min—
Tue 3 NovOlten 06:090 min—
Mon 2 NovOlten 06:090 min—
Sun 1 NovOlten 06:10−1 min—
Sat 31 OctOlten 06:100 min—
Fri 30 OctOlten 06:110 min—
Thu 29 OctOlten 06:12+1 min—
Wed 28 OctOlten 06:14+3 min+3 min
Tue 27 OctOlten 06:110 min—
Mon 26 OctOlten 06:110 min—
Sun 25 OctOlten 06:110 min—
Sat 24 OctOlten 06:12+1 min+1 min
Fri 23 OctOlten 06:110 min—
Thu 22 OctOlten 06:110 min—
Wed 21 OctOlten 06:110 min—
Tue 20 OctOlten 06:110 min—
Mon 19 OctOlten 06:110 min—
Sun 18 OctTecknau 06:010 min—
Sat 17 OctTecknau 06:010 min—
Fri 16 OctOlten 06:12+1 min+1 min
Thu 15 OctOlten 06:13+1 min+1 min
Wed 14 OctOlten 06:110 min—
Tue 13 OctOlten 06:100 min—
Mon 12 OctOlten 06:14+3 min+3 min
Sun 11 OctOlten 06:110 min—
Sat 10 OctOlten 06:120 min—
Fri 9 OctOlten 06:110 min—
Thu 8 OctOlten 06:12+3 min+3 min
Wed 7 OctOlten 06:11+1 min—