RB47 1276 Korntal – Heimerdingen

View line RB47

Korntal 23:05 → Heimerdingen 23:28 Daily 0 h 23 min · 7 stops SBB CFF FFS

It has not run yet today

Last recorded run: Friday 20 November −3 min

Next service: today 23:05 from Korntal · Sat 21 Nov

Next departure 23:05 today · Korntal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 15 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 16 no data
Typical delay
−6min
Median at arrival, 90 days
30 days: −6 min
P90
−3min
9 in 10 runs arrive with less than this
30 days: −3 min

Last 30 days

Arrival delay at Heimerdingen, 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

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

  • Early 93% · 14
  • On time 7% · 1
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=8
  • 100% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 15 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
23:05on time on time
23:08≈ 1 min early ≈ 1 min early
23:11≈ 2 min early ≈ 1 min early
23:13 / 23:15≈ 2 min early ≈ 1 min early
23:18 / 23:19≈ 4 min early ≈ 2 min early
23:22 / 23:23≈ 5 min early ≈ 2 min early
23:286 min early 3 min early

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 20 NovHeimerdingen 23:29−3 min—
Thu 19 NovHeimerdingen 23:29No data—
Wed 18 NovHeimerdingen 23:29No data—
Tue 17 NovHeimerdingen 23:29No data—
Mon 16 NovHeimerdingen 23:29No data—
Sun 15 NovHeimerdingen 23:29No data—
Sat 14 NovHeimerdingen 23:29−7 min—
Fri 13 NovHeimerdingen 23:29−5 min—
Thu 12 NovHeimerdingen 23:30No data—
Wed 11 NovHeimerdingen 23:29No data—
Tue 10 NovHeimerdingen 23:29No data—
Mon 9 NovHeimerdingen 23:29No data—
Sun 8 NovHeimerdingen 23:29No data—
Sat 7 NovHeimerdingen 23:29−6 min—
Fri 6 NovHeimerdingen 23:29−1 min+1 min
Thu 5 NovHeimerdingen 23:29No data—
Wed 4 NovHeimerdingen 23:29No data—
Tue 3 NovHeimerdingen 23:29No data—
Mon 2 NovHeimerdingen 23:29No data—
Sun 1 NovHeimerdingen 23:29No data—
Sat 31 OctKlosters Platz 22:20−7 min—
Fri 30 OctKlosters Platz 22:19−6 min+1 min
Sat 24 OctKlosters Platz 22:18−9 min—
Fri 23 OctKlosters Platz 22:20−7 min—
Sat 17 OctKlosters Platz 22:19−5 min—
Fri 16 OctKlosters Platz 22:21−6 min—
Sat 10 OctKlosters Platz 22:23−4 min+2 min
Fri 9 OctKlosters Platz 22:19−9 min—
Sun 4 OctKlosters Platz 22:27No data—
Sat 3 OctKlosters Platz 22:17−4 min—