Os 27817 27817 Příkosice – Rokycany

View line Os 27817

Příkosice 14:02 → Rokycany 14:23 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 9 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Tuesday 10 November No data

Next service: today 14:02 from Příkosice · Wed 11 Nov

Next departure 14:02 today · Příkosice
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
69%
25/36 runs under 3 min
RT coverage: 36 full · 0 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+5min
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

  • Fri 11 Sept Max en route +9 min · last fix heading to — +8 min
  • Wed 9 Sept Max en route +10 min · last fix heading to — +7 min
  • Tue 29 Sept Max en route +7 min · last fix heading to — +6 min
  • Thu 1 Oct Max en route +6 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 69% · 25
  • 3–10 min 31% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 86% T n=7
  • 57% W n=7
  • 86% T n=7
  • 50% 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, 36 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
14:02on time +3 min
14:04≈ on time ≈ +3 min
14:07≈ on time ≈ +3 min
14:09 / 14:10≈ on time ≈ +3 min
14:12≈ on time ≈ +4 min
14:14≈ +1 min ≈ +4 min
14:16≈ +1 min ≈ +4 min
14:19≈ +1 min ≈ +4 min
14:23+1 min +5 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
Tue 10 NovRokycany 14:24No data—
Mon 9 NovRokycany 14:24No data—
Fri 6 NovRokycany 14:24No data—
Thu 5 NovRokycany 14:24No data—
Wed 4 NovRokycany 14:25No data—
Tue 3 NovRokycany 14:24No data—
Mon 2 NovRokycany 14:24No data—
Fri 30 OctRokycany 14:24No data—
Thu 29 OctRokycany 14:24No data—
Tue 27 OctRokycany 14:24No data—
Mon 26 OctRokycany 14:24No data—
Fri 23 OctRokycany 14:24No data—
Thu 22 OctRokycany 14:24No data—
Wed 21 OctRokycany 14:24No data—
Tue 20 OctRokycany 14:24No data—
Mon 19 OctRokycany 14:24No data—
Fri 16 OctRokycany 14:24No data—
Thu 15 OctRokycany 14:24No data—
Wed 14 OctRokycany 14:24No data—
Tue 13 OctRokycany 14:24No data—
Mon 12 OctRokycany 14:24No data—
Fri 9 OctRokycany 14:24No data—
Thu 8 OctRokycany 14:24No data—
Wed 7 OctRokycany 14:24No data—
Tue 6 OctRokycany 14:24No data—
Mon 5 Oct— 14:41+4 min+5 min
Fri 2 Oct— 14:39+1 min+3 min
Thu 1 Oct— 14:43+5 min+6 min
Wed 30 Sept— 14:41+3 min+3 min
Tue 29 Sept— 14:43+6 min+7 min