Telegram RegisterThe public register of Telegram

Channel

Bochkala_WAR

@bochkala_war

Verified by Telegram

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

40,399subscribers

-317 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001677003375
TypeChannel
Username@bochkala_war
Created4 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/bochkala_war

Growth

40,39940,71640,557.56 August 2026 — 40,716 subscribers6 August 2026 — 40,716 subscribers6 August 2026 — 40,679 subscribers7 August 2026 — 40,635 subscribers8 August 2026 — 40,616 subscribers9 August 2026 — 40,596 subscribers10 August 2026 — 40,549 subscribers11 August 2026 — 40,526 subscribers12 August 2026 — 40,501 subscribers13 August 2026 — 40,449 subscribers14 August 2026 — 40,399 subscribers6 August 202614 August 2026
11 measurements spanning 9 days, net -317. 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 40,351–40,764 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:0840,399-50
13 Aug 2026, 04:0440,449-52
12 Aug 2026, 06:3240,501-25
11 Aug 2026, 02:5740,526-23
10 Aug 2026, 03:5840,549-47
9 Aug 2026, 05:5140,596-20
8 Aug 2026, 04:5440,616-19
7 Aug 2026, 07:0040,635-44
6 Aug 2026, 09:3040,679-37
6 Aug 2026, 01:4840,716no change
6 Aug 2026, 00:5640,716first reading

Engagement

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

ERR · 30 days
29.2%
avg views ÷ 40,399 subscribers
Avg views / post
11,800
57 posts measured
Reaction rate
1.00%
reactions ÷ views · ER floor
Posts in window
59
of 59 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held59 (4 August 202614 August 2026)
Views total673,430
Reactions total6,737
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 12:55 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
14m 12s
Average length
1m 06s

Measured directly from 13 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

5,411 reactions across 46 posts, in 31 distinct kinds. The most used accounts for 35.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,92135.5%
👍84315.6%
82815.3%
🤬59911.1%
🙏3476.41%
💔1763.25%
🤣1232.27%
😢861.59%
🤔821.52%
👏781.44%
🤯761.40%
😁561.03%
🤮490.906%
🥰350.647%
🤷‍♂220.407%
💯160.296%
🖕160.296%
😱130.24%
🎉110.203%
💩100.185%
11 further kinds240.444%

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 57 of the 59 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 6,737reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 59 most recent posts we hold, published 4 August 2026 to 14 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

14 Aug 2026, 11:19 UTC≈1,160 views56 reactionsread 14 August 2026
Photo

мо рф vs стратком ЗСУ https://t.me/bochkala_war

32💯16🔥7💊1

13 Aug 2026, 18:04 UTC≈3,840 views146 reactionsread 14 August 2026

‼️ «Скеля» переходить під оперативне керівництво корпусу «Азов» — начальник відділення комунікацій 425-го ОШП Олексій Братущак. https://t.me/bochkala_war

👍12514🤔6🖕1

13 Aug 2026, 14:27 UTC≈3,480 views248 reactionsread 14 August 2026
Photo

Вони знали про наближення «Шахеда», знали, що його ціллю є локомотив. Вони оголосили евакуацію, повели потяг до найближчої станції, щоб зупинити його та евакуювати людей найбільш безпечно там. Хоча самі мали можливість у будь-який момент покинути поїзд. Реактивний «Шахед» поцілив прям у кабіну за хвилину до повної зупинки. Всіх пасажирів врятували та доправили до місць призначення, хлопці ж загинули на місці… htt

💔176🤬37😢293🎉1🤔1🤣1

13 Aug 2026, 11:07 UTC≈3,300 views101 reactionsread 14 August 2026
Photo

СБУ викрила агентів гру рф, які «полювали» на винищувачі F-16 та Mirage 2000 Військова контррозвідка СБУ за особистої координації очільника Служби Олександра Поклада нейтралізувала агентурну мережу гру, яка планувала ракетний обстріл авіаційних баз ЗСУ. До групи входили 14 людей із різних регіонів України. Агенти фотографували українські аеродроми, літаки F-16 та Mirage 2000, екіпажі й техперсонал, а також збирали

