IR75 3135 Kreuzlingen – Konstanz

View line IR75

Kreuzlingen 21:46 → Konstanz 21:50 Daily 0 h 04 min · 2 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 21:50 −1 min

  1. Kreuzlingen21:46
  2. Konstanz21:50

Next service: tomorrow 21:46 from Kreuzlingen · Sat 7 Nov

Next departure 21:46 tomorrow · Kreuzlingen
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 5 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

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

  • Early 17% · 5
  • On time 83% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 29 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
21:463 min early 3 min early
21:50on 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
Fri 6 NovKonstanz 21:49−1 min—
Thu 5 NovKonstanz 21:49−3 min—
Wed 4 NovKonstanz 21:49−2 min—
Tue 3 NovKonstanz 21:490 min—
Mon 2 NovKonstanz 21:49No data—
Sun 1 NovKonstanz 21:490 min—
Sat 31 OctKonstanz 21:51+1 min—
Fri 30 OctKonstanz 21:51−1 min—
Thu 29 OctKonstanz 21:51No data—
Wed 28 OctKonstanz 21:510 min—
Tue 27 OctKonstanz 21:51+1 min—
Mon 26 OctKonstanz 21:51No data—
Sun 25 OctKonstanz 21:51−1 min—
Sat 24 OctKonstanz 21:510 min—
Fri 23 OctKonstanz 21:510 min—
Thu 22 OctKonstanz 21:51No data—
Wed 21 OctKonstanz 21:510 min—
Tue 20 OctKonstanz 21:51−1 min—
Mon 19 OctKonstanz 21:51No data—
Sun 18 OctAltstätten Stadt 13:50+2 min+2 min
Sat 17 OctAltstätten Stadt 13:480 min—
Fri 16 OctAltstätten Stadt 13:51+3 min+3 min
Thu 15 OctAltstätten Stadt 13:46−3 min—
Wed 14 OctAltstätten Stadt 13:480 min—
Tue 13 OctAltstätten Stadt 13:480 min—
Mon 12 OctAltstätten Stadt 13:48+1 min—
Sun 11 OctAltstätten Stadt 13:50+2 min+2 min
Sat 10 OctAltstätten Stadt 13:490 min—
Fri 9 OctAltstätten Stadt 13:48+1 min—
Thu 8 OctAltstätten Stadt 13:480 min—