Telegram RegisterThe public register of Telegram
Telegram profile photo for БРОНІК

Channel

БРОНІК

@sbronik

On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

21,960subscribers

+3,122 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003280326782
TypeChannel
Username@sbronik
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/sbronik

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

16,91321,96019,436.56 August 2026 — 18,838 subscribers6 August 2026 — 18,838 subscribers6 August 2026 — 18,837 subscribers7 August 2026 — 18,752 subscribers8 August 2026 — 18,639 subscribers9 August 2026 — 18,499 subscribers10 August 2026 — 18,285 subscribers10 August 2026 — 18,256 subscribers12 August 2026 — 18,245 subscribers12 August 2026 — 18,292 subscribers14 August 2026 — 18,195 subscribers15 August 2026 — 18,071 subscribers16 August 2026 — 17,940 subscribers17 August 2026 — 17,866 subscribers18 August 2026 — 17,843 subscribers19 August 2026 — 17,692 subscribers20 August 2026 — 17,669 subscribers21 August 2026 — 17,686 subscribers23 August 2026 — 17,507 subscribers24 August 2026 — 17,431 subscribers25 August 2026 — 17,391 subscribers26 August 2026 — 17,262 subscribers28 August 2026 — 17,260 subscribers29 August 2026 — 17,201 subscribers29 August 2026 — 17,157 subscribers30 August 2026 — 17,051 subscribers31 August 2026 — 17,036 subscribers1 September 2026 — 16,994 subscribers3 September 2026 — 16,913 subscribers4 September 2026 — 21,960 subscribers6 August 20264 September 2026
30 measurements spanning 29 days, net +3,122. 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 16,156–22,717 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
4 Sept 2026, 08:3621,960+5,047
3 Sept 2026, 00:3716,913-81
1 Sept 2026, 21:2316,994-42
31 Aug 2026, 17:5517,036-15
30 Aug 2026, 20:1217,051-106
29 Aug 2026, 23:3417,157-44
29 Aug 2026, 02:3717,201-59
28 Aug 2026, 00:5617,260-2
26 Aug 2026, 22:4317,262-129
25 Aug 2026, 20:0617,391-40
24 Aug 2026, 20:1317,431-76
23 Aug 2026, 07:5617,507-179
21 Aug 2026, 19:1417,686+17
20 Aug 2026, 16:2317,669-23
19 Aug 2026, 18:2417,692-151
18 Aug 2026, 19:3717,843-23
17 Aug 2026, 21:4817,866-74
16 Aug 2026, 20:5817,940-131
15 Aug 2026, 15:1418,071-124
14 Aug 2026, 01:1818,195first reading

Engagement

213 posts held, back to 3 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.4%
avg views ÷ 21,960 subscribers
Avg views / post
2,720
194 posts measured
Reaction rate
1.30%
reactions ÷ views · ER floor
Posts in window
194
of 213 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 3 September 2026
Posts held213 (3 August 20263 September 2026)
Views total527,784
Reactions total6,848
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 09:35 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
26m 12s
Average length
1m 03s

Measured directly from 25 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

7,259 reactions across 205 posts, in 31 distinct kinds. The most used accounts for 21.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣1,57721.7%
💯1,23016.9%
1,22916.9%
😁1,02814.2%
👍6368.76%
🔥4896.74%
👏3765.18%
🤯2924.02%
🤔560.771%
😡530.73%
😱430.592%
🥰360.496%
🙈310.427%
🌚290.4%
😢270.372%
🙉190.262%
❤‍🔥170.234%
😨160.22%
🏆150.207%
🤷90.124%
11 further kinds510.703%

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

Measured over the 213 most recent posts we hold, published 3 August 2026 to 3 September 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

3 Sept 2026, 09:30 UTC294 views3 reactionsread 3 September 2026

В перервах між стрілянинами в Києві, атаками дронів, кол-центрами, наркотрафіками і боротьбою між ГУР та СБУ, в яку включилися чи не всі провідні медіа (на стороні ГУР, що теж занадто смердить політикою, а не журналістикою), прочитав новину, що Президент запропонував очільнику Запорізької ОДА очолити Агентство відновлення. В цей момент десь тихо зажурився новий Премʼєр-міністр, якого вчергове, як і всіх інших до цьо

2🔥1

2 Sept 2026, 15:14 UTC≈2,030 views15 reactionsread 3 September 2026
Video

