S37 7066 Biel/Bienne – Ins

View line S37

Biel/Bienne 12:20 → Ins 12:54 Daily 0 h 34 min · 16 stops Aare Seeland mobil

✓ Today’s run finished

Today it reached Ins at 12:54 0 min

  1. Biel/Bienne12:20
  2. Ipsach12:24
  3. Sutz12:27
  4. Gerolfingen12:33
  5. Hagneck12:39
  6. Brüttelen12:47
  7. Ins12:54

Next service: tomorrow 12:20 from Biel/Bienne · Fri 6 Nov

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

Last 30 days

Arrival delay at Ins, 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

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

  • Early 0% · 0
  • On time 100% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 36 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:20on time on time
12:22≈ on time ≈ on time
12:23≈ on time ≈ on time
12:24≈ on time ≈ on time
12:25≈ on time ≈ on time
12:27≈ on time ≈ on time
12:30≈ on time ≈ on time
12:32≈ on time ≈ on time
12:33≈ on time ≈ on time
12:36 / 12:37≈ on time ≈ +1 min
12:39≈ on time ≈ +1 min
12:41≈ on time ≈ +1 min
12:44≈ on time ≈ +1 min
12:47≈ on time ≈ +1 min
12:51≈ on time ≈ +1 min
12:54on time +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
Thu 5 NovIns 12:540 min—
Wed 4 NovButtes 18:27+1 min+2 min
Tue 3 NovButtes 18:240 min+2 min
Mon 2 NovButtes 18:29+2 min+2 min
Sun 1 NovButtes 18:240 min+2 min
Sat 31 OctButtes 18:260 min+2 min
Fri 30 OctButtes 18:28+2 min+2 min
Thu 29 OctButtes 18:26−1 min—
Wed 28 OctButtes 18:28+2 min+2 min
Tue 27 OctButtes 18:260 min—
Mon 26 OctButtes 18:270 min—
Sun 25 OctButtes 18:250 min+2 min
Sat 24 OctButtes 18:27+1 min+3 min
Fri 23 OctButtes 18:260 min+2 min
Thu 22 OctButtes 18:27+1 min+1 min
Wed 21 OctButtes 18:26+1 min+2 min
Tue 20 OctButtes 18:27+1 min+1 min
Mon 19 OctButtes 18:260 min+1 min
Sun 18 OctButtes 18:25−1 min—
Sat 17 OctButtes 18:260 min+4 min
Fri 16 OctButtes 18:270 min+2 min
Thu 15 OctButtes 18:260 min+2 min
Wed 14 OctButtes 18:260 min+2 min
Tue 13 OctButtes 18:270 min—
Mon 12 OctButtes 18:250 min—
Sun 11 OctButtes 18:260 min—
Sat 10 OctButtes 18:27+1 min+2 min
Fri 9 OctButtes 18:270 min+1 min
Thu 8 OctButtes 18:28+1 min+1 min
Wed 7 OctButtes 18:28+1 min+2 min