RE12 4774 Wettingen – Olten

View line RE12

Wettingen 14:42 → Olten 15:24 Daily 0 h 42 min · 7 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 14:42 from Wettingen · Fri 6 Nov

Next departure 14:42 today · Wettingen
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
14:42on time on time
14:46 / 14:47≈ on time ≈ on time
14:51 / 14:52≈ on time ≈ on time
14:57 / 15:00≈ on time ≈ on time
15:07≈ on time ≈ +1 min
15:13≈ on time ≈ +1 min
15:24on 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 NovOlten 15:240 min—
Wed 4 NovOlten 15:240 min—
Tue 3 NovOlten 15:240 min—
Mon 2 NovOlten 15:240 min—
Sun 1 NovOlten 15:240 min—
Sat 31 OctOlten 15:250 min—
Fri 30 OctOlten 15:26+1 min—
Thu 29 OctOlten 15:26+1 min—
Wed 28 OctOlten 15:27+1 min+1 min
Tue 27 OctOlten 15:26+1 min—
Mon 26 OctOlten 15:26+1 min—
Sun 25 OctOlten 15:26+1 min—
Sat 24 OctOlten 15:26+1 min—
Fri 23 OctOlten 15:250 min—
Thu 22 OctOlten 15:26+1 min—
Wed 21 OctOlten 15:26+1 min—
Tue 20 OctOlten 15:250 min—
Mon 19 OctOlten 15:250 min—
Sun 18 OctOlten 15:26+1 min—
Sat 17 OctOlten 15:250 min—
Fri 16 OctOlten 15:27+1 min—
Thu 15 OctOlten 15:250 min—
Wed 14 OctOlten 15:25+1 min—
Tue 13 OctOlten 15:250 min—
Mon 12 OctOlten 15:26+1 min+1 min
Sun 11 OctOlten 15:26+1 min—
Sat 10 OctOlten 15:26+1 min—
Fri 9 OctOlten 15:26+1 min+1 min
Thu 8 OctOlten 15:250 min—
Wed 7 OctOlten 15:250 min—