RE5 1116 Solothurn – Bern

View line RE5

Solothurn 11:47 → Bern 12:22 Daily 0 h 35 min · 7 stops RBS

Running now · updated 11:48

Position estimated from the timetable

Between Solothurn and Biberist RBS 0 min

Estimated arrival at Bern 12:22

  1. Solothurn11:47
  2. Biberist RBS11:50
  3. Lohn-Lüterkofen11:54
  4. Bätterkinden11:58
  5. Fraubrunnen12:02
  6. Jegenstorf12:09
  7. Bern12:22

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 21 runs arrived on time.

On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 10 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

Distribution · 90 days

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

  • Early 3% · 1
  • On time 97% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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 10Today
11:47on time on timePassed
11:50≈ on time ≈ on timeNext
11:54≈ on time ≈ on time
11:58≈ on time ≈ on time
12:02≈ on time ≈ on time
12:09≈ on time ≈ on time
12:22on 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
Mon 16 NovBern 12:23No data—
Sun 15 NovBern 12:22−1 min+3 min
Sat 14 NovBern 12:220 min—
Fri 13 NovBern 12:230 min—
Thu 12 NovBern 12:23No data—
Wed 11 NovBern 12:22−1 min—
Tue 10 NovBern 12:23−1 min—
Mon 9 NovBern 12:230 min—
Sun 8 NovBern 12:230 min—
Sat 7 NovBern 12:22−1 min—
Fri 6 NovBern 12:24+1 min—
Thu 5 NovBern 12:23No data—
Wed 4 NovBern 12:22−1 min—
Tue 3 NovBern 12:230 min—
Mon 2 NovBern 12:23No data—
Sun 1 NovBern 12:230 min—
Sat 31 OctBern 12:22−1 min—
Fri 30 OctBern 12:22−1 min—
Thu 29 OctBern 12:23No data—
Wed 28 OctBern 12:230 min—
Tue 27 OctBern 12:24+1 min—
Mon 26 OctBern 12:24No data—
Sun 25 OctBern 12:240 min+2 min
Sat 24 OctBern 12:24+2 min+2 min
Fri 23 OctBern 12:230 min—
Thu 22 OctBern 12:23No data—
Wed 21 OctBern 12:24+1 min+1 min
Tue 20 OctBern 12:230 min—
Mon 19 OctBern 12:23No data—
Sun 18 OctBern 12:240 min+3 min