RE5 1124 Solothurn – Bern

View line RE5

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

✓ Today’s run finished

Today it reached Bern at 13:07 0 min

  1. Solothurn12:32
  2. Biberist RBS12:35
  3. Lohn-Lüterkofen12:39
  4. Bätterkinden12:43
  5. Jegenstorf12:54
  6. Bern13:07

Next service: Monday 12:32 from Solothurn · Mon 23 Nov

Next departure 12:32 Monday · Solothurn
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 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

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

  • Early 11% · 5
  • On time 89% · 41
  • 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=8
  • 100% W n=7
  • 100% T n=6
  • 100% F n=7
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 46 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
12:32on time on time
12:35≈ on time ≈ on time
12:39≈ on time ≈ on time
12:43≈ on time ≈ on time
12:54≈ on time ≈ on time
13:07on 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
Fri 20 NovBern 13:080 min—
Thu 19 NovBern 13:080 min—
Wed 18 NovBern 13:080 min—
Tue 17 NovBern 13:080 min—
Mon 16 NovBern 13:080 min+2 min
Sun 15 NovChur 10:02−1 min+1 min
Sat 14 NovChur 10:030 min+2 min
Fri 13 NovBern 13:080 min—
Thu 12 NovBern 13:08−1 min—
Wed 11 NovBern 13:080 min—
Tue 10 NovBern 13:080 min—
Mon 9 NovBern 13:070 min—
Sun 8 NovChur 10:030 min—
Sat 7 NovChur 10:02−1 min—
Fri 6 NovBern 13:080 min—
Thu 5 NovBern 13:08−1 min—
Wed 4 NovBern 13:080 min—
Tue 3 NovBern 13:080 min—
Mon 2 NovBern 13:08−1 min—
Sun 1 NovChur 10:030 min—
Sat 31 OctChur 10:02−1 min—
Fri 30 OctBern 13:080 min—
Thu 29 OctBern 13:08No data—
Wed 28 OctBern 13:07−1 min—
Tue 27 OctBern 13:080 min+2 min
Mon 26 OctBern 13:080 min+1 min
Sun 25 OctChur 10:030 min—
Sat 24 OctChur 10:02−1 min+1 min
Fri 23 OctBern 13:080 min—
Thu 22 OctBern 13:08−1 min+2 min