Posted without readable text

Channel
ДЕРЗКИЙ КВАДРАТ 18+
@derzkiy_kvadrat
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
27,746subscribers
-990 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001864387035 |
|---|---|
| Type | Channel |
| Username | @derzkiy_kvadrat |
| Description | Дерзко, актуально и 24 на 7 мы рассказываем о событиях на нашем безумном шарике! Реклама напрямую @powerlitel А+ https://gosuslugi.ru/snet/68d536e0bc730f442ab21a50 Реклама через Биржу https://telega.in/c/+I9xSeMlM4xdkNDQy |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 41 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/derzkiy_kvadrat |
Topic
Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Oct 2026, 22:36 | 27,746 | -4 |
| 17 Oct 2026, 22:21 | 27,750 | -15 |
| 16 Oct 2026, 22:26 | 27,765 | -11 |
| 15 Oct 2026, 21:26 | 27,776 | -28 |
| 14 Oct 2026, 19:20 | 27,804 | -24 |
| 13 Oct 2026, 13:09 | 27,828 | -31 |
| 9 Oct 2026, 11:15 | 27,859 | -39 |
| 5 Oct 2026, 04:58 | 27,898 | -36 |
| 28 Sept 2026, 17:59 | 27,934 | -85 |
| 18 Sept 2026, 00:20 | 28,019 | -22 |
| 15 Sept 2026, 21:02 | 28,041 | -35 |
| 14 Sept 2026, 02:02 | 28,076 | -25 |
| 12 Sept 2026, 08:18 | 28,101 | -36 |
| 10 Sept 2026, 03:22 | 28,137 | -54 |
| 6 Sept 2026, 21:15 | 28,191 | -64 |
| 4 Sept 2026, 04:41 | 28,255 | -13 |
| 2 Sept 2026, 21:44 | 28,268 | -27 |
| 1 Sept 2026, 16:56 | 28,295 | -33 |
| 31 Aug 2026, 14:03 | 28,328 | -13 |
| 30 Aug 2026, 17:24 | 28,341 | first reading |
Engagement
772 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 108 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.47%
- avg views ÷ 27,746 subscribers
- Avg views / post
- 408
- 368 posts measured
- Reaction rate
- 0.779%
- reactions ÷ views · ER floor
- Posts in window
- 368
- of 772 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 107 of 368 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 19 October 2026 |
|---|---|
| Posts held | 772 (6 August 2026 – 19 October 2026) |
| Views total | 150,227 |
| Reactions total | 354 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Oct 2026, 02:20 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
- ≈5,280
- Videos
- ≈7,670
- Links
- ≈8,220
Lifetime counters from Telegram’s own channel header, read 19 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 2h 10m
- Average length
- 30s
Measured directly from 260 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
991 reactions across 228 posts, in 13 distinct kinds. The most used accounts for 22.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 224 | 22.6% | |
| 🤡 | 191 | 19.3% | |
| 👍 | 149 | 15.0% | |
| 👎 | 79 | 7.97% | |
| 🔥 | 67 | 6.76% | |
| 🤣 | 56 | 5.65% | |
| 🗿 | 52 | 5.25% | |
| 😁 | 46 | 4.64% | |
| 🤮 | 46 | 4.64% | |
| 🤬 | 34 | 3.43% | |
| 😢 | 30 | 3.03% | |
| 😱 | 16 | 1.61% | |
| 🤔 | 1 | 0.101% |
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 264 of the 772 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 991 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 772 most recent posts we hold, published 6 August 2026 to 19 October 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.
Recent posts
— «Стыд и срам бегать в таких коротких шортах! Тьфу!» Прохожая сделала замечание девушке, которая бегала по улице в настолько коротких шортах, что те напоминали по её мнению трусы. В ответ девушка заявила, что бегать в такой одежде удобно, в отличие от шароваров. Что думаете? ❤️ - нормальные шорты 👎🏻 - короткие 📱 Мы в мессенджере МАКС
❤4
‼️ Робот-пылесос Xiaomi УНИЧТОЖИЛ КВАРТИРУ в Татарстане — робот загорелся на зарядной станции и за несколько минут сжёг всё вокруг Дома в этот момент была только собака — она чудом спаслась, спрятавшись под диваном. Стены и потолок выгорели полностью 📱 Мы в мессенджере МАКС
❤1
Posted without readable text
Мощная магнитная буря ожидается на Земле через два дня Специалисты прогнозируют усиление геомагнитной активности, вызванное солнечной вспышкой. Метеозависимые люди могут столкнуться с ухудшением самочувствия, включая головные боли и общую слабость. 📱 Мы в мессенджере МАКС
Posted without readable text
Москву начали украшать к Новому году. До праздника ещё 74 дня 📱 Мы в мессенджере МАКС
В Оренбургской области пьяный отец нанёс ребёнку 30 ударов и утопил его в ванне. 22-летний житель Бузулука избил малыша и утопил в воде, после чего попытался выдать расправу за несчастный случай. Выяснилось, что мужик издевался над ребёнком регулярно: бросал об батарею, запрещал кормить, а в холод оставлял на веранде в одном подгузнике. На ублюдка уже завели уголовку. 📱 Мы в мессенджере МАКС
Здравствуйте. Стремянка есть у вас? Парашютист приземлился на крышу дома под Астраханью Мужчина смотрел телевизор, когда на крыше что-то загремело. На улице он увидел необычную картину: весь дом был опутан стропами, а на крыше сидел парашютист — тот очень извинялся и просил лестницу. Хозяин не стал ругаться — вызвал МЧС, и парашютиста сняли. 📱 Мы в мессенджере МАКС
Posted without readable text
Netflix зарегистрировал товарный знак в России до 2036 года Под ним приостановившая работу в России компания сможет предоставлять телепрограммы через сервисы «видео по запросу», а также продавать одежду, обувь, сумки, игрушки и канцелярию. 📱 Мы в мессенджере МАКС
🫨 Один из протестующих во Франции попытался разнести витрину марсельского магазина Lacoste, чтобы его ограбить, но что-то пошло не так, и витрина разнесла самого грабителя 📱 Мы в мессенджере МАКС
Showing the 12 most recent of 772 posts we hold for @derzkiy_kvadrat. 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.
Posts edited after publishing
@derzkiy_kvadrat edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 1 September 2026
- Most recent edit
- 1 September 2026
Forward network
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“ДЕРЗКИЙ КВАДРАТ 18+” (@derzkiy_kvadrat), 27,746 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/derzkiy_kvadrat.
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.