RE12 4792 Wettingen – Olten

View line RE12

Wettingen 23:42 → Olten 00:25 Daily 0 h 43 min · 9 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November −1 min

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

Next departure 23:42 today · Wettingen
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
94%
50/53 runs under 3 min
RT coverage: 53 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 23 Oct Max en route +8 min · last fix heading to Olten +8 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 92% · 49
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 86% W n=7
  • 100% T n=6
  • 90% F n=10
  • 100% S n=8
  • 89% S n=9

Stops and timetable

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

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