IR66 3232 Bern – Neuchâtel

View line IR66

Bern 17:23 → Neuchâtel 18:03 Mon, Tue, Wed, Thu, Fri 0 h 40 min · 5 stops BLS

✓ Today’s run finished

Today it reached Neuchâtel at 18:03 −2 min

  1. Bern17:23
  2. Bern Bümpliz Nord17:28
  3. Kerzers17:40
  4. Ins17:49
  5. Neuchâtel18:03

Next service: tomorrow 17:23 from Bern · Thu 12 Nov

Next departure 17:23 tomorrow · Bern
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 3 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 3 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: −1 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

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

  • Early 59% · 17
  • On time 41% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
17:23on time on time
17:28≈ on time ≈ on time
17:40 / 17:41≈ 1 min early ≈ on time
17:49 / 17:50≈ 1 min early ≈ on time
18:031 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
Wed 11 NovNeuchâtel 18:02−2 min—
Tue 10 NovSigmaringen 22:34−2 min—
Mon 9 NovSigmaringen 22:34−2 min—
Sun 8 NovSigmaringen 22:33No data—
Sat 7 NovSigmaringen 22:33No data—
Fri 6 NovSigmaringen 22:340 min—
Thu 5 NovSigmaringen 22:34−1 min—
Wed 4 NovSigmaringen 22:33−1 min—
Tue 3 NovSigmaringen 22:33−1 min—
Mon 2 NovSigmaringen 22:33−1 min—
Sun 1 NovSigmaringen 22:33No data—
Fri 30 OctNeuchâtel 18:03−1 min—
Thu 29 OctNeuchâtel 18:03−1 min—
Wed 28 OctNeuchâtel 18:02−2 min—
Tue 27 OctNeuchâtel 18:03−1 min—
Mon 26 OctNeuchâtel 18:03−1 min—
Fri 23 OctNeuchâtel 18:02−2 min—
Thu 22 OctNeuchâtel 18:03−2 min—
Wed 21 OctNeuchâtel 18:01−3 min—
Tue 20 OctNeuchâtel 18:03−1 min—
Mon 19 OctNeuchâtel 18:02−2 min—
Fri 16 OctNeuchâtel 18:05−2 min—
Thu 15 OctNeuchâtel 18:04−1 min—
Wed 14 OctNeuchâtel 18:03−1 min—
Tue 13 OctNeuchâtel 18:03−2 min—
Mon 12 OctNeuchâtel 18:02−1 min—
Fri 9 OctNeuchâtel 18:03−2 min—
Thu 8 OctNeuchâtel 18:05+1 min+1 min
Wed 7 OctNeuchâtel 18:050 min—
Tue 6 OctNeuchâtel 18:02−2 min—