Os 8261 8261 Olbramovice – Votice

View line Os 8261

Olbramovice 09:42 → Votice 09:46 Mon, Tue, Wed, Thu, Fri 0 h 04 min · 2 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 09:42 from Olbramovice · Mon 9 Nov

Next departure 09:42 Monday · Olbramovice
On-time · 30 days
32%
6/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
65%
40/62 runs under 3 min
RT coverage: 62 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +4 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +12 min

Last 30 days

Arrival delay at Votice, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 5 Nov Max en route +15 min · last fix heading to Votice +15 min
  • Tue 3 Nov Max en route +13 min · last fix heading to Votice +13 min
  • Thu 29 Oct Max en route +12 min · last fix heading to Votice +12 min
  • Mon 24 Aug Max en route +11 min · last fix heading to — +11 min
  • Thu 22 Oct Max en route +9 min · last fix heading to Votice +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 65% · 40
  • 3–10 min 29% · 18
  • 10–30 min 6% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=12
  • 50% T n=12
  • 83% W n=12
  • 62% T n=13
  • 62% F n=13
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 62 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
09:42+1 min +7 min
09:46+1 min +8 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
Fri 6 NovVotice 09:49+1 min+1 min
Thu 5 NovVotice 10:04+15 min+15 min
Wed 4 NovVotice 09:54+5 min+6 min
Tue 3 NovVotice 10:03+13 min+13 min
Mon 2 NovVotice 09:54+4 min+4 min
Fri 30 OctVotice 09:54+4 min+4 min
Thu 29 OctVotice 10:03+12 min+12 min
Tue 27 OctVotice 09:59No data—
Mon 26 OctVotice 09:52+2 min+2 min
Fri 23 OctVotice 09:50+2 min+2 min
Thu 22 OctVotice 09:59+9 min+9 min
Wed 21 OctVotice 09:500 min+1 min
Tue 20 OctVotice 09:56+6 min+6 min
Mon 19 OctVotice 09:52+1 min+1 min
Fri 16 OctVotice 09:54+4 min+4 min
Thu 15 OctVotice 09:54+3 min+3 min
Wed 14 OctVotice 09:58+8 min+9 min
Tue 13 OctVotice 09:57+7 min+7 min
Mon 12 OctVotice 09:51+1 min+1 min
Fri 9 OctVotice 09:57+7 min+7 min
Thu 8 OctVotice 09:51+1 min+1 min
Wed 7 OctVotice 09:51+1 min+1 min
Tue 6 OctVotice 09:55+5 min+5 min
Mon 5 Oct— 10:04+3 min+3 min
Fri 2 Oct— 10:03+2 min+3 min
Thu 1 Oct— 10:020 min+1 min
Wed 30 Sept— 10:000 min—
Tue 29 Sept— 10:000 min—
Fri 25 Sept— 10:01+1 min+2 min
Thu 24 Sept— 10:00−1 min—