S5 15748 Kerzers – Neuchâtel

View line S5

Kerzers 13:31 → Neuchâtel 13:56 Daily 0 h 25 min · 8 stops BLS

It has not run yet today

Last recorded run: Friday 13 November −1 min

Next service: today 13:31 from Kerzers · Sat 14 Nov

Next departure 13:31 today · Kerzers
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 9 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Neuchâtel, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 46% · 19
  • On time 54% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=7
  • 100% W n=7
  • 100% T n=2
  • 100% F n=6
  • 100% 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, 41 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
13:31on time on time
13:34≈ on time ≈ on time
13:38≈ on time ≈ on time
13:40≈ on time ≈ on time
13:42≈ on time ≈ on time
13:46≈ 1 min early ≈ on time
13:49≈ 1 min early ≈ on time
13:561 min early 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
Fri 13 NovNeuchâtel 13:54−1 min—
Thu 12 NovNeuchâtel 13:57No data—
Wed 11 NovNeuchâtel 13:54−1 min—
Tue 10 NovNeuchâtel 13:54−1 min—
Mon 9 NovNeuchâtel 13:57No data—
Sun 8 NovNeuchâtel 13:54−1 min—
Sat 7 NovNeuchâtel 13:540 min—
Fri 6 NovNeuchâtel 13:54−1 min—
Thu 5 NovNeuchâtel 13:57No data—
Wed 4 NovNeuchâtel 13:54−1 min—
Tue 3 NovNeuchâtel 13:59+3 min+3 min
Mon 2 NovNeuchâtel 13:57No data—
Sun 1 NovNeuchâtel 13:56−1 min—
Sat 31 OctNeuchâtel 13:56−1 min—
Fri 30 OctNeuchâtel 13:55−2 min—
Thu 29 OctNeuchâtel 13:57No data—
Wed 28 OctNeuchâtel 13:56−1 min—
Tue 27 OctNeuchâtel 13:57−1 min—
Mon 26 OctNeuchâtel 13:56−1 min—
Sun 25 OctNeuchâtel 13:56−1 min—
Sat 24 OctNeuchâtel 13:55−2 min—
Fri 23 OctNeuchâtel 13:56−1 min—
Thu 22 OctNeuchâtel 13:57No data—
Wed 21 OctNeuchâtel 13:570 min—
Tue 20 OctNeuchâtel 13:56−1 min—
Mon 19 OctNeuchâtel 13:57No data—
Sun 18 OctNeuchâtel 13:56−1 min—
Sat 17 OctNeuchâtel 13:55−1 min—
Fri 16 OctNeuchâtel 13:56−2 min—
Thu 15 OctNeuchâtel 13:57No data—