КПВ 72209 Лом – Брусарци

View line КПВ

Лом 15:00 → Брусарци 15:25 Daily 0 h 25 min · 7 stops BDŽ

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 15:00 from Лом · Mon 9 Nov

Next departure 15:00 today · Лом
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 2 no data
Typical delay
0min
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 Брусарци, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 22 Oct Max en route +15 min · last fix heading to Брусарци +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 80% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 33 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
15:00on time on time
15:04 / 15:05≈ on time ≈ on time
15:08 / 15:09≈ on time ≈ on time
15:11 / 15:12≈ on time ≈ on time
15:16 / 15:17≈ on time ≈ on time
15:20 / 15:21≈ on time ≈ on time
15:25on time 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 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

DateLast stopFinalMax
Sun 8 NovБрусарци 15:240 min—
Sat 7 NovБрусарци 15:240 min—
Fri 6 NovБрусарци 15:240 min—
Thu 5 NovБрусарци 15:240 min—
Wed 4 NovБрусарци 15:250 min—
Tue 3 NovБрусарци 15:240 min—
Mon 2 NovБрусарци 15:240 min—
Sun 1 NovБрусарци 15:260 min—
Sat 31 OctБрусарци 15:260 min—
Fri 30 OctБрусарци 15:260 min—
Thu 29 OctБрусарци 15:260 min—
Wed 28 OctБрусарци 15:260 min—
Tue 27 OctБрусарци 15:260 min—
Mon 26 OctБрусарци 15:260 min—
Sun 25 OctБрусарци 15:26No data—
Sat 24 OctБрусарци 15:260 min—
Fri 23 OctБрусарци 15:260 min—
Thu 22 OctБрусарци 15:39+13 min+15 min
Wed 21 OctБрусарци 15:260 min—
Tue 20 OctБрусарци 15:260 min—
Mon 19 OctБрусарци 15:260 min—
Sun 18 OctБрусарци 15:270 min—
Sat 17 OctБрусарци 15:260 min—
Fri 16 OctБрусарци 15:260 min—
Thu 15 OctБрусарци 15:260 min—
Wed 14 OctБрусарци 15:260 min—
Tue 13 OctБрусарци 15:260 min—
Mon 12 OctБрусарци 15:260 min—
Sun 11 OctБрусарци 15:260 min—
Sat 10 OctБрусарци 15:260 min—