RE12 4767 Olten – Wettingen

View line RE12

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

✓ Today’s run finished

Today, last fix heading to Wettingen at 11:17 No data

  1. Olten10:35
  2. Aarau10:44
  3. Wildegg10:52
  4. Brugg AG10:59
  5. Turgi11:07
  6. Baden11:12
  7. Wettingen11:16

Next service: tomorrow 10:35 from Olten · Fri 20 Nov

Next departure 10:35 tomorrow · Olten
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 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 Wettingen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 31 Oct Max en route +5 min · last fix heading to Wettingen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 44
  • 3–10 min 2% · 1
  • 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=5
  • 100% F n=6
  • 83% S n=6
  • 100% S n=7

Stops and timetable

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

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