Цікаві питання від судді Глотова М.С. та цікаві фрагменти розмов, зафіксовані в результаті ОРЗ, про ймовірний вплив ОП на судову гілку влади.

💯76👏2

2 Sept 2026, 11:25 UTC≈2,290 views12 reactionsread 3 September 2026

Для тих, хто хоче прослухати даний фрагмент, публікую оцифрований ШІ текст. Звертаю увагу, що голоси та окремі слова спотворені саме інструментом.

😁74👏1

2 Sept 2026, 11:24 UTC≈2,270 views10 reactionsread 3 September 2026
File

File, posted without a caption

🔥5😁5

2 Sept 2026, 11:06 UTC≈2,420 views52 reactionsread 3 September 2026

Таким чином, з наведеного вбачається, що ймовірно Железняк, у розпорядженні якого були матеріали кримінального провадження у справі МіндічГейту, вирішив допомогти Мудрій та Микитасю усунути з посади Ігоря Поночовного. З цією метою 10.12.2025 він, діючи без дозволу слідчого та прокурора у провадженні, скинув Мудрій фрагмент відповідного протоколу і вже наступного дня, діючи за її вказівкою, почав публікувати інформац

💯20👍147🤔4🤨4🤯2🔥1

2 Sept 2026, 10:57 UTC≈2,280 views21 reactionsread 3 September 2026
Photo

19.12.2025 продовжує публікації щодо Білоуса.

🤯16😁41

2 Sept 2026, 10:56 UTC≈2,250 views28 reactionsread 3 September 2026
Photo

Що робить наш "опозиціонер"? Вже наступного дня, тобто 11.12.2025 починає виконувати вказівку Мудрої

😱16🤯5💯4🔥3

2 Sept 2026, 10:56 UTC≈2,280 views25 reactionsread 3 September 2026

Отже, 10.12.2025 Железняк під час засідання ТСК скинув Мудрій повідомлення про те, що на плівках Міндіча згадується Білоус (на той час заступник Міністра юстиції) та переслав відповідний фрагмент протоколу НСРД. Мудра обговорює це з Микитасем і вказує, що на її прохання Железняк оприлюднить інформацію щодо Білоуса. У свою чергу це дасть підставу звільнити Поночовного (керівника Офісу протидії рейдерству Мін'юсту),

🔥19👏3🙈2😨1

2 Sept 2026, 10:50 UTC≈3,970 views32 reactionsread 3 September 2026

Отже, розмова між Микитасем та Мудрою 10.12.2025 Микитась М.В. – Котик, котик, котик, у меня честно корыстный интерес. Ты знаешь же ж, для тебя и для меня. У меня чисто корыстный интерес. По всей этой ситуации. Мудра І.Р. – Ну ты ж знаешь, мою позицию. Лучше это сделать не моими руками. Микитась М.В. – Ну конечно, не твоими руками это будет сделано. Мудра І.Р. – Да. Микитась М.В. – Вот я это сделаю. Вот я это сд

🔥1783🌚3😱1

2 Sept 2026, 10:02 UTC≈2,290 views19 reactionsread 3 September 2026

Відомості про те, що і кому скидав Железняк 10.12.2025 зафіксовано в протоколі про результати ОРЗ - аудіо контролю особи від 16.02.2026. Так у протоколі зафіксовано розмову по телефону Микитася М.В. з Мудрою І.Р., яка мала місце 10.12.2025 у період часу з 13:41 до 13:44.

🌚106😁3

2 Sept 2026, 09:58 UTC≈2,270 views15 reactionsread 3 September 2026
Video

В ході засідання ТСК 10.12.2025 Железняк з кимось активно переписується. Під час розслідування справи Форест Гамп слідство встановило з ким все таки він переписувався і з якого приводу.

🔥76👏2

2 Sept 2026, 09:55 UTC≈2,050 views5 reactionsread 3 September 2026
Photo

Повертаючись до теми Железняка. 10 грудня 2025 року відбулось засідання ТСК по "МіндічГейту", яке у своєму каналі анонсував Железняк. Засідання розпочалось о 10:10 і тривало 3 години 16 хвилин. (Тобто завершилось приблизно о 13:30).

👍41

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

Posts edited after publishing

@sbronik edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
10 August 2026

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

“БРОНІК” (@sbronik), 21,960 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/sbronik.

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.