Os 27811 27811 Příkosice – Rokycany

View line Os 27811

Příkosice 09:02 → Rokycany 09:23 Daily 0 h 21 min · 9 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 09:02 from Příkosice · Fri 6 Nov

Next departure 09:02 today · Příkosice
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
81%
47/58 runs under 3 min
RT coverage: 58 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

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

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

Worst days

  • Sat 19 Sept Max en route +9 min · last fix heading to — +8 min
  • Fri 28 Aug Max en route +9 min · last fix heading to — +7 min
  • Tue 22 Sept Max en route +7 min · last fix heading to — +5 min
  • Sat 26 Sept Max en route +6 min · last fix heading to — +4 min
  • Mon 7 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 78% · 45
  • 3–10 min 19% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 75% T n=8
  • 88% W n=8
  • 75% T n=8
  • 88% F n=8
  • 50% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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:02on time +3 min
09:04≈ on time ≈ +3 min
09:07≈ on time ≈ +3 min
09:09 / 09:10≈ on time ≈ +3 min
09:12≈ on time ≈ +4 min
09:14≈ on time ≈ +3 min
09:16≈ on time ≈ +3 min
09:19≈ on time ≈ +3 min
09:23on time +3 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
Thu 5 NovRokycany 09:24No data—
Wed 4 NovRokycany 09:24No data—
Tue 3 NovRokycany 09:24No data—
Mon 2 NovRokycany 09:24No data—
Sun 1 NovRokycany 09:24No data—
Sat 31 OctRokycany 09:24No data—
Fri 30 OctRokycany 09:24No data—
Thu 29 OctRokycany 09:24No data—
Wed 28 OctRokycany 09:24No data—
Tue 27 OctRokycany 09:24No data—
Mon 26 OctRokycany 09:24No data—
Sun 25 OctRokycany 09:24No data—
Sat 24 OctRokycany 09:24No data—
Fri 23 OctRokycany 09:25No data—
Thu 22 OctRokycany 09:25No data—
Wed 21 OctRokycany 09:24No data—
Tue 20 OctRokycany 09:24No data—
Mon 19 OctRokycany 09:24No data—
Sun 18 OctRokycany 09:24No data—
Sat 17 OctRokycany 09:24No data—
Fri 16 OctRokycany 09:25No data—
Thu 15 OctRokycany 09:24No data—
Wed 14 OctRokycany 09:24No data—
Tue 13 OctRokycany 09:24No data—
Mon 12 OctRokycany 09:24No data—
Sun 11 OctRokycany 09:24No data—
Sat 10 OctRokycany 09:24No data—
Fri 9 OctRokycany 09:24No data—
Thu 8 OctRokycany 09:24No data—
Wed 7 OctRokycany 09:24No data—