RE12 4777 Olten – Wettingen

View line RE12

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

✓ Today’s run finished

Today it reached Wettingen at 16:16 0 min

  1. Olten15:35
  2. Aarau15:44
  3. Wildegg15:52
  4. Brugg AG15:59
  5. Turgi16:07
  6. Baden16:12
  7. Wettingen16:16

Next service: tomorrow 15:35 from Olten · Sun 8 Nov

Next departure 15:35 tomorrow · Olten
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 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: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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=5
  • 100% T n=7
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=6

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