Os 19305 19305 Kouřim – Pečky

View line Os 19305

Kouřim 06:08 → Pečky 06:46 Daily 0 h 38 min · 11 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Monday 9 November −1 min

Next service: today 06:08 from Kouřim · Tue 10 Nov

Next departure 06:08 today · Kouřim
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
100%
76/76 runs under 3 min
RT coverage: 76 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Pečky, 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

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

  • Early 8% · 6
  • On time 92% · 70
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 100% W n=11
  • 100% T n=11
  • 100% F n=11
  • 100% S n=11
  • 100% S n=11

Stops and timetable

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

Last 90 days, 76 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
06:08on time +1 min
06:13 / 06:14≈ on time ≈ +1 min
06:17≈ on time ≈ +1 min
06:20≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:25 / 06:29≈ on time ≈ +1 min
06:32≈ on time ≈ +1 min
06:35≈ on time ≈ +1 min
06:38≈ on time ≈ +1 min
06:40≈ on time ≈ +1 min
06:46on time +1 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
Mon 9 NovPečky 06:49−1 min+1 min
Sun 8 NovPečky 06:49−1 min+1 min
Sat 7 NovPečky 06:490 min+1 min
Fri 6 NovPečky 06:49+1 min+1 min
Thu 5 NovPečky 06:49+1 min+4 min
Wed 4 NovPečky 06:49+1 min+2 min
Tue 3 NovPečky 06:490 min+1 min
Mon 2 NovPečky 06:490 min+2 min
Sun 1 NovChroustov 06:500 min+2 min
Sat 31 OctPečky 06:500 min+1 min
Fri 30 OctPečky 06:490 min+2 min
Thu 29 OctPečky 06:49−1 min+1 min
Wed 28 OctPečky 06:490 min—
Tue 27 OctPečky 06:49−1 min+1 min
Mon 26 OctPečky 06:49−1 min+1 min
Sun 25 OctPečky 06:490 min—
Sat 24 OctRadim 06:49−1 min+1 min
Fri 23 OctPečky 06:51+1 min+1 min
Thu 22 OctPečky 06:49−1 min+1 min
Wed 21 OctPečky 06:50−1 min+2 min
Tue 20 OctPečky 06:51+1 min+2 min
Mon 19 OctPečky 06:500 min+1 min
Sun 18 OctRadim 06:490 min—
Sat 17 OctPečky 06:51+1 min+1 min
Fri 16 OctPečky 06:50+1 min+1 min
Thu 15 OctPečky 06:51+1 min+1 min
Wed 14 OctPečky 06:50+1 min+1 min
Tue 13 OctPečky 06:47No data—
Mon 12 OctPečky 06:47No data—
Sun 11 OctPečky 06:47No data—