RE7 4377 Bern → Wolhusen

View line RE7

Bern 15:36 → Wolhusen 16:44 Daily 1 h 08 min · 8 stops BLS

RE7 4377 Bern–Wolhusen: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:04 (GMT+1).

✓ Today’s run finished

Today it reached Wolhusen at 16:47 +3 min

  1. Bern15:36
  2. Konolfingen15:52
  3. Langnau i.E.16:05
  4. Escholzmatt16:21
  5. Schüpfheim16:28
  6. Entlebuch16:35
  7. Wolhusen16:44

Next service: tomorrow 15:36 from Bern · Mon 23 Nov

Next departure 15:36 tomorrow · Bern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
51/52 runs under 3 min
RT coverage: 52 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: 0 min

Last 30 days

Arrival delay at Wolhusen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 25 Oct Max en route +6 min · last fix heading to Wolhusen +6 min

Distribution · 90 days

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

  • Early 12% · 6
  • On time 87% · 45
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=9
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 88% S n=8

Stops and timetable

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

Last 90 days, 52 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
15:36on time on time
15:52≈ on time ≈ on time
16:05 / 16:06≈ on time ≈ on time
16:12 / 16:14≈ on time ≈ on time
16:21≈ on time ≈ +1 min
16:28 / 16:29≈ on time ≈ +1 min
16:35≈ on time ≈ +1 min
16:44on time +1 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
Sun 22 NovWolhusen 16:48+3 min+3 min
Sat 21 NovWolhusen 16:44−1 min—
Fri 20 NovWolhusen 16:440 min—
Thu 19 NovWolhusen 16:44−1 min—
Wed 18 NovWolhusen 16:440 min—
Tue 17 NovWolhusen 16:44−1 min—
Mon 16 NovWolhusen 16:44−1 min—
Sun 15 NovWolhusen 16:44−1 min—
Sat 14 NovWolhusen 16:44−1 min—
Fri 13 NovWolhusen 16:44−1 min—
Thu 12 NovWolhusen 16:45+1 min+1 min
Wed 11 NovWolhusen 16:440 min—
Tue 10 NovWolhusen 16:440 min—
Mon 9 NovWolhusen 16:44−1 min—
Sun 8 NovWolhusen 16:440 min—
Sat 7 NovWolhusen 16:440 min—
Fri 6 NovWolhusen 16:440 min—
Thu 5 NovWolhusen 16:44−1 min—
Wed 4 NovWolhusen 16:440 min—
Tue 3 NovWolhusen 16:440 min—
Mon 2 NovWolhusen 16:440 min—
Sun 1 NovWolhusen 16:450 min—
Sat 31 OctWolhusen 16:44−1 min—
Fri 30 OctWolhusen 16:44−1 min—
Thu 29 OctWolhusen 16:450 min—
Wed 28 OctWolhusen 16:450 min—
Tue 27 OctWolhusen 16:450 min—
Mon 26 OctWolhusen 16:45−1 min—
Sun 25 OctWolhusen 16:51+6 min+6 min
Sat 24 OctWolhusen 16:44−1 min—