RE5 1135 Bern – Solothurn

View line RE5

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

✓ Today’s run finished

Today, last fix heading to Solothurn at 14:09 No data

  1. Bern13:35
  2. Jegenstorf13:48
  3. Fraubrunnen13:52
  4. Bätterkinden13:58
  5. Lohn-Lüterkofen14:02
  6. Biberist RBS14:06
  7. Solothurn14:10

Next service: tomorrow 13:35 from Bern · Fri 6 Nov

Next departure 13:35 tomorrow · Bern
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 7 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

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=2
  • 100% F n=4
  • 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, 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
13:35on time on time
13:48≈ on time ≈ on time
13:52≈ on time ≈ on time
13:58≈ on time ≈ on time
14:02≈ on time ≈ on time
14:06≈ on time ≈ on time
14:10on time on time

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