Os 19301 19301 Bošice – Pečky

View line Os 19301

Bošice 04:34 → Pečky 05:04 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Pečky at 05:04 0 min

  1. Bošice04:34
  2. Žabonosy04:40
  3. Plaňany zastávka04:42
  4. Vrbčany04:50
  5. Chroustov04:53
  6. Radim04:58
  7. Pečky05:04

Next service: tomorrow 04:34 from Bošice · Fri 20 Nov

Next departure 04:34 tomorrow · Bošice
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
100%
52/52 runs under 3 min
RT coverage: 52 full · 0 partial · 6 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

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

  • Early 17% · 9
  • On time 83% · 43
  • 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=11
  • 100% T n=11
  • 100% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 52 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:34on time +1 min
04:37≈ on time ≈ +1 min
04:40≈ on time ≈ +1 min
04:42≈ on time ≈ +1 min
04:45 / 04:47≈ on time ≈ on time
04:50≈ on time ≈ on time
04:53≈ on time ≈ on time
04:56≈ 1 min early ≈ on time
04:58≈ 1 min early ≈ on time
05:041 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 19 NovPečky 05:070 min+1 min
Wed 18 NovPečky 05:080 min+1 min
Mon 16 NovPečky 05:05−1 min+1 min
Fri 13 NovPečky 05:04−1 min+1 min
Thu 12 NovPečky 05:080 min+1 min
Wed 11 NovPečky 05:080 min+1 min
Tue 10 NovPečky 05:04−2 min+2 min
Mon 9 NovPečky 05:08−1 min+1 min
Fri 6 NovPečky 05:040 min+1 min
Thu 5 NovPečky 05:040 min+1 min
Wed 4 NovPečky 05:070 min+2 min
Tue 3 NovPečky 05:070 min+1 min
Mon 2 NovPečky 05:080 min+1 min
Fri 30 OctPečky 05:07−1 min+1 min
Thu 29 OctPečky 05:07−2 min+1 min
Tue 27 OctPečky 05:070 min+1 min
Mon 26 OctPečky 05:070 min+1 min
Fri 23 OctPečky 05:080 min—
Thu 22 OctPečky 05:07−1 min+2 min
Wed 21 OctPečky 05:07−2 min+1 min
Tue 20 OctPečky 05:090 min+2 min
Mon 19 OctPečky 05:07−2 min—
Fri 16 OctPečky 05:080 min+1 min
Thu 15 OctPečky 05:07−1 min—
Wed 14 OctPečky 05:070 min+1 min
Tue 13 OctPečky 05:05No data—
Mon 12 OctPečky 05:05No data—
Fri 9 OctPečky 05:05No data—
Thu 8 OctPečky 05:05No data—
Wed 7 OctPečky 05:05No data—