Даров всем , как у вас дела ваще , давно я уде не постил ниче
custom 54742468473986921401

Channel
@superbear777
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
62subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002541337864 |
|---|---|
| Type | Channel |
| Username | @superbear777 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/superbear777 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:04 | 62 | -5 |
| 14 Aug 2026, 21:06 | 67 | +1 |
| 10 Aug 2026, 02:01 | 66 | no change |
| 7 Aug 2026, 16:49 | 66 | first reading |
17 posts held, back to 6 December 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 pageof 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 17 posts for this entry, the most recent from 27 April 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
65 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 27.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5188292086654318827 | 18 | 27.7% | |
| custom 5474313037139690491 | 15 | 23.1% | |
| custom 5188583886732409891 | 12 | 18.5% | |
| custom 5474265981477997049 | 7 | 10.8% | |
| custom 5188193207917230796 | 4 | 6.15% | |
| custom 5474246847398692140 | 4 | 6.15% | |
| custom 5474553877430814627 | 3 | 4.62% | |
| custom 5474250493825924196 | 2 | 3.08% |
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 areTelegram’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 11 of the 17 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 65reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 6 December 2025 to 27 April 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.
Даров всем , как у вас дела ваще , давно я уде не постил ниче
custom 54742468473986921401
Video, posted without a caption
custom 54742468473986921403custom 51882920866543188272
Обломки иранской ракеты пробили крышу веранды возле входа в отель Fairmont The Palm. Со слов туристов, возгорание до сих пор не потушили. Столб чёрного дыма поднялся на сотни метров, его видно из разных районов города. ❗ Подписывайся на Mash в МАХ
custom 51882920866543188275
Очень неожиданно , пво пропустила (ракета попала в в здание)
Ну как бы норм , каждую минуту сбивают (пво)ракеты
custom 54742504938259241962
Photo, posted without a caption
custom 51882920866543188274custom 54742659814779970491
Выборочно дам мишек (кто зайдет по ссылке и скинет скрин в коменты
https://t.me/PlushkaAppBot/Plushka?startapp=r__7969482729
Ну одно и тоже
Всех (мужиков) с 23 февраля
custom 51885838867324098913
Photo, posted without a caption
Photo, posted without a caption
custom 51881932079172307963custom 51882920866543188271
Showing the 12 most recent of 17 posts we hold for @superbear777. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Super bear 777😋” (@superbear777), 62 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/superbear777.
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.