RE5 1235 Bern – Solothurn

View line RE5

Bern 23:35 → Solothurn 00:13 Daily 0 h 38 min · 10 stops RBS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 23:35 from Bern · Thu 5 Nov

Next departure 23:35 today · Bern
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 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

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

  • Early 5% · 2
  • On time 95% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 41 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:35on time on time
23:48≈ on time ≈ on time
23:52≈ on time ≈ on time
23:54≈ on time ≈ on time
23:55≈ on time ≈ on time
23:57≈ on time ≈ on time
00:01≈ on time ≈ on time
00:05≈ on time ≈ on time
00:09≈ on time ≈ on time
00:13on 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
Wed 4 NovSolothurn 00:140 min—
Tue 3 NovSolothurn 00:13−1 min—
Mon 2 NovSolothurn 00:14−1 min—
Sun 1 NovSolothurn 00:14−1 min—
Sat 31 OctSolothurn 00:13−1 min—
Fri 30 OctSolothurn 00:13−1 min—
Thu 29 OctSolothurn 00:13−1 min—
Wed 28 OctSolothurn 00:140 min—
Tue 27 OctSolothurn 00:140 min—
Mon 26 OctSolothurn 00:14−1 min—
Sun 25 OctSolothurn 00:13−1 min—
Sat 24 OctSolothurn 00:130 min—
Fri 23 OctSolothurn 00:15+1 min+1 min
Thu 22 OctSolothurn 00:13−1 min—
Wed 21 OctSolothurn 00:130 min—
Tue 20 OctSolothurn 00:140 min—
Mon 19 OctSolothurn 00:140 min—
Sun 18 OctSolothurn 00:14−1 min—
Sat 17 OctSolothurn 00:140 min—
Fri 16 OctSolothurn 00:140 min—
Thu 15 OctSolothurn 00:140 min+1 min
Wed 14 OctSolothurn 00:14−1 min—
Tue 13 OctSolothurn 00:13−1 min—
Mon 12 OctSolothurn 00:13−1 min—
Sun 11 OctSolothurn 00:13−1 min—
Sat 10 OctSolothurn 00:14−1 min—
Fri 9 OctSolothurn 00:150 min—
Thu 8 OctSolothurn 00:140 min—
Wed 7 OctSolothurn 00:140 min—
Tue 6 OctSolothurn 00:13−1 min—