Os 19337 19337 Kouřim – Pečky

View line Os 19337

Kouřim 22:10 → Pečky 22:46 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Kouřim22:10
  2. Zalešany22:19
  3. Žabonosy22:22
  4. Plaňany22:27
  5. Chroustov22:35
  6. Chotutice22:38
  7. Pečky22:46

Next service: tomorrow 22:10 from Kouřim · Fri 6 Nov

Next departure 22:10 tomorrow · Kouřim
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 16 full · 0 partial · 5 no data
On-time · 90 days
98%
52/53 runs under 3 min
RT coverage: 53 full · 0 partial · 7 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: +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

Worst days

  • Fri 4 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 23% · 12
  • On time 75% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 53 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
22:10on time on time
22:15 / 22:16≈ on time ≈ on time
22:19≈ on time ≈ on time
22:22≈ on time ≈ on time
22:24≈ on time ≈ on time
22:27 / 22:29≈ on time ≈ on time
22:32≈ 1 min early ≈ on time
22:35≈ 1 min early ≈ on time
22:38≈ 1 min early ≈ on time
22:40≈ 1 min early ≈ on time
22: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
Thu 5 NovPečky 22:480 min+2 min
Wed 4 NovPečky 22:490 min+1 min
Tue 3 NovPečky 22:49+1 min+4 min
Mon 2 NovPečky 22:490 min+1 min
Fri 30 OctPečky 22:49−1 min+3 min
Thu 29 OctPečky 22:490 min+4 min
Tue 27 OctPečky 22:49−2 min+1 min
Mon 26 OctPečky 22:490 min+1 min
Fri 23 OctPečky 22:510 min+3 min
Thu 22 OctPečky 22:500 min—
Wed 21 OctPečky 22:490 min+1 min
Tue 20 OctPečky 22:48−2 min+1 min
Mon 19 OctPečky 22:50+1 min+1 min
Fri 16 OctPečky 22:500 min—
Thu 15 OctPečky 22:49+1 min+1 min
Wed 14 OctPečky 22:500 min+1 min
Tue 13 OctPečky 22:47No data—
Mon 12 OctPečky 22:47No data—
Fri 9 OctPečky 22:47No data—
Thu 8 OctPečky 22:48No data—
Wed 7 OctPečky 22:47No data—
Tue 6 OctPečky 22:47No data—
Mon 5 OctPečky 22:47No data—
Wed 30 Sept— 22:59−1 min—
Tue 29 Sept— 22:59−1 min—
Fri 25 Sept— 22:58−2 min—
Thu 24 Sept— 23:00−1 min—
Wed 23 Sept— 22:59−1 min—
Tue 22 Sept— 22:59−1 min—
Mon 21 Sept— 23:00−1 min—