Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 81% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
32 measurements spanning 42 days, net +14,696. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)
Subscribers
Change
18 Sept 2026, 13:57
37,587
+37,558
17 Sept 2026, 13:01
29
-21,428
16 Sept 2026, 02:58
21,457
+150
14 Sept 2026, 12:56
21,307
+50
13 Sept 2026, 20:52
21,257
+21,252
9 Sept 2026, 22:41
5
-22,586
6 Sept 2026, 15:00
22,591
-39
4 Sept 2026, 03:16
22,630
-13
2 Sept 2026, 19:33
22,643
-12
1 Sept 2026, 20:38
22,655
-8
31 Aug 2026, 23:38
22,663
-7
30 Aug 2026, 21:39
22,670
-12
29 Aug 2026, 22:32
22,682
-12
28 Aug 2026, 19:04
22,694
+1
27 Aug 2026, 20:54
22,693
-2
26 Aug 2026, 21:55
22,695
-18
26 Aug 2026, 01:05
22,713
-7
24 Aug 2026, 22:23
22,720
-18
23 Aug 2026, 06:27
22,738
-24
21 Aug 2026, 20:08
22,762
first reading
Engagement
49 posts held, back to 3 July 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 69 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
5.57%
avg views ÷ 37,587 subscribers
Avg views / post
2,090
28 posts measured
Reaction rate
0.884%
reactions ÷ views · ER floor
Posts in window
28
of 49 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 27 of 28 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 24 September 2026
Posts held
49 (3 July 2025 – 24 September 2026)
Views total
58,620
Reactions total
499
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
24 Sept 2026, 13:09 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
302
Videos
67
Links
365
Lifetime counters from Telegram’s own channel header, read 24 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.
Video runtime
1m 19s
Average length
40s
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.
Reaction mix
725 reactions across 47 posts, in 19 distinct kinds. The most used accounts for 20.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😁
149
20.6%
❤
147
20.3%
🤡
146
20.1%
👍
65
8.97%
🤬
51
7.03%
❤🔥
47
6.48%
😱
30
4.14%
🔥
18
2.48%
🎉
17
2.34%
👎
17
2.34%
🤯
11
1.52%
💯
8
1.10%
👌
7
0.966%
🏆
4
0.552%
☃
3
0.414%
🗿
2
0.276%
🎅
1
0.138%
😍
1
0.138%
😐
1
0.138%
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 47 of the 49 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 725 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 49 most recent posts we hold, published 3 July 2025 to 24 September 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.
Telegram Stars
Stars received
6
across the posts below
Posts paid on
3
of 49 we hold a reading for · 6%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @blokirovki_interneta. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 49 most recent posts we hold for this entry, published 3 July 2025 to 24 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🫢 Google взял на себя роль РКН
Пока у нас ограничивают зарубежные сервисы, Google может затруднить установку уже российских приложений на Android
🛒 Причина — новая система верификации. Но в первую очередь под ударом окажутся приложения, уже удалённые из Google Play
Так что лучше проверьте, все ли ваши родственники уже освоили VPN
А то с таким давлением с обоих сторон скоро новости им придётся узнавать из газет 🤷…
🌐 539 сетевых сбоев за неделю
Начало сентября выдалось неспокойным для интернета по всему миру
Только с 7 по 13 сентября Cisco ThousandEyes насчитала 539 сетевых сбоев
Проблемы возникали у провайдеров, облачных платформ, DNS и CDN. Иногда одного сбоя хватало, чтобы доступ к сервисам пропал у пользователей в нескольких странах
Даже непривычно, что интернет может не работать не из-за проделок РКН 😶
🇷🇺 Узнавай о бл…
🙄 Белые списки с нами навсегда
Ограничения мобильного интернета могут сохраниться после завершения СВО, считает руководитель IT-агентства «ЮзерТеч»
Вместо оттепели он ожидает продолжение движения по китайской модели контроля с белыми списками и жёсткой привязкой SIM-карт к личности через Госуслуги
Только в «китайской модели» сначала развивали конкурентоспособные аналоги, а потом всё блокировали. У нас эту часть, п…
🤪 YouTube внезапно оказался незаменимым
Депутат Свинцов признал, что полностью отказаться от YouTube в ближайшие два года не получится
У VK Видео и Rutube недостаточно контента для полноценной замены. А полный отказ от YouTube сейчас, по его словам, был бы неправильным с точки зрения интересов пользователей
Что-то об этих интересах не вспоминали, когда всё блокировали. А провал блокировок теперь оправдывают забото…
🪑 На блокировках не экономят
Минцифры предлагает разрешить Главному радиочастотному центру (ГРЧЦ), подведомственному Роскомнадзору, не перечислять в бюджет половину годовой прибыли
Вместо этого деньги хотят направить на закупку оборудования для усиления блокировок в Рунете
Удивляет больше не сама новость, а что у ГРЧЦ есть хоть какая-то прибыль 😀
🇷🇺 Узнавай о блокировках первым.
🫣 Импортозамещение: итоги
Россияне стали смотреть YouTube на 24% дольше, несмотря на замедление
В первом полугодии среднее время просмотра достигло 99 минут в день на пользователя, Rutube тем временем стали смотреть меньше
Видимо, отвалившиеся после первых ограничений пользователи наконец освоили VPN, и интерес к отечественным «аналогам» магическим образом пропал 🙄
🇷🇺 Узнавай о блокировках первым.
🤡 РКН СПАС ЭТИ ВЫБОРЫ
Роскомнадзор отчитался об отражении свыше 3 000 DDoS-атак на инфраструктуру выборов.
Под удар попали сайты ЦИК, Госуслуг, федеральное и московское электронное голосование, а также ЕСИА и системы московского ДИТ.
🇷🇺 Узнавай о блокировках первым.
👀 Единая Россия набирает рекордные 57% после подсчёта свыше 90% бюллетеней.
Это значит, что партия сможет принимать законы без голосования других фракций, преодолевать вето президента и самостоятельно вносить изменения в Конституцию.
Лучший ВПН
🤦♂️ 5G БУДЕТ К 2030-му?
По прогнозу аналитика Эльдара Муртазина, доступ к 5G у 80% россиян появится только в 2030–2031 годах
Сейчас сеть запущена в 16 городах, до конца года прорабатывают запуск ещё в 50
Для подключения нужен совместимый смартфон и покрытие, а доступ на iPhone зависит от решения Apple
Главное, чтобы к этому времени хоть один незаблокированный сайт остался 👍
🇷🇺 Узнавай о блокировках первым.
🏬 App Store пал следом
Пользователи в РФ жалуются на неработающий App Store
У одних магазин вообще не открывается, у других приложения еле скачиваются
Причина проблем пока неизвестна.
Но с VPN доступ магическим образом возвращается
🇷🇺 Узнавай о блокировках первым.
‼️ DEEPSEEK УМЕР В РОССИИ
Пользователи массово жалуются, что с 7:00 DeepSeek перестал загружаться и отвечать на запросы
Предварительно, проблема касается только браузерной версии нейросети. За пределами РФ аналогичных сбоев не зафиксировано
А у вас работает?
👍 — да, всё стабильно
👎 — не работает
🗳 Хочешь голосовать? Выключи-ка VPN
На сайте электронного голосования в Москве обнаружили необычную проверку. Перед входом браузер пытается загрузить картинку с YouTube
🤐 Если она открывается, система считает это признаком включённого VPN. Результат проверки отправляется на сервер, после чего пользователь авторизуется через mos_ru
После выборов введут штрафы за VPN и задним числом всех оштрафуют? 😁
🇷🇺 Узнавай о …
🤡11😱1
Showing the 12 most recent of 49 posts we hold for @blokirovki_interneta. 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.
Mentions
Named by 3 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.
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.
Handles this channel named that no longer answer
Dead references
12
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
12
vacant every time we have ever looked
@blokirovki_interneta named 12 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@an3go named in 7 posts, 8 August 2026 – 18 August 2026
@devov080 named in 7 posts, 8 August 2026 – 18 August 2026
@dynayka named in 7 posts, 8 August 2026 – 18 August 2026
@evelonegift named in 7 posts, 8 August 2026 – 18 August 2026
@heliman8 named in 7 posts, 8 August 2026 – 18 August 2026
@ivnx111 named in 7 posts, 8 August 2026 – 18 August 2026
@kabanchik_acer named in 7 posts, 8 August 2026 – 18 August 2026
@konstuctor1337 named in 7 posts, 8 August 2026 – 18 August 2026
@kst_rapinthekitchen named in 7 posts, 8 August 2026 – 18 August 2026
@mandarin79 named in 7 posts, 8 August 2026 – 18 August 2026
@rom4gamz named in 7 posts, 8 August 2026 – 18 August 2026
@yarikfokusnik named in 7 posts, 8 August 2026 – 18 August 2026
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“Блокировки Интернета 🚫” (@blokirovki_interneta), 37,587 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/blokirovki_interneta.
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.