Os 19325 19325 Kouřim – Pečky
Alerts for train 19325
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 19325.
It has not run yet today
Last recorded run: Monday 9 November −1 min
Next service: today 17:10 from Kouřim · Tue 10 Nov
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 18 Sept Max en route +15 min · last fix heading to — +12 min
- Thu 17 Sept Max en route +14 min · last fix heading to — +11 min
- Fri 4 Sept Max en route +9 min · last fix heading to — +7 min
- Mon 17 Aug Max en route +7 min · last fix heading to — +5 min
- Thu 29 Oct Max en route +6 min · last fix heading to Pečky +4 min
Distribution · 90 days
52 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 12% · 6
- On time 67% · 35
- 3–10 min 17% · 9
- 10–30 min 4% · 2
- 30+ min 0% · 0
On-time by weekday
- 90% M n=10
- 100% T n=10
- 90% W n=10
- 55% T n=11
- 64% F n=11
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:10 | on time | on time | |
| 17:15 / 17:16 | ≈ on time | ≈ +1 min | |
| 17:19 | ≈ on time | ≈ +1 min | |
| 17:22 | ≈ on time | ≈ +1 min | |
| 17:24 | ≈ on time | ≈ +2 min | |
| 17:27 / 17:29 | ≈ on time | ≈ +2 min | |
| 17:32 | ≈ on time | ≈ +2 min | |
| 17:35 | ≈ on time | ≈ +3 min | |
| 17:38 | ≈ on time | ≈ +3 min | |
| 17:40 | ≈ on time | ≈ +3 min | |
| 17:46 | on time | +4 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Pečky 17:49 | −1 min | +3 min |
| Fri 6 Nov | Pečky 17:52 | +2 min | +3 min |
| Thu 5 Nov | Pečky 17:49 | 0 min | +1 min |
| Wed 4 Nov | Pečky 17:49 | −1 min | +2 min |
| Tue 3 Nov | Pečky 17:48 | −2 min | +1 min |
| Mon 2 Nov | Pečky 17:49 | +1 min | +1 min |
| Fri 30 Oct | Pečky 17:50 | 0 min | +4 min |
| Thu 29 Oct | Pečky 17:54 | +4 min | +6 min |
| Tue 27 Oct | Pečky 17:50 | 0 min | +2 min |
| Mon 26 Oct | Pečky 17:49 | −1 min | +2 min |
| Fri 23 Oct | Pečky 17:50 | +1 min | +1 min |
| Thu 22 Oct | Pečky 17:54 | +4 min | +5 min |
| Wed 21 Oct | Pečky 17:50 | +1 min | +1 min |
| Tue 20 Oct | Pečky 17:49 | 0 min | — |
| Mon 19 Oct | Pečky 17:49 | +1 min | +3 min |
| Fri 16 Oct | Pečky 17:49 | −1 min | +1 min |
| Thu 15 Oct | Pečky 17:53 | +3 min | +6 min |
| Wed 14 Oct | Pečky 17:48 | −2 min | +1 min |
| Tue 13 Oct | Pečky 17:47 | No data | — |
| Mon 12 Oct | Pečky 17:48 | No data | — |
| Fri 9 Oct | Pečky 17:47 | No data | — |
| Thu 8 Oct | Pečky 17:47 | No data | — |
| Wed 7 Oct | Pečky 17:47 | No data | — |
| Tue 6 Oct | Pečky 17:47 | No data | — |
| Mon 5 Oct | Pečky 17:47 | No data | — |
| Wed 30 Sept | — 17:59 | −1 min | — |
| Tue 29 Sept | — 17:59 | −1 min | — |
| Fri 25 Sept | — 17:59 | −2 min | — |
| Thu 24 Sept | — 17:59 | −1 min | — |
| Wed 23 Sept | — 17:59 | −2 min | — |