Так как к нему обращаться?
- Илья22%
- Евгений4%
- Руслан4%
- Кидорас69%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Channel
@RocketUP_BL
On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
16subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001477335059 |
|---|---|
| Type | Channel |
| Username | @RocketUP_BL |
| Description | ©️ @RocketUP |
| Created | 14 December 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/RocketUP_BL |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 21:15 | 16 | no change |
| 6 Aug 2026, 22:02 | 16 | first reading |
20 posts held, back to 16 January 2020 — 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 20 posts for this entry, the most recent from 20 June 2020. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
Так как к нему обращаться?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
@Semerezow - новый аккаунт, будьте осторожны, старый его аккаунт получил метку SCAM (https://t.me/Podborkioff/41)
Ботоводы История от подписчика: Я создатель канала Blockchain Magazine. Интересная история как я попал на 100к. Ниже вся история. Так же я отправил это в техподдержку телеграм для выдачи метки. Расскажи пожалуйста об этой истории. Я не надеюсь вернуть деньги, просто хочу, чтобы меньше людей попалось на этих мошенников. Доказательства мошенничества. #ботоводы
Реквизиты мошенников! Уже два случая!
+79638957792
Обратите внимание, какой хитрый поганец! Вторая буква в его юзернейме - i большая, поэтому она неотличима от нашей L маленькой!
Вас интересует реклама ?) делаем место со скидкой вам) Канал: https://t.me/karaulny_accountant Ваш пост делаем под закуп, чтобы приход был максимальным, целевая аудитория у меня активная, приход вас порадует. Извините если побеспокоил вас)
👎💩‼️Внимание! Это мошенники, мы ничего не предлагаем сами. Редакция @karaulny_accountant просит максимального репоста и ваших жалоб на аккаунт мошенника.
ОЧЕРЕДНОЙ ФЕЙК! • Имя | Юзернейм: (на момент публикации этого поста) Nikolay Creator | @Nlkoiay_Creator • ID: 1049489019 • Причина занесения в ЧС: Подделка аккаунта под @Nikolay_Creator. Всегда проверяйте в описании каналов! • Пруфы
ОСТОРОЖНО ФЕЙКИ! • Имя | Юзернейм: (на момент публикации этого поста) Помощник Депутата | @dejog Economika Support | @economlka_support • ID: 797299137 634481530 • Причина занесения в ЧС: Подделка аккаунта под @depgd, @economika_support. Всегда проверяйте в описании каналов! • Реквизиты: 4890494696248475 5599005023024982 5469330013950617 Андрей Юрьевич Т. • Пруфы
@speciall_team продолжают свою деятельность. Дело в том, что они пообещали выпустить подборку сегодня, ту которую не сдеали, но оплату получили. Но в итоге просто игнор и никакого манибека. Пруфы
Мошенник @borez – создатель канала о мошенниках @kidalobnal . Гениально! До недавнего времени (до кидка) наш канал тесно сотрудничал с админом. Пять дней назад ко мне обратился подписчик, которого данный человек по его словам кинул на крупную сумму. Историю этой ситуации и её развитие мне обещали скинуть чуть позже, разместим в нашем чате или канале. Ответа на запрос о том, что случилось от «мошенника» не последо…
Showing the 12 most recent of 20 posts we hold for @RocketUP_BL. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Так как к нему обращаться?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 16 January 2020 to 20 June 2020. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
@RocketUP_BL named 14 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“❌Сомнительные админы, каналы и проекты по подборкам❌” (@RocketUP_BL), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/RocketUP_BL.
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.