Telegram RegisterThe public register of Telegram
Telegram profile photo for ББПС 125 ОВМБр

Channel

ББПС 125 ОВМБр

@bbps_125ovmbr

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,028subscribers

-16 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002091280606
TypeChannel
Username@bbps_125ovmbr
Created27 April 2024measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/bbps_125ovmbr

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 49% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,0281,0441,0366 August 2026 — 1,044 subscribers6 August 2026 — 1,044 subscribers9 August 2026 — 1,042 subscribers13 August 2026 — 1,039 subscribers16 August 2026 — 1,038 subscribers19 August 2026 — 1,035 subscribers22 August 2026 — 1,040 subscribers25 August 2026 — 1,037 subscribers28 August 2026 — 1,032 subscribers31 August 2026 — 1,033 subscribers8 September 2026 — 1,032 subscribers12 September 2026 — 1,033 subscribers15 September 2026 — 1,030 subscribers19 September 2026 — 1,028 subscribers6 August 202619 September 2026
14 measurements spanning 44 days, net -16. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,026–1,046 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 12:161,028-2
15 Sept 2026, 09:591,030-3
12 Sept 2026, 05:151,033+1
8 Sept 2026, 08:011,032-1
31 Aug 2026, 02:041,033+1
28 Aug 2026, 10:341,032-5
25 Aug 2026, 03:131,037-3
22 Aug 2026, 02:381,040+5
19 Aug 2026, 05:261,035-3
16 Aug 2026, 06:121,038-1
13 Aug 2026, 00:141,039-3
9 Aug 2026, 17:421,042-2
6 Aug 2026, 14:021,044no change
6 Aug 2026, 13:521,044first reading

Engagement

6 posts held, back to 19 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

187 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥10958.3%
4725.1%
🫡115.88%
105.35%
❤‍🔥42.14%
🤝31.60%
🏆10.535%
😍10.535%
🤩10.535%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 6 of the 6 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 187 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 19 July 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 07:42 UTC317 views33 reactionsread 6 August 2026
Photo

Точність починається зі зв'язку. Бійці ББпС 125 ОВМБр відпрацювали практичне заняття із військового зв'язку. Основна увага — формам доповідей, роботі з картою та компасом, передачі інформації й орієнтуванню на місцевості. Успішне виконання бойового завдання залежить не лише від озброєння, а й від того, наскільки швидко та точно передається інформація між військовослужбовцями. Саме тому такі навички постійно вдоско

255🔥3

31 Jul 2026, 15:41 UTC197 views22 reactionsread 6 August 2026
Forwarded from @ab3armyVideo

Андрій Білецький в інтерв'ю Лорі Лумер: територіальні поступки не зупинять росію Консервативна журналістка Лора Лумер, яку вважають однією з найближчих до президента США Дональда Трампа публічних союзниць, записала півторагодинне інтерв’ю з командиром Третього армійського корпусу Андрієм Білецьким. У центрі розмови — причини російсько-української війни, перспективи української перемоги та міфи, на яких кремль рокам

14🫡51🔥1😍1

29 Jul 2026, 14:31 UTC370 views36 reactionsread 6 August 2026
Video

Працюємо без пауз. ББпС 125 ОВМБр продовжує виконувати бойові завдання. Під ударами — позиції та особовий склад противника. Кожне ураження — це ще один крок до послаблення ворога. ББпС | Instagram | 125 ОВМБр | Підтримай 125 ОВМБр | Долучитись до 125 ОВМБр | Третій армійський корпус

🔥322🤝1🫡1

26 Jul 2026, 09:18 UTC494 views33 reactionsread 6 August 2026
Photo

За впевненими рішеннями завжди стоїть підготовка. Сержантський склад ББпС 125 ОВМБр пройшов смугу перешкод — один із етапів підготовки, де випробовуються не лише фізичні якості, а й витримка, концентрація та здатність діяти під навантаженням. Саме такі тренування допомагають відточувати навички, які потрібні не лише для особистої готовності, а й для ефективного управління особовим складом під час виконання бойових

🔥246🏆1🤝1🤩1

21 Jul 2026, 08:50 UTC514 views33 reactionsread 6 August 2026
Video

Кожна ціль має значення. ББпС 125-ї ОВМБр продовжує бойову роботу. FPV уражають особовий склад, укриття та техніку противника, позбавляючи його можливості діяти й утримувати позиції. Бойова робота — на відео. ББпС | Instagram | 125 ОВМБр | Підтримай 125 ОВМБр | Долучитись до 125 ОВМБр | Третій армійський корпус

🔥272🫡21❤‍🔥1

19 Jul 2026, 17:41 UTC340 views30 reactionsread 6 August 2026
Forwarded from @ovmbr125Photo

Відзнаки, які носять із гордістю У світлі смолоскипів, під прапорами бригади та підрозділу, бійці ББпС 125-ї ОВМБр отримали нагороди й шеврони. Для Трійки це більше, ніж церемонія. Нагороду отримують за результат. Шеврон — за право бути частиною команди. Долучайся до 125-ї ОВМБр на 125.ab3.army. 125 ОВМБр | Instagram | Facebook | TikTok | Підтримай 125 ОВМБр | Долучитись до 125 ОВМБр | Третій армійський корпус

🔥22❤‍🔥3🫡31🤝1

Showing the 6 most recent of 6 posts we hold for @bbps_125ovmbr. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 6 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 19 September 2026 — this entry's latest reading, not the date you are reading this.

“ББПС 125 ОВМБр” (@bbps_125ovmbr), 1,028 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bbps_125ovmbr.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.