RE7 4364 Wolhusen – Bern

View line RE7

Wolhusen 09:15 → Bern 10:27 Daily 1 h 12 min · 8 stops BLS

✓ Today’s run finished

Today it reached Bern at 10:28 +1 min

  1. Wolhusen09:15
  2. Entlebuch09:22
  3. Schüpfheim09:28
  4. Trubschachen09:44
  5. Langnau i.E.09:51
  6. Konolfingen10:06
  7. Bern10:27

Next service: tomorrow 09:15 from Wolhusen · Wed 11 Nov

Next departure 09:15 tomorrow · Wolhusen
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 44 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

  • Early 23% · 10
  • On time 77% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 100% S n=9

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 44 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:15+1 min +1 min
09:22≈ on time ≈ +1 min
09:28 / 09:29≈ on time ≈ +1 min
09:36≈ on time ≈ +1 min
09:44≈ on time ≈ +1 min
09:51 / 09:54≈ on time ≈ +1 min
10:06 / 10:07≈ on time ≈ +1 min
10:27on time +2 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
Tue 10 NovBern 10:29+1 min—
Mon 9 NovBern 10:29+2 min+2 min
Sun 8 NovBern 10:24−3 min—
Sat 7 NovBern 10:24−3 min—
Fri 6 NovBern 10:29+1 min—
Thu 5 NovBern 10:280 min—
Wed 4 NovBern 10:280 min—
Tue 3 NovBern 10:28+1 min—
Mon 2 NovBern 10:29+1 min+1 min
Sun 1 NovBern 10:25−3 min—
Sat 31 OctBern 10:29+1 min+1 min
Fri 30 OctBern 10:30+2 min+2 min
Thu 29 OctBern 10:28No data—
Wed 28 OctBern 10:30+2 min+2 min
Tue 27 OctBern 10:28−1 min—
Mon 26 OctWolhusen 11:01−2 min—
Sun 25 OctBern 10:25−3 min—
Sat 24 OctBern 10:27−1 min—
Fri 23 OctBern 10:280 min—
Thu 22 OctBern 10:29+1 min+1 min
Wed 21 OctBern 10:29+1 min+1 min
Tue 20 OctBern 10:31+2 min+2 min
Mon 19 OctBern 10:280 min—
Sun 18 OctBern 10:29+1 min+1 min
Sat 17 OctBern 10:280 min+1 min
Fri 16 OctBern 10:29+2 min+2 min
Thu 15 OctBern 10:29+1 min+1 min
Wed 14 OctBern 10:280 min—
Tue 13 OctBern 10:27−1 min+1 min
Mon 12 OctBern 10:280 min—