RE7 4387 Bern – Wolhusen

View line RE7

Bern 20:36 → Wolhusen 21:44 Daily 1 h 08 min · 8 stops BLS

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 20:36 from Bern · Thu 12 Nov

Next departure 20:36 today · Bern
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
90%
45/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 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: +1 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

  • Sat 7 Nov Max en route +49 min · last fix heading to Trubschachen +49 min
  • Fri 21 Aug Max en route +19 min · last fix heading to Schüpfheim +19 min
  • Thu 3 Sept Max en route +13 min · last fix heading to Wolhusen +13 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Wolhusen +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Wolhusen +3 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 84% · 42
  • 3–10 min 4% · 2
  • 10–30 min 4% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 88% M n=8
  • 100% T n=7
  • 100% W n=7
  • 86% T n=7
  • 67% F n=6
  • 86% S n=7
  • 100% S n=8

Stops and timetable

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

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