Os 8273 8273 Olbramovice – Votice

View line Os 8273

Olbramovice 15:42 → Votice 15:46 Daily 0 h 04 min · 2 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Votice at 15:47 +1 min

  1. Olbramovice15:42
  2. Votice15:46

Next service: tomorrow 15:42 from Olbramovice · Sat 7 Nov

Next departure 15:42 tomorrow · Olbramovice
On-time · 30 days
43%
13/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
62%
55/89 runs under 3 min
RT coverage: 89 full · 0 partial · 0 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: +9 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

  • Sun 18 Oct Max en route +39 min · last fix heading to Votice +39 min
  • Mon 2 Nov Max en route +19 min · last fix heading to Votice +18 min
  • Wed 19 Aug Max en route +17 min · last fix heading to — +17 min
  • Mon 10 Aug Max en route +15 min · last fix heading to — +15 min
  • Tue 1 Sept Max en route +13 min · last fix heading to — +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 62% · 55
  • 3–10 min 31% · 28
  • 10–30 min 6% · 5
  • 30+ min 1% · 1

On-time by weekday

  • 69% M n=13
  • 69% T n=13
  • 77% W n=13
  • 62% T n=13
  • 54% F n=13
  • 45% S n=11
  • 54% S n=13

Stops and timetable

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

Last 90 days, 89 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
15:42+1 min +8 min
15: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 15:49+1 min+1 min
Thu 5 NovVotice 15:490 min—
Wed 4 NovVotice 15:500 min+1 min
Tue 3 NovVotice 15:54+5 min+5 min
Mon 2 NovVotice 16:08+18 min+19 min
Sun 1 NovVotice 15:56+6 min+6 min
Sat 31 OctVotice 15:57+7 min+7 min
Fri 30 OctVotice 15:55+5 min+6 min
Thu 29 OctVotice 15:53+3 min+3 min
Wed 28 OctVotice 15:51+1 min+1 min
Tue 27 OctVotice 15:500 min—
Mon 26 OctVotice 15:49−1 min—
Sun 25 OctVotice 15:58+8 min+8 min
Sat 24 OctVotice 15:55+5 min+6 min
Fri 23 OctVotice 15:58+9 min+9 min
Thu 22 OctVotice 16:00+9 min+9 min
Wed 21 OctVotice 15:55+5 min+6 min
Tue 20 OctVotice 15:51+1 min+1 min
Mon 19 OctVotice 15:500 min—
Sun 18 OctVotice 16:29+39 min+39 min
Sat 17 OctVotice 15:51+1 min+1 min
Fri 16 OctVotice 15:54+2 min+2 min
Thu 15 OctVotice 15:56+5 min+5 min
Wed 14 OctVotice 15:500 min—
Tue 13 OctVotice 16:00+10 min+10 min
Mon 12 OctVotice 15:53+3 min+3 min
Sun 11 OctVotice 15:49−1 min—
Sat 10 OctVotice 15:51+1 min+1 min
Fri 9 OctVotice 15:57+7 min+8 min
Thu 8 OctVotice 15:58+7 min+7 min