S8 8110 Jegenstorf – Bern

View line S8

Jegenstorf 11:17 → Bern 11:35 Mon, Tue, Wed, Thu, Fri, Sat 0 h 18 min · 9 stops RBS

✓ Today’s run finished

Today it reached Bern at 11:35 0 min

  1. Jegenstorf11:17
  2. Urtenen11:19
  3. Schönbühl Shoppyland11:22
  4. Moosseedorf11:23
  5. Zollikofen11:26
  6. Worblaufen11:30
  7. Bern11:35

Next service: tomorrow 11:17 from Jegenstorf · Wed 18 Nov

Next departure 11:17 tomorrow · Jegenstorf
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 8 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 32 full · 0 partial · 10 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

Worst days

  • Tue 10 Nov Max en route +5 min · last fix heading to Bern +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=1
  • 88% T n=8
  • 100% W n=7
  • 100% T n=3
  • 100% F n=6
  • 100% S n=6
  • 100% S n=1

Stops and timetable

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

Last 90 days, 32 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
11:17on time on time
11:19≈ on time ≈ on time
11:21≈ on time ≈ on time
11:22≈ on time ≈ on time
11:23≈ on time ≈ on time
11:26≈ on time ≈ on time
11:27≈ on time ≈ on time
11:30≈ on time ≈ on time
11:35on 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
Tue 17 NovBern 11:340 min—
Mon 16 NovBern 11:34No data—
Sat 14 NovBern 11:340 min—
Fri 13 NovBern 11:340 min—
Thu 12 NovBern 11:340 min—
Wed 11 NovBern 11:340 min—
Tue 10 NovBern 11:39+5 min+5 min
Mon 9 NovBern 11:34No data—
Sat 7 NovBern 11:340 min—
Fri 6 NovBern 11:340 min—
Thu 5 NovBern 11:34No data—
Wed 4 NovBern 11:340 min—
Tue 3 NovBern 11:340 min—
Mon 2 NovBern 11:34No data—
Sat 31 OctBern 11:35−1 min—
Fri 30 OctBern 11:35−1 min—
Thu 29 OctBern 11:36No data—
Wed 28 OctBern 11:360 min—
Tue 27 OctBern 11:360 min—
Mon 26 OctBern 11:37No data—
Sat 24 OctBern 11:360 min—
Fri 23 OctBern 11:360 min—
Thu 22 OctBern 11:36No data—
Wed 21 OctBern 11:360 min—
Tue 20 OctBern 11:360 min—
Mon 19 OctBern 11:36No data—
Sat 17 OctBern 11:35−1 min—
Fri 16 OctBern 11:360 min—
Thu 15 OctBern 11:36No data—
Wed 14 OctBern 11:360 min—