S12 349 St. Urban → Langenthal

View line S12

St. Urban 15:30 → Langenthal 15:41 Daily 0 h 11 min · 8 stops Aare Seeland mobil

S12 349 St. Urban–Langenthal: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 19:14 (GMT+1).

✓ Today’s run finished

Today it reached Langenthal at 15:43 +2 min

  1. St. Urban15:30
  2. Roggwil Buchägerten15:30
  3. Roggwil Dorf15:32
  4. Kaltenherberg15:34
  5. Langenthal Industrie Nord15:35
  6. Langenthal Gaswerk15:36
  7. Langenthal15:41

Next service: tomorrow 15:30 from St. Urban · Sun 22 Nov

Next departure 15:30 tomorrow · St. Urban
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%
49/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
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 Langenthal, 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

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

  • Early 31% · 15
  • On time 69% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 49 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
15:30+1 min +2 min
15:30≈ +1 min ≈ +2 min
15:32≈ +1 min ≈ +2 min
15:33≈ +1 min ≈ +2 min
15:34≈ +1 min ≈ +2 min
15:35≈ +1 min ≈ +2 min
15:36≈ +1 min ≈ +2 min
15:41on 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
Sat 21 NovLangenthal 15:39+2 min+3 min
Fri 20 NovLangenthal 15:420 min+2 min
Thu 19 NovLangenthal 15:44+2 min+3 min
Wed 18 NovLangenthal 15:420 min+3 min
Tue 17 NovLangenthal 15:420 min+2 min
Mon 16 NovLangenthal 15:39+2 min+2 min
Sun 15 NovLangenthal 15:39−3 min—
Sat 14 NovLangenthal 15:39+1 min—
Fri 13 NovLangenthal 15:44+2 min+3 min
Thu 12 NovLangenthal 15:39−1 min+1 min
Wed 11 NovLangenthal 15:44+2 min+3 min
Tue 10 NovLangenthal 15:39+2 min+2 min
Mon 9 NovLangenthal 15:43+1 min+3 min
Sun 8 NovLangenthal 15:39+1 min—
Sat 7 NovLangenthal 15:42+1 min+3 min
Fri 6 NovLangenthal 15:420 min+2 min
Thu 5 NovLangenthal 15:39+1 min—
Wed 4 NovLangenthal 15:420 min+2 min
Tue 3 NovLangenthal 15:39+2 min+2 min
Mon 2 NovLangenthal 15:39+1 min+1 min
Sun 1 NovLangenthal 15:400 min+1 min
Sat 31 OctLangenthal 15:40−2 min+2 min
Fri 30 OctLangenthal 15:43+1 min+2 min
Thu 29 OctLangenthal 15:44+2 min+2 min
Wed 28 OctLangenthal 15:40−1 min—
Tue 27 OctLangenthal 15:39−2 min—
Mon 26 OctLangenthal 15:410 min+2 min
Sun 25 OctLangenthal 15:39−3 min—
Sat 24 OctLangenthal 15:40−1 min+1 min
Fri 23 OctLangenthal 15:40−2 min—