RE5 1180 Solothurn – Bern

View line RE5

Solothurn 18:02 → Bern 18:37 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 6 stops RBS

✓ Today’s run finished

Today it reached Bern at 18:37 0 min

  1. Solothurn18:02
  2. Biberist RBS18:05
  3. Lohn-Lüterkofen18:09
  4. Bätterkinden18:13
  5. Jegenstorf18:24
  6. Bern18:37

Next service: tomorrow 18:02 from Solothurn · Wed 11 Nov

Next departure 18:02 tomorrow · Solothurn
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
51/53 runs under 3 min
RT coverage: 53 full · 0 partial · 0 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 Bern, in minutes. One bar per run.

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

Worst days

  • Sun 4 Oct Max en route +7 min · last fix heading to Samedan +7 min
  • Mon 9 Nov Max en route +7 min · last fix heading to Samedan +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 51
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
18:02on time on time
18:05≈ on time ≈ on time
18:09≈ on time ≈ on time
18:13≈ on time ≈ on time
18:24≈ on time ≈ on time
18:37on 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
Tue 10 NovBern 18:380 min—
Mon 9 NovSamedan 22:17+7 min+7 min
Sun 8 NovSamedan 22:090 min—
Sat 7 NovSamedan 22:090 min—
Fri 6 NovSamedan 22:100 min—
Thu 5 NovSamedan 22:090 min—
Wed 4 NovSamedan 22:12+2 min+2 min
Tue 3 NovSamedan 22:090 min—
Mon 2 NovSamedan 22:09−1 min—
Sun 1 NovSamedan 22:090 min—
Sat 31 OctSamedan 22:100 min—
Fri 30 OctSamedan 22:100 min—
Thu 29 OctSamedan 22:11+1 min—
Wed 28 OctSamedan 22:11+1 min—
Tue 27 OctSamedan 22:110 min—
Mon 26 OctSamedan 22:11+1 min—
Sun 25 OctSamedan 22:10+1 min—
Sat 24 OctSamedan 22:100 min—
Fri 23 OctSamedan 22:100 min—
Thu 22 OctSamedan 22:100 min—
Wed 21 OctSamedan 22:100 min—
Tue 20 OctSamedan 22:100 min—
Mon 19 OctSamedan 22:100 min—
Sun 18 OctSamedan 22:11+1 min—
Sat 17 OctSamedan 22:100 min—
Fri 16 OctSamedan 22:100 min—
Thu 15 OctSamedan 22:10+1 min—
Wed 14 OctSamedan 22:11+1 min+7 min
Tue 13 OctSamedan 22:110 min—
Mon 12 OctSamedan 22:100 min—