RE5 1094 Solothurn – Bern

View line RE5

Solothurn 06:32 → Bern 07:07 Daily 0 h 35 min · 6 stops RBS

It has not run yet today

Last recorded run: Thursday 5 November +1 min

Next service: Monday 06:32 from Solothurn · Mon 9 Nov

Next departure 06:32 Monday · Solothurn
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
96%
46/48 runs under 3 min
RT coverage: 48 full · 0 partial · 5 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Bern +5 min
  • Wed 30 Sept Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 92% · 44
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=11
  • 91% W n=11
  • 86% T n=7
  • 100% F n=9
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 48 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
06:32on time on time
06:35≈ on time ≈ on time
06:39≈ on time ≈ on time
06:43≈ on time ≈ on time
06:54≈ on time ≈ on time
07:07on 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
Thu 5 NovBern 10:08+1 min—
Wed 4 NovBern 10:09+1 min—
Tue 3 NovBern 10:090 min—
Mon 2 NovBern 10:080 min—
Fri 30 OctBern 10:080 min—
Thu 29 OctBern 10:08No data—
Wed 28 OctBern 10:080 min—
Tue 27 OctBern 10:080 min—
Mon 26 OctSolothurn 11:010 min—
Fri 23 OctBern 10:080 min—
Thu 22 OctBern 10:080 min—
Wed 21 OctBern 10:09+1 min—
Tue 20 OctBern 10:080 min—
Mon 19 OctBern 10:080 min—
Fri 16 OctBern 10:080 min—
Thu 15 OctBern 10:080 min—
Wed 14 OctBern 10:080 min—
Tue 13 OctBern 10:090 min—
Mon 12 OctBern 10:080 min—
Fri 9 OctBern 10:080 min—
Thu 8 OctBern 10:13+5 min+5 min
Wed 7 OctBern 10:080 min—
Tue 6 OctBern 10:080 min—
Mon 5 OctBern 10:090 min—
Sun 4 OctWorblaufen 10:040 min—
Thu 1 OctBern 18:07No data—
Wed 30 SeptBern 18:06+4 min+4 min
Tue 29 SeptBern 14:060 min—
Mon 28 SeptBern 14:060 min—
Fri 25 SeptBern 14:060 min—