RE12 4769 Olten – Wettingen

View line RE12

Olten 11:35 → Wettingen 12:16 Daily 0 h 41 min · 7 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 11:35 from Olten · Fri 6 Nov

Next departure 11:35 today · Olten
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 8 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 Wettingen, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
11:35+1 min +1 min
11:44 / 11:45≈ on time ≈ +1 min
11:52≈ on time ≈ +1 min
11:59 / 12:03≈ on time ≈ +1 min
12:07≈ on time ≈ +1 min
12:12 / 12:13≈ on time ≈ +1 min
12:16on 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 NovWettingen 12:17No data—
Wed 4 NovWettingen 12:170 min+1 min
Tue 3 NovWettingen 12:170 min—
Mon 2 NovWettingen 12:17No data—
Sun 1 NovWettingen 12:17+1 min—
Sat 31 OctWettingen 12:170 min—
Fri 30 OctWettingen 12:170 min—
Thu 29 OctWettingen 12:17No data—
Wed 28 OctWettingen 12:170 min—
Tue 27 OctWettingen 12:17+1 min—
Mon 26 OctWettingen 12:18No data—
Sun 25 OctWettingen 12:17+1 min—
Sat 24 OctWettingen 12:170 min—
Fri 23 OctWettingen 12:16+1 min—
Thu 22 OctWettingen 12:17No data—
Wed 21 OctWettingen 12:170 min—
Tue 20 OctWettingen 12:20+3 min+3 min
Mon 19 OctWettingen 12:17No data—
Sun 18 OctWettingen 12:180 min+1 min
Sat 17 OctWettingen 12:170 min—
Fri 16 OctWettingen 12:180 min—
Thu 15 OctWettingen 12:17No data—
Wed 14 OctWettingen 12:170 min—
Tue 13 OctWettingen 12:19+1 min+1 min
Mon 12 OctWettingen 12:17No data—
Sun 11 OctWettingen 12:170 min—
Sat 10 OctWettingen 12:180 min—
Fri 9 OctWettingen 12:170 min—
Thu 8 OctWettingen 12:170 min—
Wed 7 OctWettingen 12:170 min—