Os 19311 19311 Kouřim – Pečky

View line Os 19311

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

✓ Today’s run finished

Today it reached Pečky at 10:46 0 min

  1. Kouřim10:10
  2. Zalešany10:19
  3. Žabonosy10:22
  4. Plaňany10:27
  5. Chroustov10:35
  6. Chotutice10:38
  7. Pečky10:46

Next service: tomorrow 10:10 from Kouřim · Tue 10 Nov

Next departure 10:10 tomorrow · Kouřim
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
100%
76/76 runs under 3 min
RT coverage: 76 full · 0 partial · 8 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 14% · 11
  • On time 86% · 65
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 100% W n=12
  • 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
10:10on time on time
10:15 / 10:16≈ on time ≈ on time
10:19≈ on time ≈ on time
10:22≈ on time ≈ on time
10:24≈ on time ≈ on time
10:27 / 10:29≈ on time ≈ on time
10:32≈ 1 min early ≈ on time
10:35≈ 1 min early ≈ on time
10:38≈ 1 min early ≈ on time
10:40≈ 1 min early ≈ on time
10:461 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
Mon 9 NovPečky 10:490 min+4 min
Sun 8 NovPečky 10:49−1 min+1 min
Sat 7 NovPečky 10:49−1 min—
Fri 6 NovPečky 10:49−1 min—
Thu 5 NovPečky 10:490 min+1 min
Wed 4 NovPečky 10:49−1 min+1 min
Tue 3 NovPečky 10:49−1 min—
Mon 2 NovPečky 10:490 min+2 min
Sun 1 NovPečky 10:49−1 min+1 min
Sat 31 OctPečky 10:49−2 min+1 min
Fri 30 OctPečky 10:490 min+1 min
Thu 29 OctPečky 10:49−1 min—
Wed 28 OctPečky 10:48−1 min—
Tue 27 OctPečky 10:500 min—
Mon 26 OctPečky 10:49−1 min—
Sun 25 OctPečky 10:490 min+1 min
Sat 24 OctPečky 10:490 min+1 min
Fri 23 OctPečky 10:500 min+2 min
Thu 22 OctPečky 10:49−1 min+1 min
Wed 21 OctPečky 10:490 min+3 min
Tue 20 OctPečky 10:51+1 min+1 min
Mon 19 OctPečky 10:49−1 min—
Sun 18 OctPečky 10:490 min+1 min
Sat 17 OctPečky 10:50+1 min+1 min
Fri 16 OctPečky 10:490 min+1 min
Thu 15 OctPečky 10:51+1 min+3 min
Wed 14 OctPečky 10:49−1 min—
Tue 13 OctPečky 10:47No data—
Mon 12 OctPečky 10:47No data—
Sun 11 OctPečky 10:47No data—