Channel
@StopBums
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
63subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002529395604 |
|---|---|
| Type | Channel |
| Username | @StopBums |
| Description | Нас обманули. Теперь мы объединяемся. BUMS — это скам. Airdrop не состоялся, правила меняются, запущено нелегальное казино. Здесь — доказательства, новости и чат пострадавших. Присоединяйтесь. Помогите остановить это. |
| 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 | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/StopBums |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 03:31 | 63 | no change |
| 7 Aug 2026, 16:16 | 63 | first reading |
14 posts held, back to 9 August 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 14 posts for this entry, the most recent from 7 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
Measured directly from 1 video 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.
12 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 100.0% |
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 1 of the 14 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 12reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 9 August 2025 to 7 March 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.
Уважаемый господин Дуров, @monk @unbrokensociety @crow Мы обращаемся к Вам от лица сообщества пострадавших пользователей проекта BUMS (@bums). Этот проект получил доверие огромного числа людей во многом благодаря публикациям на Вашем личном Telegram-канале. Для аудитории это стало прямым сигналом, что проект заслуживает внимания и доверия. Речь, в частности, идёт о следующих публикациях: https://t.me/durov/373 htt…
❤12
❌ Вам отказали в раздаче аирдропа за публикацию скриншота чата с целью нас уничтожить! 💬 Такое сообщение получил наш подписчик от службы поддержки BUMS, за то, что разместил в небольшом чате скрин с их перепиской. В скриншоте не было никакой дискредитирующей информации. Там они пишут, что объявление аирдропа будет в третьем квартале. При этом человек задонатил в игру более 2000$. ❓ BUMS вы охренели? Собрали миллион…
❗️Bums и FomoHash, листинг или последний сбор перед закатом? Оба проекта ожили и начали готовить якобы долгожданный листинг спустя год. Я уже не раз писал, что ВЕРЫ НЕТ, перестаньте кормить их донатами. Если у них действительно есть планы на листинг, значит просто ждем. Но без каких-либо заносов наших денег. Мы сразу перестали играть и донатить, как только они объявили второй сезон вместо обещанного листинга. Но …
Хронология проекта BUMS 06.09.2024 — создан канал BUMS. 08.09.2024 — опубликован первый пост. 11.09.2024 — стартовала игра. 15.09.2024 — объявлено о 2 млн игроков. 16.09.2024 — заявлено, что токен будет запущен на TON. 22.09.2024 — упоминание CoinMarketCap. 23.09.2024 — объявлено о 7 млн игроков. 30.09.2024 — объявлено о 10 млн игроков. 03.10.2024 — получена верификация в X и YouTube. 03.10.2024 — появляется bums_ch…
Этот человек работал HR’m в компании TONBOX и нанимал сотрудников для разработки. Офис у них в Питере, при необходимости можно будет ее допросить если дело все-таки заведут. https://m.vk.com/ishtochek
Наши данные указывают на участие @TonBox в продвижении проектов @Corn, @Boom, @Bits, @Agent301bot и @bums (совпадения username, единые связки каналов/чатов, админские роли, инфраструктурные пересечения). Сообщество считает эти проекты мошенническими.
@TonBox — сервис качественного трафика и консультаций. @Bits, @Boom, @Corn, @Agent301bot, @bums — это всё мы. 🤑 — более 58 млн пользователей — более 12,6 млн DAU Тарифы (зависят от объёма закупки): • 20 000 — $0.035 • 100 000 — $0.03 • 1 000 000 — $0.027 Индивидуальные условия: таргетинг, премиальная аудитория, устройства. По всем вопросам — в TG: @TonBoxMarketing.
и @mrkt
Photo, posted without a caption
Один и тот же сервер используется у @corn и @treasury_official_bot
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 14 posts we hold for @StopBums. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“StopBums” (@StopBums), 63 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/StopBums.
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.