Os 8236 8236 Veselí nad Lužnicí – Tábor

View line Os 8236

Veselí nad Lužnicí 19:06 → Tábor 19:31 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 9 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Tábor at 19:32 No data

  1. Veselí nad Lužnicí19:06
  2. Řípec-Dráchov19:09
  3. Myslkovice19:16
  4. Doubí u Tábora19:19
  5. Planá nad Lužnicí19:22
  6. Tábor-Čápův Dvůr19:27
  7. Tábor19:31

Next service: tomorrow 19:06 from Veselí nad Lužnicí · Fri 6 Nov

Next departure 19:06 tomorrow · Veselí nad Lužnicí
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Tábor, 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

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

  • Early 3% · 1
  • On time 97% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
19:06on time on time
19:09≈ on time ≈ on time
19:12 / 19:13≈ on time ≈ on time
19:16≈ on time ≈ on time
19:19≈ on time ≈ +1 min
19:22 / 19:23≈ on time ≈ +1 min
19:25≈ on time ≈ on time
19:27≈ on time ≈ on time
19:31on time 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
Thu 5 NovTábor 19:32No data—
Wed 4 NovTábor 19:32No data—
Tue 3 NovTábor 19:32No data—
Mon 2 NovTábor 19:32No data—
Fri 30 OctTábor 19:32No data—
Thu 29 OctTábor 19:32No data—
Tue 27 OctTábor 19:33No data—
Mon 26 OctTábor 19:32No data—
Fri 23 OctTábor 19:32No data—
Thu 22 OctTábor 19:32No data—
Wed 21 OctTábor 19:32No data—
Tue 20 OctTábor 19:32No data—
Mon 19 OctTábor 19:32No data—
Fri 16 OctTábor 19:32No data—
Thu 15 OctTábor 19:32No data—
Wed 14 OctTábor 19:32No data—
Tue 13 OctTábor 19:32No data—
Mon 12 OctTábor 19:33No data—
Fri 9 OctTábor 19:32No data—
Thu 8 OctTábor 19:32No data—
Wed 7 OctTábor 19:32No data—
Tue 6 OctTábor 19:32No data—
Mon 5 OctTábor 19:32No data—
Fri 2 Oct— 19:450 min—
Thu 1 Oct— 19:44−1 min—
Wed 30 Sept— 19:450 min—
Tue 29 Sept— 19:450 min—
Fri 25 Sept— 19:460 min—
Thu 24 Sept— 19:44−1 min—
Wed 23 Sept— 19:460 min—