ПВ 90101 Русе Разпределителна – Ветово
Alerts for train 90101
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line ПВ.
It has not run yet today
Last recorded run: Sunday 8 November 0 min
Next service: today 11:30 from Русе Разпределителна · Mon 9 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
- Fri 6 Nov Max en route +11 min · last fix heading to Ветово +10 min
- Sat 24 Oct Max en route +9 min · last fix heading to Тракия +8 min
- Sun 1 Nov Max en route +6 min · last fix heading to Шумен +3 min
Distribution · 90 days
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 81% · 13
- 3–10 min 13% · 2
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=1
- 100% W n=1
- 100% T n=2
- 75% F n=4
- 50% S n=2
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 16 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 |
|---|---|---|---|
| 11:30 | on time | +2 min | |
| 11:39 / 11:40 | ≈ on time | ≈ +2 min | |
| 11:45 / 11:46 | ≈ on time | ≈ +2 min | |
| 11:53 / 11:54 | ≈ on time | ≈ +3 min | |
| 12:08 | on time | +5 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 |
|---|---|---|---|
| Sun 8 Nov | Ветово 12:09 | 0 min | — |
| Sat 7 Nov | Ветово 12:09 | No data | — |
| Fri 6 Nov | Ветово 12:19 | +10 min | +11 min |
| Thu 5 Nov | Ветово 12:09 | 0 min | — |
| Wed 4 Nov | Ветово 12:09 | No data | — |
| Tue 3 Nov | Ветово 12:09 | 0 min | — |
| Mon 2 Nov | Ветово 12:09 | +1 min | — |
| Sun 1 Nov | Шумен 14:52 | +3 min | +6 min |
| Sat 31 Oct | Ветово 12:09 | No data | — |
| Fri 30 Oct | Ветово 12:09 | 0 min | — |
| Thu 29 Oct | Ветово 12:09 | 0 min | — |
| Wed 28 Oct | Ветово 12:09 | No data | — |
| Tue 27 Oct | Ветово 12:09 | No data | — |
| Mon 26 Oct | Шумен 14:49 | 0 min | +12 min |
| Sun 25 Oct | Шумен 14:49 | No data | — |
| Sat 24 Oct | Тракия 14:50 | +8 min | +9 min |
| Fri 23 Oct | Ветово 12:09 | 0 min | +1 min |
| Thu 22 Oct | Ветово 12:09 | No data | — |
| Wed 21 Oct | Ветово 12:09 | No data | — |
| Tue 20 Oct | Ветово 12:09 | No data | — |
| Mon 19 Oct | Ветово 12:09 | 0 min | — |
| Sun 18 Oct | Ветово 12:09 | No data | — |
| Sat 17 Oct | Ветово 12:09 | No data | — |
| Fri 16 Oct | Ветово 12:09 | No data | — |
| Thu 15 Oct | Ветово 12:09 | No data | — |
| Wed 14 Oct | Ветово 12:09 | No data | — |
| Tue 13 Oct | Ветово 12:09 | No data | — |
| Mon 12 Oct | Шумен 14:49 | No data | — |
| Sun 11 Oct | Шумен 14:49 | 0 min | +2 min |
| Sat 10 Oct | Шумен 14:49 | 0 min | +2 min |