RE5 1070 Solothurn – Bern

View line RE5

Solothurn 07:02 → Bern 07:37 Daily 0 h 35 min · 6 stops RBS

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 07:02 from Solothurn · Mon 9 Nov

Next departure 07:02 Monday · Solothurn
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
98%
50/51 runs under 3 min
RT coverage: 51 full · 0 partial · 4 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

  • Wed 14 Oct Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 50
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=11
  • 91% W n=11
  • 100% T n=9
  • 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, 51 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
07:02on time on time
07:05≈ on time ≈ on time
07:09≈ on time ≈ on time
07:13≈ on time ≈ on time
07:24≈ on time ≈ on time
07: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
Fri 6 NovBern 07:380 min—
Thu 5 NovBern 07:380 min—
Wed 4 NovBern 07:39+1 min+1 min
Tue 3 NovBern 07:39+1 min—
Mon 2 NovBern 07:380 min—
Fri 30 OctBern 07:370 min—
Thu 29 OctBern 07:40+2 min+2 min
Wed 28 OctBern 07:380 min—
Tue 27 OctBern 07:380 min—
Mon 26 OctBern 07:390 min—
Fri 23 OctBern 07:380 min—
Thu 22 OctBern 07:39+1 min—
Wed 21 OctBern 07:39+1 min—
Tue 20 OctBern 07:390 min—
Mon 19 OctBern 07:380 min—
Fri 16 OctBern 07:39+1 min+1 min
Thu 15 OctBern 07:38−1 min—
Wed 14 OctBern 07:42+4 min+4 min
Tue 13 OctBern 07:39+1 min—
Mon 12 OctBern 07:380 min—
Fri 9 OctBern 07:380 min—
Thu 8 OctBern 07:38−1 min—
Wed 7 OctBern 07:380 min—
Tue 6 OctBern 07:380 min—
Mon 5 OctBern 07:38−1 min—
Sun 4 OctWorblaufen 07:340 min—
Mon 28 SeptBern 09:060 min—
Fri 25 SeptBern 09:060 min—
Thu 24 SeptBern 11:360 min—
Wed 23 SeptBern 11:360 min—