S5 15745 Neuchâtel – Kerzers

View line S5

Neuchâtel 12:04 → Kerzers 12:27 Daily 0 h 23 min · 8 stops BLS

It has not run yet today

Last recorded run: Monday 16 November No data

Next service: today 12:04 from Neuchâtel · Tue 17 Nov

Next departure 12:04 today · Neuchâtel
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 10 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: 0 min

Last 30 days

Arrival delay at Kerzers, 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 +7 min · last fix heading to Marin-Epagnier +7 min

Distribution · 90 days

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

  • Early 18% · 7
  • On time 79% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 83% T n=6
  • 100% W n=6
  • 100% T n=2
  • 100% F n=7
  • 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, 39 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:04on time on time
12:07≈ on time ≈ on time
12:10≈ on time ≈ on time
12:11≈ on time ≈ on time
12:14≈ on time ≈ on time
12:18≈ on time ≈ on time
12:20≈ on time ≈ on time
12:27on time +1 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
Mon 16 NovKerzers 12:28No data—
Sun 15 NovKerzers 12:280 min—
Sat 14 NovKerzers 12:280 min—
Fri 13 NovKerzers 12:27−2 min—
Thu 12 NovKerzers 12:28No data—
Wed 11 NovKerzers 12:270 min—
Tue 10 NovKerzers 12:27−1 min—
Mon 9 NovKerzers 12:28No data—
Sun 8 NovKerzers 12:28−1 min—
Sat 7 NovKerzers 12:280 min—
Fri 6 NovKerzers 12:280 min—
Thu 5 NovKerzers 12:28No data—
Wed 4 NovKerzers 12:280 min—
Tue 3 NovKerzers 12:27−1 min—
Mon 2 NovKerzers 12:28No data—
Sun 1 NovKerzers 12:27−1 min—
Sat 31 OctKerzers 12:26−1 min—
Fri 30 OctKerzers 12:280 min—
Thu 29 OctKerzers 12:28No data—
Wed 28 OctKerzers 12:280 min—
Tue 27 OctKerzers 12:280 min—
Mon 26 OctKerzers 12:28No data—
Sun 25 OctKerzers 12:270 min—
Sat 24 OctKerzers 12:270 min—
Fri 23 OctKerzers 12:28+1 min+1 min
Thu 22 OctKerzers 12:28No data—
Wed 21 OctKerzers 12:280 min—
Tue 20 OctKerzers 12:28−1 min—
Mon 19 OctKerzers 12:28No data—
Sun 18 OctKerzers 12:30+1 min+1 min