RE1 5239 Herisau – Konstanz

View line RE1

Herisau 20:05 → Konstanz 20:50 Daily 0 h 45 min · 5 stops Thurbo

It has not run yet today

Last recorded run: Friday 6 November −1 min

Next service: today 20:05 from Herisau · Sat 7 Nov

Next departure 20:05 today · Herisau
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 2 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
20:05on time on time
20:14 / 20:15≈ on time ≈ on time
20:33≈ on time ≈ on time
20:47≈ on time ≈ on time
20:501 min early on time

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 20:49−1 min—
Thu 5 NovKonstanz 20:49−1 min—
Wed 4 NovKonstanz 20:49−1 min—
Tue 3 NovKonstanz 20:520 min—
Mon 2 NovKonstanz 20:49−1 min—
Sun 1 NovKonstanz 20:49−1 min—
Sat 31 OctKonstanz 20:510 min—
Fri 30 OctKonstanz 20:510 min—
Thu 29 OctKonstanz 20:50−1 min—
Wed 28 OctKonstanz 20:520 min—
Tue 27 OctKonstanz 20:520 min—
Mon 26 OctKonstanz 20:51−1 min—
Sun 25 OctKonstanz 20:50−1 min—
Sat 24 OctKonstanz 20:51No data—
Fri 23 OctKonstanz 20:52+1 min+1 min
Thu 22 OctKonstanz 20:51−1 min—
Wed 21 OctKonstanz 20:50−1 min—
Tue 20 OctKonstanz 20:520 min—
Mon 19 OctKonstanz 20:50−1 min—
Sun 18 OctKonstanz 20:50−1 min—
Sat 17 OctKonstanz 20:510 min—
Fri 16 OctKonstanz 20:51−1 min—
Thu 15 OctKonstanz 20:51No data—
Wed 14 OctKonstanz 20:510 min—
Tue 13 OctKonstanz 20:520 min—
Mon 12 OctKonstanz 20:510 min—
Sun 11 OctKonstanz 20:510 min—
Sat 10 OctKonstanz 20:520 min—
Fri 9 OctKonstanz 20:51−1 min—
Thu 8 OctKonstanz 20:520 min—