BDŽ train delays, Wednesday 7 October 2026
Delays recorded on this day, in Bulgaria local time. Below: how it went, then the whole day as one file to download.
How late the trains were
79% of stops were reached less than 5 minutes late, and half of them within 0 minutes of the timetable.
- Trains
- 525
- 5 min late or more
- 21% of stops
- 15 min late or more
- 4% of stops
- Median delay
- 0 min
- Cancelled trains
- 4
Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 8,302 stops that had one, as the operator sent it. Cancelled trains (marked cancelled, or with every stop skipped), skipped stops and values over an hour early or twelve hours late are left out. 100% of the stops of the trains that ran (skipped stops aside) had a delay.
Fewer trains than usual: the archive saw 12 of the 529 trains the timetable planned (2%, against 100% on a usual day). The feed stopped or repeated old data for part of the day.
Most delayed trains
| Line | Left its first stop | Where it was latest | Delay |
|---|---|---|---|
| МБВ Международен бърз влак | София | 376 min | |
| Невша | 55 min | ||
| Русе | 40 min | ||
| София Север | 37 min | ||
| Крум | 36 min |
Download
Get the CSV Accounts are free: you sign in with a code sent to your email, no password. You come back here after signing in.
Read this day from code
This day’s table of final delays has a fixed address. Read it from DuckDB, Polars or curl, with one of your API tokens in place of YOUR_TOKEN:
https://data.train-archive.eu/daily/provider=bg-bdz/service=TripUpdate/date=2026-10-07.parquet?token=YOUR_TOKEN
A few rows of the file
13 different trains, each at one stop. The CSV has more columns, listed below.
Stop stop_name | Status trip_status |
|---|---|
| Пловдив | scheduled |
| Пловдив | scheduled |
| Мездра | scheduled |
| Свищов | scheduled |
| Варна | scheduled |
| Бургас | scheduled |
| Царева Ливада | scheduled |
| Радомир | scheduled |
| Кюстендил | scheduled |
| Монтана | scheduled |
| Пловдив | scheduled |
| Долна Махала | scheduled |
| София | scheduled |
What the columns mean
service_date- The day the train was scheduled to run.
route- The line, as the operator names it (for example IC 3 or S2).
trip_id- The operator’s code for this train run. The same train on another day has another code.
trip_start_time- When the train was scheduled to leave its first station.
stop_sequence, stop_id, stop_name- Which stop along the route: its position, code and name.
arrival_delay_min, departure_delay_min- How late the train was at that stop, in minutes. Negative means early. Empty when the operator gave a time but no delay.
predicted_arrival, predicted_departure- The time the operator last announced for that stop, in local time.
observed_at- When that last announcement was seen. After the train has passed, it is what happened.
trip_status- scheduled, cancelled or added (a train that was not in the timetable).
stop_status- skipped when the train did not stop there; empty otherwise.
route_id- The route’s code in the timetable, to join with it.