Channel
@blacklist_migalki
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
49subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001490116869 |
|---|---|
| Type | Channel |
| Username | @blacklist_migalki |
| Description | Информация о кидалах и мошенниках форума Migalki.plus🚨 |
| Created | 17 January 2021 — measured — dated from the channel’s first post |
| First recorded | 25 September 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/blacklist_migalki |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 03:22 | 49 | first reading |
11 posts held, back to 17 January 2021 — 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 11 posts for this entry, the most recent from 25 August 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 25 September 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.
👤 Ник в Telegram └ Aurora 🆔 ID Telegram └ 5481138848 📱 Имя пользователя └ @auroraaaaaaa123 🔗 Ссылка на ник └ https://t.me/auroraaaaaaa123 📝 Описание претензии └ Предложение стороннего гаранта, попытка скама ⏳ Решение └ 🚷Забанен🚷 📋 Подробнее └ https://t.me/MigalkiPlusChat/23381?single
👤 Ник в Telegram └ https://t.me/migalkiplus 🆔 ID Telegram └ 5042708265 📱 Имя пользователя └ @migalkiplus 📝 Описание претензии └ Фейковый гарант, кидает на деньги
👤 Имя пользователя в Telegramm └ https://t.me/@puzzleio 🆔 ID Telegramm └ 5101717763 📱 Ник пользователя └ PUZZLE [911]re 📝 Описание претензии └ Скаммер. Удалил всю переписку. Гаситься за копейки. Ущерб 20$ ⏳ Решение └ 🚷Забанен🚷
👤 Ник в Telegramm └ https://t.me/VinceOne 🆔 ID Telegramm └ 592105077 📱 Имя пользователя └ @VinceOne 📝 Описание претензии └ Взял оплату и начал кормить "завтраками" ⏳ Решение └ 🚷Забанен🚷
👤 Ник в Telegramm └ https://t.me/ChiTok22 🆔 ID Telegramm └ 1947911174 📱 Имя пользователя └ @ChiTok22 📝 Описание претензии └ Скамит на BTC ⏳ Решение └ 🚷Забанен🚷
👤 Ник в Telegramm └ https://t.me/TakeItEasy_Now 🆔 ID Telegramm └ 1921787505 📱 Имя пользователя └ @TakeItEasy_Now 📝 Описание претензии └ Взял предоплату за рассылку по каналам Телеграмм и пропал ⏳ Решение └ 🚷Не рекомендуется работать с данным персонажем🚷
👤 Ник в Telegram └ https://t.me/Elenaportu 🆔 ID Telegram └ 1028816109 📱 Имя пользователя └ @Elenaportu 📝 Описание претензии └ Продает нарисованые "пробивы" ⏳ Решение └ 🚷Забанен🚷
👤 Ник в Telegram └ cocos 🆔 ID Telegram └ 1484463082 📱 Имя пользователя └ @uqjshsh7 📝 Описание претензии └ Кидает на документы ⏳ Решение └ 🚷Забанен🚷
⠀ ⏳ Решение └ 🚷Забанен🚷 👤 Ник на форуме └ Hack-Mail 📱 Контакты └ [email protected]
⚖️ Арбитраж └ от 02.01.2021 👤 Ник на форуме └ Hack-Mail 📇 Профиль ответчика └ http://migalki.plus/forum/members/hack-mail.566/ 📱 Контакты └ [email protected] 📝 Описание претензии └ Заказ селлеру обойти двойную верификацию в gmail и предоставить доступ в почту. Селлер обещал предоставить доступ к почте за 10 000 р, в течении 1-3 дней. Все данные включая логин и пароль от почты были переданы селлеру + пр…
Channel created
Showing the 11 most recent of 11 posts we hold for @blacklist_migalki. 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.
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.
@blacklist_migalki named 2 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“🚷 Черный список Migalki.plus” (@blacklist_migalki), 49 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/blacklist_migalki.
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.