S37 7014 Biel/Bienne → Ins

View line S37

Biel/Bienne 05:48 → Ins 06:24 Sat, Sun 0 h 36 min · 16 stops Aare Seeland mobil

S37 7014 Biel/Bienne–Ins: final delay under 3 min on 9 of its 9 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 16:47 (GMT+1).

✓ Today’s run finished

Today it reached Ins at 06:25 +1 min

  1. Biel/Bienne05:48
  2. Ipsach05:52
  3. Sutz05:55
  4. Gerolfingen06:01
  5. Hagneck06:09
  6. Brüttelen06:17
  7. Ins06:24

Next service: tomorrow 05:48 from Biel/Bienne · Sun 22 Nov

Next departure 05:48 tomorrow · Biel/Bienne
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 21 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 35 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 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • 100% T n=1
  • — F n=0
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 15 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
05:48on time on time
05:50≈ on time ≈ on time
05:51≈ on time ≈ on time
05:52≈ on time ≈ +1 min
05:53≈ on time ≈ +1 min
05:55≈ on time ≈ +1 min
05:58≈ on time ≈ +1 min
06:00≈ on time ≈ +1 min
06:01≈ on time ≈ +1 min
06:04 / 06:07≈ +1 min ≈ +1 min
06:09≈ +1 min ≈ +1 min
06:11≈ +1 min ≈ +1 min
06:14≈ +1 min ≈ +1 min
06:17≈ +1 min ≈ +2 min
06:21≈ +1 min ≈ +2 min
06:24+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 21 NovIns 06:24+1 min+2 min
Fri 20 NovButtes 05:24No data—
Thu 19 NovButtes 05:24No data—
Wed 18 NovButtes 05:24No data—
Tue 17 NovButtes 05:24No data—
Mon 16 NovButtes 05:24No data—
Sun 15 NovIns 06:240 min—
Sat 14 NovIns 06:27+2 min+2 min
Fri 13 NovButtes 05:27No data—
Thu 12 NovButtes 05:24No data—
Wed 11 NovButtes 05:24No data—
Tue 10 NovButtes 05:24No data—
Mon 9 NovButtes 05:24No data—
Sun 8 NovIns 06:24+1 min+1 min
Sat 7 NovIns 06:27+2 min+2 min
Fri 6 NovButtes 05:24No data—
Thu 5 NovButtes 05:24No data—
Wed 4 NovButtes 05:24No data—
Tue 3 NovButtes 05:24No data—
Mon 2 NovButtes 05:24No data—
Sun 1 NovIns 06:25+1 min+2 min
Sat 31 OctIns 06:250 min—
Fri 30 OctButtes 05:26No data—
Thu 29 OctButtes 05:26No data—
Wed 28 OctButtes 05:26No data—
Tue 27 OctButtes 05:26No data—
Mon 26 OctButtes 05:26No data—
Sun 25 OctIns 06:26+1 min+2 min
Sat 24 OctIns 06:27+2 min+2 min
Fri 23 OctButtes 05:26No data—