RE5 1096 Solothurn – Bern

View line RE5

Solothurn 09:47 → Bern 10:22 Daily 0 h 35 min · 7 stops RBS

✓ Today’s run finished

Today it reached Bern at 10:23 +1 min

  1. Solothurn09:47
  2. Biberist RBS09:50
  3. Lohn-Lüterkofen09:54
  4. Bätterkinden09:58
  5. Fraubrunnen10:02
  6. Jegenstorf10:09
  7. Bern10:22

Next service: tomorrow 09:47 from Solothurn · Sun 8 Nov

Next departure 09:47 tomorrow · Solothurn
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 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 4 Nov Max en route +5 min · last fix heading to Bern +5 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 32
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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