S35 6521 Kerzers – Lyss

View line S35

Kerzers 12:06 → Lyss 12:26 Daily 0 h 20 min · 8 stops BLS

✓ Today’s run finished

Today it reached Lyss at 12:27 +1 min

  1. Kerzers12:06
  2. Kerzers Papiliorama12:08
  3. Fräschels12:10
  4. Bargen BE12:16
  5. Aarberg12:19
  6. Lyss Grien12:22
  7. Lyss12:26

Next service: tomorrow 12:06 from Kerzers · Sat 7 Nov

Next departure 12:06 tomorrow · Kerzers
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Lyss, 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 1 Nov Max en route +3 min · last fix heading to Lyss +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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