RE5 1105 Bern – Solothurn

View line RE5

Bern 10:35 → Solothurn 11:10 Daily 0 h 35 min · 7 stops RBS

Running now · updated 11:11

Between Biberist RBS and Solothurn No data

Estimated arrival at Solothurn 11:10 · 30 km/h

  1. Bern10:35
  2. Jegenstorf10:48
  3. Fraubrunnen10:52
  4. Bätterkinden10:58
  5. Lohn-Lüterkofen11:02
  6. Biberist RBS11:06
  7. Solothurn11:10
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Solothurn, 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

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

  • Early 3% · 1
  • On time 97% · 33
  • 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=5
  • 100% W n=6
  • 100% T n=5
  • 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, 34 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 10Today
10:35on time on timePassed
10:48≈ on time ≈ on timePassed
10:52≈ on time ≈ on timePassed
10:58≈ on time ≈ on timePassed
11:02≈ on time ≈ on timePassed
11:06≈ on time ≈ on timePassed
11:10on time on timeNext

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 NovSolothurn 11:090 min—
Wed 4 NovSolothurn 11:090 min—
Tue 3 NovSolothurn 11:090 min—
Mon 2 NovSolothurn 11:09−1 min—
Sun 1 NovSolothurn 11:100 min—
Sat 31 OctSolothurn 11:110 min—
Fri 30 OctSolothurn 11:110 min—
Thu 29 OctSolothurn 11:11No data—
Wed 28 OctSolothurn 11:110 min—
Tue 27 OctSolothurn 11:110 min—
Mon 26 OctSolothurn 11:120 min—
Sun 25 OctSolothurn 11:110 min—
Sat 24 OctSolothurn 11:110 min—
Fri 23 OctSolothurn 11:110 min—
Thu 22 OctSolothurn 11:110 min—
Wed 21 OctSolothurn 11:110 min—
Tue 20 OctSolothurn 11:120 min—
Mon 19 OctSolothurn 11:110 min—
Sun 18 OctSolothurn 11:11−1 min—
Sat 17 OctSolothurn 11:10−1 min—
Fri 16 OctSolothurn 11:110 min—
Thu 15 OctSolothurn 11:110 min—
Wed 14 OctSolothurn 11:100 min—
Tue 13 OctSolothurn 11:11−1 min—
Mon 12 OctSolothurn 11:110 min—
Sun 11 OctSolothurn 11:110 min—
Sat 10 OctSolothurn 11:120 min—
Fri 9 OctSolothurn 11:100 min—
Thu 8 OctSolothurn 11:11+3 min+3 min
Wed 7 OctSolothurn 11:10−1 min—