RE5 1191 Bern – Solothurn

View line RE5

Bern 19:05 → Solothurn 19:40 Daily 0 h 35 min · 7 stops RBS

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 19:05 from Bern · Sun 8 Nov

Next departure 19:05 today · Bern
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 0 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

Worst days

  • Wed 28 Oct Max en route +5 min · last fix heading to Solothurn +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 94% · 34
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 80% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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
19:05on time on time
19:18≈ on time ≈ on time
19:22≈ on time ≈ on time
19:28≈ on time ≈ on time
19:32≈ on time ≈ on time
19:36≈ on time ≈ on time
19:40on 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
Sat 7 NovSolothurn 19:390 min—
Fri 6 NovSolothurn 19:390 min—
Thu 5 NovSolothurn 19:390 min—
Wed 4 NovSolothurn 19:390 min—
Tue 3 NovSolothurn 19:390 min—
Mon 2 NovSolothurn 19:390 min—
Sun 1 NovSolothurn 19:390 min—
Sat 31 OctSolothurn 19:400 min—
Fri 30 OctSolothurn 19:410 min—
Thu 29 OctSolothurn 19:40−1 min—
Wed 28 OctSolothurn 19:46+5 min+5 min
Tue 27 OctSolothurn 19:410 min—
Mon 26 OctSolothurn 19:410 min—
Sun 25 OctSolothurn 19:40−1 min—
Sat 24 OctSolothurn 19:410 min—
Fri 23 OctSolothurn 19:410 min—
Thu 22 OctSolothurn 19:410 min—
Wed 21 OctSolothurn 19:40−1 min—
Tue 20 OctSolothurn 19:41−1 min—
Mon 19 OctSolothurn 19:40−1 min—
Sun 18 OctSolothurn 19:40−1 min—
Sat 17 OctSolothurn 19:41+1 min—
Fri 16 OctSolothurn 19:410 min—
Thu 15 OctSolothurn 19:410 min—
Wed 14 OctSolothurn 19:410 min—
Tue 13 OctSolothurn 19:410 min—
Mon 12 OctSolothurn 19:410 min—
Sun 11 OctSolothurn 19:40−1 min—
Sat 10 OctSolothurn 19:40−1 min—
Fri 9 OctSolothurn 19:420 min—