RE5 1112 Solothurn – Bern

View line RE5

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

Running now · updated 11:48

Position estimated from the timetable

Between Jegenstorf and Bern 0 min

Estimated arrival at Bern 11:52 · 59 km/h

  1. Solothurn11:17
  2. Biberist RBS11:20
  3. Lohn-Lüterkofen11:24
  4. Bätterkinden11:28
  5. Fraubrunnen11:32
  6. Jegenstorf11:39
  7. Bern11:52

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

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

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

  • Early 26% · 9
  • On time 74% · 26
  • 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=7
  • 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, 35 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:17on time on timePassed
11:20≈ on time ≈ on timePassed
11:24≈ on time ≈ on timePassed
11:28≈ on time ≈ on timePassed
11:32≈ on time ≈ on timePassed
11:39≈ on time ≈ on timePassed
11:52on time on timeNext

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