RE5 1202 Solothurn – Bern

View line RE5

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

✓ Today’s run finished

Today it reached Bern at 20:52 −1 min

  1. Solothurn20:17
  2. Biberist RBS20:20
  3. Lohn-Lüterkofen20:24
  4. Bätterkinden20:28
  5. Fraubrunnen20:32
  6. Jegenstorf20:39
  7. Bern20:52

Next service: tomorrow 20:17 from Solothurn · Fri 20 Nov

Next departure 20:17 tomorrow · Solothurn
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 4 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

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

  • Early 0% · 0
  • On time 100% · 43
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=4
  • 100% T n=6
  • 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, 43 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
20:17on time on time
20:20≈ on time ≈ on time
20:24≈ on time ≈ on time
20:28≈ on time ≈ on time
20:32≈ on time ≈ on time
20:39≈ on time ≈ on time
20:52on 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 20:52−1 min—
Wed 18 NovBern 20:53No data—
Tue 17 NovBern 20:530 min—
Mon 16 NovBern 20:530 min—
Sun 15 NovBern 20:53+1 min+1 min
Sat 14 NovBern 20:530 min—
Fri 13 NovBern 20:53−1 min—
Thu 12 NovBern 20:53−1 min—
Wed 11 NovBern 20:52−1 min—
Tue 10 NovBern 20:52−1 min—
Mon 9 NovBern 20:530 min—
Sun 8 NovBern 20:530 min—
Sat 7 NovBern 20:52−1 min—
Fri 6 NovBern 20:52−1 min—
Thu 5 NovBern 20:530 min—
Wed 4 NovBern 20:530 min—
Tue 3 NovBern 20:52−1 min—
Mon 2 NovBern 20:53−1 min—
Sun 1 NovBern 20:53−1 min—
Sat 31 OctBern 20:530 min—
Fri 30 OctBern 20:530 min—
Thu 29 OctBern 20:530 min—
Wed 28 OctBern 20:53−1 min—
Tue 27 OctBern 20:530 min—
Mon 26 OctBern 20:530 min—
Sun 25 OctBern 20:52−1 min—
Sat 24 OctBern 20:52−1 min—
Fri 23 OctBern 20:530 min—
Thu 22 OctBern 20:53No data—
Wed 21 OctBern 20:53No data—