S14 23862 Weinfelden – Konstanz

View line S14

Weinfelden 13:06 → Konstanz 13:34 Daily 0 h 28 min · 9 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 13:34 0 min

  1. Weinfelden13:06
  2. Kehlhof13:11
  3. Siegershausen13:17
  4. Lengwil13:21
  5. Kreuzlingen Bernrain13:24
  6. Kreuzlingen13:31
  7. Konstanz13:34

Next service: tomorrow 13:06 from Weinfelden · Thu 12 Nov

Next departure 13:06 tomorrow · Weinfelden
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%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Konstanz, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 17 Oct Max en route +5 min · last fix heading to Konstanz +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 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=6
  • 100% T n=1
  • 100% F n=5
  • 83% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 33 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
13:06on time on time
13:11≈ on time ≈ on time
13:14≈ on time ≈ on time
13:17≈ on time ≈ +1 min
13:21 / 13:22≈ on time ≈ +1 min
13:24≈ on time ≈ +1 min
13:27≈ on time ≈ +1 min
13:31≈ on time ≈ +1 min
13:34on time +1 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
Wed 11 NovKonstanz 13:340 min—
Tue 10 NovKonstanz 13:340 min—
Mon 9 NovKonstanz 13:34No data—
Sun 8 NovKonstanz 13:340 min—
Sat 7 NovKonstanz 13:340 min—
Fri 6 NovKonstanz 13:340 min—
Thu 5 NovKonstanz 13:34No data—
Wed 4 NovKonstanz 13:340 min—
Tue 3 NovKonstanz 13:340 min—
Mon 2 NovKonstanz 13:34No data—
Sun 1 NovKonstanz 13:360 min—
Sat 31 OctKonstanz 13:38+2 min+2 min
Fri 30 OctKonstanz 13:360 min—
Thu 29 OctKonstanz 13:36No data—
Wed 28 OctKonstanz 13:36−1 min—
Tue 27 OctKonstanz 13:360 min—
Mon 26 OctKonstanz 13:36No data—
Sun 25 OctKonstanz 13:36+1 min—
Sat 24 OctKonstanz 13:360 min—
Fri 23 OctKonstanz 13:360 min—
Thu 22 OctKonstanz 13:36No data—
Wed 21 OctKonstanz 13:360 min—
Tue 20 OctKonstanz 13:36−1 min—
Mon 19 OctKonstanz 13:36No data—
Sun 18 OctKonstanz 13:350 min—
Sat 17 OctKonstanz 13:40+5 min+5 min
Fri 16 OctKonstanz 13:350 min—
Thu 15 OctKonstanz 13:35No data—
Wed 14 OctKonstanz 13:34−1 min—
Tue 13 OctKonstanz 13:360 min—