Os 27813 27813 Příkosice → Rokycany

View line Os 27813

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

It has not run yet today

Last recorded run: Friday 20 November No data

Next service: today 11:02 from Příkosice · Sat 21 Nov

Next departure 11: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
88%
37/42 runs under 3 min
RT coverage: 42 full · 0 partial · 46 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

  • Fri 25 Sept Max en route +9 min · last fix heading to — +7 min
  • Tue 8 Sept Max en route +6 min · last fix heading to — +5 min
  • Thu 1 Oct Max en route +5 min · last fix heading to — +4 min
  • Thu 24 Sept Max en route +4 min · last fix heading to — +3 min
  • Sat 19 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 83% · 35
  • 3–10 min 12% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 83% T n=6
  • 100% W n=6
  • 67% T n=6
  • 83% F n=6
  • 80% S n=5
  • 100% S n=6

Stops and timetable

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

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