S14 23850 Weinfelden – Konstanz

View line S14

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

✓ Today’s run finished

Today it reached Konstanz at 11:34 0 min

  1. Weinfelden11:06
  2. Kehlhof11:11
  3. Siegershausen11:17
  4. Lengwil11:21
  5. Kreuzlingen Bernrain11:24
  6. Kreuzlingen11:31
  7. Konstanz11:34

Next service: tomorrow 11:06 from Weinfelden · Wed 11 Nov

Next departure 11:06 tomorrow · Weinfelden
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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