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

View line КПВ

Брусарци 12:20 → Лом 12:45 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 7 stops BDŽ

It has not run yet today

Last recorded run: Friday 13 November +5 min

Next service: today 12:20 from Брусарци · Mon 16 Nov

Next departure 12:20 today · Брусарци
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 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

  • Fri 13 Nov Max en route +6 min · last fix heading to Лом +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
12:20on time on time
12:24 / 12:25≈ on time ≈ on time
12:28 / 12:29≈ on time ≈ on time
12:32 / 12:33≈ on time ≈ on time
12:35 / 12:36≈ on time ≈ on time
12:39 / 12:40≈ on time ≈ on time
12:45on 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
Fri 13 NovЛом 12:49+5 min+6 min
Thu 12 NovЛом 12:440 min—
Wed 11 NovЛом 12:440 min—
Tue 10 NovЛом 12:440 min—
Mon 9 NovЛом 12:440 min—
Fri 6 NovЛом 12:440 min—
Thu 5 NovЛом 12:440 min—
Wed 4 NovЛом 12:440 min—
Tue 3 NovЛом 12:440 min—
Mon 2 NovЛом 12:440 min—
Fri 30 OctЛом 12:460 min—
Thu 29 OctЛом 12:460 min—
Wed 28 OctЛом 12:460 min—
Tue 27 OctЛом 12:460 min—
Mon 26 OctЛом 12:460 min—
Fri 23 OctЛом 12:460 min—
Thu 22 OctЛом 12:460 min—
Wed 21 OctЛом 12:460 min—
Tue 20 OctЛом 12:460 min—
Mon 19 OctЛом 12:460 min—
Fri 16 OctЛом 12:460 min—
Thu 15 OctЛом 12:460 min—
Wed 14 OctЛом 12:460 min—
Tue 13 OctЛом 12:460 min—
Mon 12 OctЛом 12:460 min—
Fri 9 OctЛом 12:460 min—
Thu 8 OctЛом 12:460 min—
Wed 7 OctЛом 12:470 min—
Tue 6 OctЛом 12:46No data—