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

View line Os 2150

České Velenice 07:03 → České Budějovice 07:49 Tue, Sat, Sun 0 h 46 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to České Budějovice at 07:49 No data

  1. České Velenice07:03
  2. Nové Hrady07:14
  3. Jílovice07:23
  4. Borovany07:30
  5. Radostice u Trocnova07:33
  6. Nová Ves u Českých Budějovic07:41
  7. České Budějovice07:49

Next service: tomorrow 07:03 from České Velenice · Sun 15 Nov

Next departure 07:03 tomorrow · České Velenice
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
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at České Budějovice, 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 8% · 2
  • On time 92% · 24
  • 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
07:03on time +2 min
07:09≈ on time ≈ +1 min
07:14 / 07:15≈ on time ≈ +1 min
07:19≈ on time ≈ +1 min
07:23≈ on time ≈ +1 min
07:26≈ on time ≈ +1 min
07:30 / 07:31≈ on time ≈ +1 min
07:33≈ on time ≈ +1 min
07:35≈ on time ≈ +1 min
07:41 / 07:42≈ on time ≈ +2 min
07:46≈ on time ≈ +2 min
07:49on 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
Sat 14 NovČeské Budějovice 07:49No data—
Sun 8 NovČeské Budějovice 07:49No data—
Sat 7 NovČeské Budějovice 07:49No data—
Sun 1 NovČeské Budějovice 07:50No data—
Sat 31 OctČeské Budějovice 07:50No data—
Fri 30 OctČeské Budějovice 07:50No data—
Thu 29 OctČeské Budějovice 07:50No data—
Wed 28 OctČeské Budějovice 07:50No data—
Sun 25 OctČeské Budějovice 07:50No data—
Sat 24 OctČeské Budějovice 07:50No data—
Sun 18 OctČeské Budějovice 07:50No data—
Sat 17 OctČeské Budějovice 07:50No data—
Sun 11 OctČeské Budějovice 07:50No data—
Sat 10 OctČeské Budějovice 07:50No data—
Sun 4 Oct— 08:060 min—
Sat 3 Oct— 08:040 min—
Mon 28 Sept— 08:050 min—
Sun 27 Sept— 08:06+2 min+2 min
Sat 26 Sept— 08:06+2 min+2 min
Sun 20 Sept— 08:090 min—
Sat 19 Sept— 08:040 min—
Sun 13 Sept— 08:03−1 min—
Sat 12 Sept— 08:03−1 min—
Sun 6 Sept— 08:030 min+2 min
Sat 5 Sept— 08:040 min+1 min
Mon 31 Aug— 08:030 min+2 min
Sun 30 Aug— 08:030 min—
Sat 29 Aug— 08:030 min—
Fri 28 Aug— 08:050 min—
Thu 27 Aug— 08:03−1 min+1 min