S35 6533 Kerzers – Lyss

View line S35

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

✓ Today’s run finished

Today it reached Lyss at 18:26 0 min

  1. Kerzers18:06
  2. Kerzers Papiliorama18:08
  3. Fräschels18:10
  4. Bargen BE18:16
  5. Aarberg18:19
  6. Lyss Grien18:22
  7. Lyss18:26

Next service: tomorrow 18:06 from Kerzers · Sun 8 Nov

Next departure 18:06 tomorrow · Kerzers
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
94%
33/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 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

  • Tue 13 Oct Max en route +9 min · last fix heading to Lyss +9 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Lyss +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 33
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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