RE5 1174 Solothurn – Bern

View line RE5

Solothurn 17:32 → Bern 18:07 Daily 0 h 35 min · 6 stops RBS

✓ Today’s run finished

Today it reached Bern at 18:07 0 min

  1. Solothurn17:32
  2. Biberist RBS17:35
  3. Lohn-Lüterkofen17:39
  4. Bätterkinden17:43
  5. Jegenstorf17:54
  6. Bern18:07

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

Next departure 17:32 Monday · Solothurn
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 2 no data
On-time · 90 days
89%
32/36 runs under 3 min
RT coverage: 36 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 +8 min · last fix heading to Bern +8 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Bern +4 min
  • Thu 5 Nov Max en route +4 min · last fix heading to Bern +4 min
  • Tue 3 Nov Max en route +3 min · last fix heading to Bern +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 32
  • 3–10 min 11% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 86% W n=7
  • 71% T n=7
  • 100% F n=7
  • — 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, 36 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
17:32on time on time
17:35≈ on time ≈ on time
17:39≈ on time ≈ on time
17:43≈ on time ≈ +1 min
17:54≈ on time ≈ +2 min
18:07on time +3 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 20 NovBern 18:040 min—
Thu 19 NovBern 18:080 min—
Wed 18 NovBern 18:09+2 min+2 min
Tue 17 NovBern 18:090 min—
Mon 16 NovBern 18:080 min—
Sat 14 NovHeimerdingen 14:59No data—
Fri 13 NovBern 18:080 min—
Thu 12 NovBern 18:13+4 min+4 min
Wed 11 NovBern 18:080 min—
Tue 10 NovBern 18:09+1 min+1 min
Mon 9 NovBern 18:080 min—
Sat 7 NovHeimerdingen 14:59No data—
Fri 6 NovBern 18:07−1 min—
Thu 5 NovBern 18:09+4 min+4 min
Wed 4 NovBern 18:080 min—
Tue 3 NovBern 18:12+3 min+3 min
Mon 2 NovBern 18:08−1 min—
Fri 30 OctBern 18:070 min—
Thu 29 OctBern 18:09+1 min—
Wed 28 OctBern 18:09+1 min—
Tue 27 OctBern 18:080 min—
Mon 26 OctBern 18:080 min—
Fri 23 OctBern 18:080 min—
Thu 22 OctBern 18:08−1 min—
Wed 21 OctBern 18:080 min—
Tue 20 OctBern 18:08−1 min—
Mon 19 OctBern 18:080 min—
Fri 16 OctBern 18:08−1 min—
Thu 15 OctBern 18:080 min—
Wed 14 OctBern 18:17+8 min+8 min