👍81😱113🤣3🤬2🔥1

13 Aug 2026, 05:56 UTC≈3,240 views148 reactionsread 14 August 2026
Photo

Від "обломків" БпЛА загорівся Салаватський нафтопереробний завод «Газпром нафтохім Салават» — один із найбільших на рашці нафтопереробних та нафтохімічних комплексів. https://t.me/bochkala_war

👍78🔥5810😁2

12 Aug 2026, 20:48 UTC≈3,660 views195 reactionsread 14 August 2026
Photo

Карта звільнених населених пунктів 🇺🇦 https://t.me/bochkala_war

138🙏43👍6🤣5🤔2🦄1

12 Aug 2026, 16:54 UTC≈3,860 views77 reactionsread 14 August 2026
Photo

Коментар речника Повітряних Сил стосовно ранкових зведень по балістиці 🤷‍♂️ https://t.me/bochkala_war

33🤷‍♂22🤔14🤣6🔥1🤬1

12 Aug 2026, 14:16 UTC≈3,890 views171 reactionsread 14 August 2026
Photo

ЗСУ під час наступальної операції на Олександрівському напрямку звільнили 745 км² території та 26 населених пунктів. Про це 12 серпня повідомив Президент Володимир Зеленський. Операція тривала із січня по серпень 2026 року. За цей час українські військові завдали значних втрат російському угрупованню. «Завдяки активним діям наших військ вдалося суттєво вдарити по окупаційному контингенту. Російські втрати склали щ

110👍36🔥8🙏6🤣4🤯3🥰2💩1

12 Aug 2026, 09:53 UTC≈3,680 views58 reactionsread 14 August 2026
Forwarded from @stopcorPhoto

🎉 11 років «Стоп корупції»: від перших журналістських розслідувань — до всеукраїнського руху. За цей час ми пройшли великий шлях. Викривали корупційні схеми та зловживання посадовців, захищали права громадян, розширювали мережу осередків і об’єднували навколо спільної мети журналістів, активістів, юристів та правозахисників з усієї України. Були тиск, погрози та спроби дискредитації — але вони не змусили нас зупинит

👍497🤣2

10 Aug 2026, 12:07 UTC≈4,000 views190 reactionsread 14 August 2026
Photo

Тобольськ 🔥 https://t.me/bochkala_war

🔥12550👏11👍4

10 Aug 2026, 10:20 UTC≈4,130 views150 reactionsread 14 August 2026
Photo

18-річний лейтенант адамкаДиров 💩 https://t.me/bochkala_war

🤣92🤮47💩9👎1😁1

10 Aug 2026, 10:07 UTC≈4,170 views115 reactionsread 14 August 2026
Photo

🛑 Нацполіція та СБУ викрили схему реєстрації терміналів супутникового зв'язку для окупантів Правоохоронці встановили основних учасників злочинної групи, які підшуковували громадян для оформлення терміналів, а також понад десяток осіб, які здійснили їх реєстрацію без фактичного отримання обладнання. Серед завербованих переважно жителі Житомира. Вербування відбувалося через Telegram, зареєстрований на території росії

🤬95👍153🔥1🤣1

Showing the 12 most recent of 59 posts we hold for @bochkala_war. 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.

Citation-graph rank

Citation-graph rank — 24,380 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Анатолій Штефан "Штірліц"
@a_shtirlitz · 139,761
Telegram ranks this channel #76 of 86 here — alongside 85 others — read 13 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

2 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Бочкала Роман Олександрович (uk.wikipedia.org)
“…* Офіційний [https://t.me/bochkala_war Telegram-канал] {{Webarchive|url=https://web.archive.org/web/20220504212803/https://t.me/bochkala_war |date=4 травня…”
read 9 August 2026
Мі-35М (uk.wikipedia.org)
“…сили України|ЗС України]]{{Cite web|title=Bochkala_WAR|url=https://t.me/bochkala_war/5773?single|website=Telegram|accessdate=2022-05-30}} Потім…”
read 9 August 2026

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Bochkala_WAR” (@bochkala_war), 40,399 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/bochkala_war.

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.