RE5 1140 Solothurn – Bern

View line RE5

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

It has not run yet today

Last recorded run: Monday 9 November No data

Next service: today 14:02 from Solothurn · Tue 10 Nov

Next departure 14:02 today · Solothurn
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
100%
51/51 runs under 3 min
RT coverage: 51 full · 0 partial · 9 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 Bern, 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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=9
  • 100% W n=9
  • 100% T n=9
  • 100% F n=10
  • 100% S n=4
  • 100% S n=5

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
14:02on time +1 min
14:05≈ on time ≈ +1 min
14:09≈ on time ≈ +1 min
14:13≈ on time ≈ +1 min
14:24≈ on time ≈ on time
14:37on 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
Mon 9 NovBern 14:38No data—
Sun 8 NovChur 14:02−1 min—
Sat 7 NovChur 14:02−1 min—
Fri 6 NovBern 14:380 min—
Thu 5 NovBern 14:38No data—
Wed 4 NovBern 14:380 min—
Tue 3 NovBern 14:38−1 min—
Mon 2 NovBern 14:38No data—
Sun 1 NovChur 14:030 min—
Sat 31 OctChur 14:02−1 min—
Fri 30 OctBern 14:380 min—
Thu 29 OctBern 14:380 min—
Wed 28 OctBern 14:380 min+1 min
Tue 27 OctBern 14:380 min—
Mon 26 OctBern 14:38No data—
Sun 25 OctChur 14:030 min—
Sat 24 OctChur 14:030 min—
Fri 23 OctBern 14:380 min—
Thu 22 OctBern 14:380 min+2 min
Wed 21 OctBern 14:380 min—
Tue 20 OctBern 14:380 min—
Mon 19 OctBern 14:38No data—
Sun 18 OctChur 14:03−1 min—
Sat 17 OctChur 14:030 min—
Fri 16 OctBern 14:390 min+1 min
Thu 15 OctBern 14:38No data—
Wed 14 OctBern 14:380 min+1 min
Tue 13 OctBern 14:38−1 min—
Mon 12 OctBern 14:38No data—
Fri 9 OctBern 14:37−1 min+2 min