Os 2143 2143 České Budějovice – České Velenice

View line Os 2143

České Budějovice 06:09 → České Velenice 06:57 Tue, Sat, Sun 0 h 48 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to České Velenice at 06:58 No data

  1. České Budějovice06:09
  2. Nová Ves u Českých Budějovic06:16
  3. Radostice u Trocnova06:25
  4. Hluboká u Borovan06:32
  5. Jílovice06:35
  6. Nové Hrady06:44
  7. České Velenice06:57

Next service: tomorrow 06:09 from České Budějovice · Sun 15 Nov

Next departure 06:09 tomorrow · České Budějovice
On-time · 30 days
—
Too little data (0/12 runs with data)
RT coverage: 0 full · 0 partial · 12 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at České Velenice, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
06:09on time on time
06:11≈ on time ≈ on time
06:16 / 06:17≈ on time ≈ on time
06:23≈ on time ≈ on time
06:25≈ on time ≈ +1 min
06:28 / 06:29≈ on time ≈ +1 min
06:32≈ on time ≈ +1 min
06:35 / 06:36≈ on time ≈ +1 min
06:40≈ on time ≈ +1 min
06:44 / 06:46≈ on time ≈ +1 min
06:50≈ on time ≈ +1 min
06:57on 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
Sat 14 NovČeské Velenice 06:58No data—
Sun 8 NovČeské Velenice 06:58No data—
Sat 7 NovČeské Velenice 06:58No data—
Sun 1 NovČeské Velenice 06:58No data—
Sat 31 OctČeské Velenice 06:58No data—
Fri 30 OctČeské Velenice 06:58No data—
Thu 29 OctČeské Velenice 06:58No data—
Wed 28 OctČeské Velenice 06:58No data—
Sun 25 OctČeské Velenice 06:58No data—
Sat 24 OctČeské Velenice 06:58No data—
Sun 18 OctČeské Velenice 06:58No data—
Sat 17 OctČeské Velenice 06:58No data—
Sun 11 OctČeské Velenice 06:58No data—
Sat 10 OctČeské Velenice 06:58No data—
Sun 4 Oct— 07:11−1 min—
Sat 3 Oct— 07:120 min—
Mon 28 Sept— 07:120 min—
Sun 27 Sept— 07:120 min+1 min
Sat 26 Sept— 07:110 min—
Sun 20 Sept— 07:110 min—
Sat 19 Sept— 07:130 min—
Sun 13 Sept— 07:10−1 min—
Sat 12 Sept— 07:11−1 min+2 min
Sun 6 Sept— 07:110 min+1 min
Sat 5 Sept— 07:110 min+1 min
Mon 31 Aug— 07:12+1 min+2 min
Sun 30 Aug— 07:10−1 min—
Sat 29 Aug— 07:120 min—
Fri 28 Aug— 07:120 min—
Thu 27 Aug— 07:14+2 min+4 min