RE5 1090 Solothurn – Bern

View line RE5

Solothurn 09:02 → Bern 09:37 Daily 0 h 35 min · 6 stops RBS

✓ Today’s run finished

Today, last fix heading to Bern at 09:38 No data

  1. Solothurn09:02
  2. Biberist RBS09:05
  3. Lohn-Lüterkofen09:09
  4. Bätterkinden09:13
  5. Jegenstorf09:24
  6. Bern09:37

Next service: tomorrow 09:02 from Solothurn · Fri 20 Nov

Next departure 09:02 tomorrow · Solothurn
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 2 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 33 full · 0 partial · 2 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: +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

  • Tue 10 Nov Max en route +11 min · last fix heading to Bern +11 min
  • Wed 4 Nov Max en route +7 min · last fix heading to Bern +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 86% W n=7
  • 100% T n=5
  • 100% F n=6
  • — 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, 33 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:02on time on time
09:05≈ on time ≈ on time
09:09≈ on time ≈ on time
09:13≈ on time ≈ on time
09:24≈ on time ≈ on time
09:37on time on time

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
Thu 19 NovBern 09:38No data—
Wed 18 NovBern 09:37−1 min—
Tue 17 NovBern 09:390 min—
Mon 16 NovBern 09:37−1 min—
Fri 13 NovBern 09:38−1 min—
Thu 12 NovBern 09:380 min—
Wed 11 NovBern 09:37−1 min—
Tue 10 NovBern 09:49+11 min+11 min
Mon 9 NovBern 09:37−1 min—
Fri 6 NovBern 09:380 min—
Thu 5 NovBern 09:380 min—
Wed 4 NovBern 09:44+7 min+7 min
Tue 3 NovBern 09:380 min—
Mon 2 NovBern 09:380 min—
Fri 30 OctBern 09:380 min—
Thu 29 OctBern 09:38No data—
Wed 28 OctBern 09:39+1 min—
Tue 27 OctBern 09:38−1 min—
Mon 26 OctSolothurn 11:010 min—
Fri 23 OctBern 09:380 min—
Thu 22 OctBern 09:380 min—
Wed 21 OctBern 09:380 min—
Tue 20 OctBern 09:38−1 min—
Mon 19 OctBern 09:380 min—
Fri 16 OctBern 09:380 min—
Thu 15 OctBern 09:380 min—
Wed 14 OctBern 09:37−1 min—
Tue 13 OctBern 09:390 min—
Mon 12 OctBern 09:380 min—
Fri 9 OctBern 09:380 min—