21 Nov 2025, 09:31 UTC199 viewsread 31 August 2026
Кф закрыт, братство/союз разрыв, патент за нами, мы еще вернемся.😤
Channel
BEGNAROVY
@B8GNAROVY
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003278474047 |
|---|---|
| Type | Channel |
| Username | @B8GNAROVY |
| Description | закрыты |
| Created | 28 October 2025 — measured — dated from the channel’s first post |
| First recorded | 31 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/B8GNAROVY |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 00:00 | 4 | no change |
| 30 Aug 2026, 23:45 | 4 | first reading |
Engagement
8 posts held, back to 28 October 2025 — the 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 8 posts for this entry, the most recent from 21 November 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 31 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
36 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 19.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5352562937775018091 | 7 | 19.4% | |
| custom 5377616830632323244 | 7 | 19.4% | |
| custom 5352782255985019884 | 5 | 13.9% | |
| custom 5323591824290374223 | 4 | 11.1% | |
| custom 5390872680255747881 | 4 | 11.1% | |
| custom 5194990337260534401 | 3 | 8.33% | |
| custom 5391300746761240796 | 3 | 8.33% | |
| custom 5442742738296529848 | 3 | 8.33% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 8 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 28 October 2025 to 21 November 2025, 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
17 Nov 2025, 18:03 UTC227 views2 reactionsread 31 August 2026
Sticker
Sticker, posted without a caption
custom 53525629377750180912
5 Nov 2025, 15:15 UTC616 views4 reactionsread 31 August 2026
Все посты братство и остальные находиться в архиве
custom 53776168306323232442custom 53527822559850198841custom 53908726802557478811
5 Nov 2025, 12:06 UTC559 views1 reactionsread 31 August 2026
Sticker
Sticker, posted without a caption
custom 53525629377750180911
5 Nov 2025, 11:47 UTC685 views6 reactionsread 31 August 2026
по поводу братства писать - @kazznm перед заключением братства ознакомьтесь с правилами
custom 51949903372605344012custom 53776168306323232442custom 53527822559850198841custom 54427427382965298481
28 Oct 2025, 18:50 UTC747 views13 reactionsread 31 August 2026
PATENT⛔ starting from 21.08.25 name "Begnarovy" belongs to us. If we find a similar name or our KF name being used, we will take appropriate measures.🤩
custom 53525629377750180912custom 53527822559850198842custom 53776168306323232442custom 53908726802557478812custom 53913007467612407962custom 51949903372605344011custom 53235918242903742231custom 54427427382965298481
28 Oct 2025, 18:39 UTC814 views10 reactionsread 31 August 2026
Photo
✨🤩elcome to ⭐️⭐️⭐️❤️ BEGNAROVY🎁 sometimes, the universe whispers instead of shouting. ПАХАН ✅
custom 53235918242903742233custom 53525629377750180912custom 53527822559850198841custom 53776168306323232441custom 53908726802557478811custom 53913007467612407961custom 54427427382965298481
28 Oct 2025, 14:10 UTCviews —
Channel created
Showing the 8 most recent of 8 posts we hold for @B8GNAROVY. 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 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“BEGNAROVY” (@B8GNAROVY), 4 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/B8GNAROVY.
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.