Os 27841 27841 Mirošov město → Rokycany

View line Os 27841

Mirošov město 04:07 → Rokycany 04:23 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 7 stops České dráhy, a.s.

Os 27841 Mirošov město–Rokycany: final delay under 3 min on 29 of its 29 runs with data in the last 90 days (100%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 18:07 (GMT+1).

It does not run today

Last recorded run: Friday 20 November No data

Next service: tomorrow 04:07 from Mirošov město · Mon 23 Nov

Next departure 04:07 tomorrow · Mirošov město
On-time · 30 days
—
Too little data (0/18 runs with data)
RT coverage: 0 full · 0 partial · 18 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 32 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
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

Distribution · 90 days

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

  • Early 7% · 2
  • On time 93% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
04:07on time on time
04:09 / 04:10≈ on time ≈ on time
04:12≈ on time ≈ on time
04:14≈ on time ≈ on time
04:16≈ 1 min early ≈ on time
04:19≈ 1 min early ≈ on time
04:231 min early on time

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 04:24No data—
Thu 19 NovRokycany 04:24No data—
Wed 18 NovRokycany 04:24No data—
Mon 16 NovRokycany 04:25No data—
Fri 13 NovRokycany 04:24No data—
Thu 12 NovRokycany 04:24No data—
Wed 11 NovRokycany 04:24No data—
Tue 10 NovRokycany 04:24No data—
Mon 9 NovRokycany 04:24No data—
Fri 6 NovRokycany 04:24No data—
Thu 5 NovRokycany 04:24No data—
Wed 4 NovRokycany 04:24No data—
Tue 3 NovRokycany 04:24No data—
Mon 2 NovRokycany 04:24No data—
Fri 30 OctRokycany 04:24No data—
Thu 29 OctRokycany 04:24No data—
Tue 27 OctRokycany 04:24No data—
Mon 26 OctRokycany 04:24No data—
Fri 23 OctRokycany 04:24No data—
Thu 22 OctRokycany 04:24No data—
Wed 21 OctRokycany 04:24No data—
Tue 20 OctRokycany 04:24No data—
Mon 19 OctRokycany 04:24No data—
Fri 16 OctRokycany 04:24No data—
Thu 15 OctRokycany 04:24No data—
Wed 14 OctRokycany 04:24No data—
Tue 13 OctRokycany 04:24No data—
Mon 12 OctRokycany 04:24No data—
Fri 9 OctRokycany 04:24No data—
Thu 8 OctRokycany 04:24No data—