Telegram RegisterThe public register of Telegram

Channel

ДенжерЛьоха 🐷

@dangerlyoha

Verified by Telegram

On this record: Topic · Observations · Growth · Engagement · Reactions · Stars · Posts · Citations · Domains linked from posts · Cite this entry

327,738subscribers

+1,602 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001584210088
TypeChannel
Username@dangerlyoha
Created16 July 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/dangerlyoha

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

335,000 average views per post against 327,738 subscribers — an engagement rate of 102.2%. Across the 475 registered channels in the same cohort — 316,877–999,955 subscribers, posting mainly in Russian — the middle half sit between 2.76% and 19.0%, with a median of 7.36%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured14 of 14 published in the window (0 exact, 14 rounded by Telegram)
Views totalled4,689,600
Mature posts only116.6% over 12 posts read at least 24h after publication
Subscribers327,738 measured 12 August 2026
Cohortb316228:rus · 475 channels · p10 1.31% · p25 2.76% · p50 7.36% · p75 19.0% · p90 37.7%
Position in cohort100.000th percentile · 13.9× the cohort median
Uncertainty±0.091% of the figure, from Telegram’s rounding
Post languageRussian · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

326,136327,738326,9377 August 2026 — 326,136 subscribers7 August 2026 — 326,136 subscribers7 August 2026 — 326,164 subscribers8 August 2026 — 326,549 subscribers9 August 2026 — 326,760 subscribers10 August 2026 — 327,333 subscribers11 August 2026 — 327,530 subscribers11 August 2026 — 327,663 subscribers12 August 2026 — 327,738 subscribers7 August 202612 August 2026
9 measurements spanning 6 days, net +1,602. 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”. The vertical axis spans 325,896–327,978 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:57327,738+75
11 Aug 2026, 23:13327,663+133
11 Aug 2026, 02:12327,530+197
10 Aug 2026, 05:10327,333+573
9 Aug 2026, 05:51326,760+211
8 Aug 2026, 07:06326,549+385
7 Aug 2026, 07:16326,164+28
7 Aug 2026, 06:00326,136no change
7 Aug 2026, 05:51326,136first reading

Engagement

20 posts held, back to 3 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
102.2%
avg views ÷ 327,738 subscribers
Avg views / post
335,000
14 posts measured
Reaction rate
4.66%
reactions ÷ views · ER floor
Posts in window
14
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held20 (3 July 202611 August 2026)
Views total4,689,600
Reactions total218,680
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:49 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.

Reaction mix

322,980 reactions across 20 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5400030430999093702322,980100.0%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 20 of the 20 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 322,980reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 3 July 2026 to 11 August 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
2,693
across the posts below
Posts paid on
20
of 20 we hold a reading for · 100%
Most on one post
364
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dangerlyoha. 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 20 most recent posts we hold for this entry, published 3 July 2026 to 11 August 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.

Recent posts

11 Aug 2026, 17:12 UTC≈25,500 views1,280 reactions2 Starsread 11 August 2026

А ДЕЛО ТО ПАШЛО https://www.twitch.tv/dangerlyoha

custom 54000304309990937021,280

11 Aug 2026, 14:02 UTC≈77,100 views7,760 reactions20 Starsread 11 August 2026

здарова, чудищя! третий день подряд плотнейший влет врубахтунг через 3 чяса 😎🤙🏿 оформляем конкретний шпил

custom 54000304309990937027,760

9 Aug 2026, 17:13 UTC≈170,000 views21,000 reactions288 Starsread 12 August 2026
Photo

Photo, posted without a caption

custom 540003043099909370221,000

8 Aug 2026, 08:05 UTC≈212,000 views17,600 reactions55 Starsread 12 August 2026
Photo

польша негативно влияет посмотрел марвел спудик... бесплатно...

custom 540003043099909370217,600

6 Aug 2026, 13:01 UTC≈242,000 views21,000 reactions152 Starsread 12 August 2026
Photo

доебли! еду на пострижку запомните меня лохматим

custom 540003043099909370221,000

5 Aug 2026, 11:29 UTC≈246,000 views19,000 reactions364 Starsread 12 August 2026
Photo

уебываю в варшаву с разведкой на пару дней сильно не скучяйте, вернусь постримлю еще ок?

custom 540003043099909370219,000

31 Jul 2026, 12:46 UTC≈360,000 views14,000 reactions95 Starsread 12 August 2026

связь чудищя, шо ви) как ви) кооп с братвой переносится на завтра, седня можете отдихать 😎 обнял!)

custom 540003043099909370214,000

23 Jul 2026, 21:45 UTC≈593,000 views17,800 reactions99 Starsread 12 August 2026
Photo

ну и шо за хуйня

custom 540003043099909370217,800

20 Jul 2026, 17:35 UTC≈638,000 views21,900 reactions287 Starsread 12 August 2026
Photo

це пизда даже не ампутируешь

custom 540003043099909370221,900

19 Jul 2026, 22:08 UTC≈505,000 views23,400 reactions141 Starsread 12 August 2026
Photo

нт старый матч дерьмище

custom 540003043099909370223,400

18 Jul 2026, 22:11 UTC≈434,000 views17,400 reactions80 Starsread 12 August 2026
Photo

секса не било.

custom 540003043099909370217,400

17 Jul 2026, 16:50 UTC≈387,000 views12,100 reactions36 Starsread 12 August 2026

12 место отдельное поздравление тебе родной, обращяйтесь 💪🏿

custom 540003043099909370212,100

Showing the 12 most recent of 20 posts we hold for @dangerlyoha. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 98,699 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

Domains linked from posts

One domainthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

upg.gg1 post · 10 July 2026 – 10 July 2026 · example post

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“ДенжерЛьоха 🐷” (@dangerlyoha), 327,738 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dangerlyoha.

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.