КПВ 90201 Самуил – Каспичан
Alerts for train 90201
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line КПВ.
✓ Today’s run finished
Today it reached Каспичан at 06:03 0 min
- Самуил05:10
- Висока Поляна05:17
- Байково05:24
- Каменяк05:41
- Златна Нива05:50
- Плиска05:55
- Каспичан06:03
Next service: tomorrow 05:10 from Самуил · Fri 6 Nov
Last 30 days
Arrival delay at Каспичан, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 13 Oct Max en route +12 min · last fix heading to Каспичан +10 min
- Thu 15 Oct Max en route +6 min · last fix heading to Каспичан +5 min
- Sat 31 Oct Max en route +6 min · last fix heading to Каспичан +3 min
- Fri 9 Oct Max en route +5 min · last fix heading to Каспичан +3 min
Distribution · 90 days
29 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 25
- 3–10 min 10% · 3
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 75% T n=4
- 100% W n=4
- 80% T n=5
- 75% F n=4
- 75% S n=4
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 29 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 |
|---|---|---|---|
| 05:10 | on time | on time | |
| 05:17 / 05:18 | ≈ on time | ≈ on time | |
| 05:24 / 05:25 | ≈ on time | ≈ +1 min | |
| 05:33 / 05:34 | ≈ on time | ≈ +1 min | |
| 05:41 / 05:42 | ≈ on time | ≈ +2 min | |
| 05:50 / 05:51 | ≈ on time | ≈ +2 min | |
| 05:55 / 05:56 | ≈ on time | ≈ +3 min | |
| 06:03 | on time | +3 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 5 October 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 |
|---|---|---|---|
| Thu 5 Nov | Каспичан 06:04 | 0 min | — |
| Tue 3 Nov | Каспичан 06:04 | 0 min | — |
| Mon 2 Nov | Каспичан 06:04 | 0 min | — |
| Sun 1 Nov | Каспичан 06:04 | 0 min | — |
| Sat 31 Oct | Каспичан 06:07 | +3 min | +6 min |
| Fri 30 Oct | Каспичан 06:04 | 0 min | — |
| Thu 29 Oct | Каспичан 06:04 | 0 min | — |
| Wed 28 Oct | Каспичан 06:04 | 0 min | — |
| Tue 27 Oct | Каспичан 06:04 | 0 min | — |
| Mon 26 Oct | Каспичан 06:06 | +2 min | +4 min |
| Sun 25 Oct | Каспичан 06:04 | 0 min | — |
| Sat 24 Oct | Каспичан 06:04 | 0 min | — |
| Fri 23 Oct | Каспичан 06:04 | 0 min | — |
| Thu 22 Oct | Каспичан 06:04 | 0 min | — |
| Wed 21 Oct | Каспичан 06:04 | 0 min | — |
| Tue 20 Oct | Каспичан 06:06 | +2 min | +3 min |
| Mon 19 Oct | Каспичан 06:04 | 0 min | — |
| Sun 18 Oct | Каспичан 06:04 | 0 min | — |
| Sat 17 Oct | Каспичан 06:04 | 0 min | +1 min |
| Fri 16 Oct | Каспичан 06:04 | 0 min | — |
| Thu 15 Oct | Каспичан 06:09 | +5 min | +6 min |
| Wed 14 Oct | Каспичан 06:04 | 0 min | — |
| Tue 13 Oct | Каспичан 06:14 | +10 min | +12 min |
| Mon 12 Oct | Каспичан 06:04 | 0 min | — |
| Sun 11 Oct | Каспичан 06:04 | 0 min | — |
| Sat 10 Oct | Каспичан 06:04 | 0 min | — |
| Fri 9 Oct | Каспичан 06:07 | +3 min | +5 min |
| Thu 8 Oct | Каспичан 06:04 | 0 min | — |
| Wed 7 Oct | Каспичан 06:04 | 0 min | — |
| Tue 6 Oct | Каспичан 06:04 | No data | — |