RE5 1082 Solothurn – Bern

View line RE5

Solothurn 08:17 → Bern 08:52 Daily 0 h 35 min · 7 stops RBS

Running now · updated 08:42

Position estimated from the timetable

Between Jegenstorf and Bern 0 min

Estimated arrival at Bern 08:52 · 143 km/h

  1. Solothurn08:17
  2. Biberist RBS08:20
  3. Lohn-Lüterkofen08:24
  4. Bätterkinden08:28
  5. Fraubrunnen08:32
  6. Jegenstorf08:39
  7. Bern08:52

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

On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 0 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

  • Fri 6 Nov Max en route +10 min · last fix heading to Gossau SG +10 min
  • Mon 19 Oct Max en route +7 min · last fix heading to Gossau SG +7 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 93% · 42
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=7
  • 86% F n=7
  • 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, 45 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
08:17on time on timePassed
08:20≈ on time ≈ on timePassed
08:24≈ on time ≈ on timePassed
08:28≈ on time ≈ on timePassed
08:32≈ on time ≈ on timePassed
08:39≈ on time ≈ on timePassed
08:52on time +1 minNext

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
Sun 15 NovBern 08:39−2 min—
Sat 14 NovSingen (Hohentwiel) 18:290 min—
Fri 13 NovGossau SG 09:090 min—
Thu 12 NovGossau SG 09:090 min—
Wed 11 NovGossau SG 09:09+1 min—
Tue 10 NovGossau SG 09:09+1 min—
Mon 9 NovGossau SG 09:090 min—
Sun 8 NovSingen (Hohentwiel) 18:29+1 min—
Sat 7 NovSingen (Hohentwiel) 18:290 min—
Fri 6 NovGossau SG 09:13+10 min+10 min
Thu 5 NovGossau SG 09:090 min—
Wed 4 NovGossau SG 09:090 min—
Tue 3 NovGossau SG 09:09+2 min+2 min
Mon 2 NovGossau SG 09:090 min—
Sun 1 NovSingen (Hohentwiel) 18:29−1 min—
Sat 31 OctSingen (Hohentwiel) 18:300 min—
Fri 30 OctGossau SG 09:090 min—
Thu 29 OctGossau SG 09:090 min—
Wed 28 OctGossau SG 09:090 min—
Tue 27 OctGossau SG 09:080 min—
Mon 26 OctGossau SG 09:100 min—
Sun 25 OctSingen (Hohentwiel) 18:300 min—
Sat 24 OctSingen (Hohentwiel) 18:300 min+3 min
Fri 23 OctGossau SG 09:090 min—
Thu 22 OctGossau SG 09:090 min—
Wed 21 OctGossau SG 09:090 min—
Tue 20 OctGossau SG 09:090 min—
Mon 19 OctGossau SG 09:16+7 min+7 min
Sun 18 OctSingen (Hohentwiel) 18:300 min—
Sat 17 OctSingen (Hohentwiel) 18:300 min—