IC8 10802 Bern – Brig

View line IC8

Bern 06:07 → Brig 07:13 Daily 1 h 06 min · 5 stops SBB CFF FFS

Running now · updated 07:11

Position estimated from the timetable

Between Visp and Brig 0 min

Estimated arrival at Brig 07:13 · 70 km/h

  1. Bern06:07
  2. Thun06:26
  3. Spiez06:37
  4. Visp07:04
  5. Brig07:13

Today it is running worse than usual: typical arrival delay is 0 min; 97% of the last 30 runs arrived on time.

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 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: +1 min

Last 30 days

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

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

Worst days

  • Mon 26 Oct Max en route +10 min · last fix heading to Brig +10 min

Distribution · 90 days

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

  • Early 10% · 3
  • On time 87% · 26
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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 10Today
06:07on time on timePassed
06:26 / 06:27≈ on time ≈ on timePassed
06:37 / 06:38≈ on time ≈ +1 minPassed
07:04 / 07:05≈ on time ≈ +1 minPassed
07:13on time +1 minNext

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 17 NovBrig 07:090 min—
Mon 16 NovBrig 07:14+1 min—
Sun 15 NovBrig 07:13−1 min—
Sat 14 NovBrig 07:14−1 min—
Fri 13 NovBrig 07:140 min—
Thu 12 NovBrig 07:14−1 min—
Wed 11 NovBrig 07:13−1 min—
Tue 10 NovBrig 07:140 min—
Mon 9 NovBrig 07:140 min—
Sun 8 NovBrig 07:140 min—
Sat 7 NovBrig 07:13−1 min—
Fri 6 NovBrig 07:14+1 min—
Thu 5 NovBrig 07:13−1 min—
Wed 4 NovBrig 07:14+1 min—
Tue 3 NovBrig 07:140 min—
Mon 2 NovBrig 07:140 min—
Sun 1 NovBrig 07:13−1 min—
Sat 31 OctBrig 07:13−1 min—
Fri 30 OctBrig 07:13−1 min—
Thu 29 OctBrig 07:15+1 min+1 min
Wed 28 OctBrig 07:140 min—
Tue 27 OctBrig 07:140 min—
Mon 26 OctBrig 07:24+10 min+10 min
Sun 25 OctBrig 07:140 min—
Sat 24 OctBrig 07:140 min—
Fri 23 OctBrig 07:13−1 min—
Thu 22 OctBrig 07:15+1 min+1 min
Wed 21 OctBrig 07:140 min—
Tue 20 OctBrig 07:14−1 min—
Mon 19 OctBrig 07:16+1 min+1 min