S12 345 St. Urban → Langenthal

View line S12

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

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

✓ Today’s run finished

Today it reached Langenthal at 14:41 −2 min

  1. St. Urban14:30
  2. Roggwil Buchägerten14:30
  3. Roggwil Dorf14:32
  4. Kaltenherberg14:34
  5. Langenthal Industrie Nord14:35
  6. Langenthal Gaswerk14:36
  7. Langenthal14:41

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

Next departure 14:30 tomorrow · St. Urban
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 12 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 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

Worst days

  • Fri 6 Nov Max en route +4 min · last fix heading to Langenthal +4 min

Distribution · 90 days

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

  • Early 46% · 17
  • On time 51% · 19
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=1
  • 86% 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, 37 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
14:30+1 min +2 min
14:30≈ +1 min ≈ +2 min
14:32≈ on time ≈ +2 min
14:33≈ on time ≈ +2 min
14:34≈ on time ≈ +2 min
14:35≈ on time ≈ +2 min
14:36≈ on time ≈ +2 min
14:411 min early +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 14:39−2 min—
Fri 20 NovLangenthal 14:39+1 min—
Thu 19 NovLangenthal 14:42No data—
Wed 18 NovLangenthal 14:39−3 min—
Tue 17 NovLangenthal 14:42−1 min+2 min
Mon 16 NovLangenthal 14:42No data—
Sun 15 NovLangenthal 14:39−3 min—
Sat 14 NovLangenthal 14:44+2 min+3 min
Fri 13 NovLangenthal 14:39+2 min+2 min
Thu 12 NovLangenthal 14:43No data—
Wed 11 NovLangenthal 14:39+1 min—
Tue 10 NovLangenthal 14:380 min—
Mon 9 NovLangenthal 14:42No data—
Sun 8 NovLangenthal 14:39−2 min—
Sat 7 NovLangenthal 14:39+2 min+2 min
Fri 6 NovLangenthal 14:43+4 min+4 min
Thu 5 NovLangenthal 14:42No data—
Wed 4 NovLangenthal 14:39+2 min+2 min
Tue 3 NovLangenthal 14:39+2 min+2 min
Mon 2 NovLangenthal 14:42No data—
Sun 1 NovLangenthal 14:410 min+1 min
Sat 31 OctLangenthal 14:39−1 min—
Fri 30 OctLangenthal 14:420 min+2 min
Thu 29 OctLangenthal 14:42No data—
Wed 28 OctLangenthal 14:44+1 min+2 min
Tue 27 OctLangenthal 14:41+1 min+2 min
Mon 26 OctLangenthal 14:42No data—
Sun 25 OctLangenthal 14:38−2 min—
Sat 24 OctLangenthal 14:39−2 min—
Fri 23 OctLangenthal 14:40−2 min—