Telegram RegisterThe public register of Telegram

Channel

Хаб-локация 🔞

@dewulfwithdick

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

352subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001751779470
TypeChannel
Username@dewulfwithdick
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/dewulfwithdick

Growth

35211 Aug 2026, 06:47 — 352 subscribers11 Aug 2026, 15:22 — 352 subscribers11 Aug 2026, 06:4711 Aug 2026, 15:22
2 measurements taken within a single day. 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 351–353 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:22352no change
11 Aug 2026, 06:47352first reading

Engagement

13 posts held, back to 12 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
33.0%
avg views ÷ 352 subscribers
Avg views / post
116
9 posts measured
Reaction rate
12.3%
reactions ÷ views · ER floor
Posts in window
9
of 13 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 9 August 2026
Posts held13 (12 July 20269 August 2026)
Views total1,046
Reactions total129
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 06:47 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

157 reactions across 13 posts, in 16 distinct kinds. The most used accounts for 28.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4528.7%
💔3321.0%
custom 53192648809628530592214.0%
😢106.37%
😭106.37%
🥰85.10%
custom 525135041853706347553.18%
custom 525175249619544663253.18%
🤝53.18%
🫡53.18%
❤‍🔥31.91%
😱21.27%
custom 525143323839143359810.637%
🍌10.637%
🙏10.637%
🤬10.637%

Custom emoji. 4 of the rows above are 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 counts beside them areTelegram’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 13 of the 13 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 157reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 12 July 2026 to 9 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.

Recent posts

9 Aug 2026, 12:45 UTC63 views21 reactionsread 11 August 2026
Forwarded from @velcum67Photo

@chepupokchech нарисовал мне перед отъездом 🤩 Вэл тут занимаеца хорни гимнастикой 🤪

14custom 52517524961954466325custom 53192648809628530592

9 Aug 2026, 12:43 UTC94 views19 reactionsread 11 August 2026
Photo

Афигеть спасибо @velcum67 за этот лайнарт в моём скетчбуке Вышло абсолютно жёстко 😯😯😯😯

13custom 52513504185370634753custom 53192648809628530593

6 Aug 2026, 15:33 UTC122 views22 reactionsread 11 August 2026
Photo

Скетчили с Вэл у меня дома😯😯 Нацарапал небольшую довольную письку за минут 20😇😇😇😇

16custom 53192648809628530593custom 52513504185370634752custom 52514332383914335981

2 Aug 2026, 14:04 UTC101 views8 reactionsread 11 August 2026
Forwarded from @chrystal_2288Photo

3 дня 35 персонажей У всех свои характеры, свои истории и фишки. Я постаралась учесть пожелания каждого и надеюсь, что все остались довольны. Файл работы будет в комментариях к посту.

🥰8

27 Jul 2026, 15:18 UTC93 views7 reactionsread 11 August 2026
Forwarded from @varvarlyanaPhoto

ОТКРЫТ СБОР СРЕДСТВ НА СОЗДАНИЕ ВЫСТАВОЧНОГО ЗАЛА С РАБОТАМИ ОЛЕСИ (ссылка на сообщение матери) ПРОШУ РЕПОСТНУТЬ КУДА УГОДНО! АРТ / ЛИЧНЫЕ ТГК, ДРУЗЬЯМ, В НОВОСТНЫЕ ПАБЛИКИ 🌄🌄🌄🌄🌄 - недавно этот мир покинула прекрасная художница Олеся Косарева. Она погибла в результате наводнения. В знак памяти о ней и её творчестве, её мать открывает сбор средств на выставочный зал с работами девушки. 🌄🌄🌄🌄🌄 Переводы принимаются на но

🫡5😭1🙏1

27 Jul 2026, 08:48 UTC113 views11 reactionsread 11 August 2026

Спасибо всем за соболезнования, за ваши добрые слова. Сегодня я была на опознании. Тело сильно пострадало, опознать по нему невозможно, я узнала Олесю по одежде. Её тело прошло страшный путь: 40 километров в потоке, пока не застряло в завале из мусора и деревьев. Мы будем кремировать Олесю. Денег на это хватит из собранных средств. Я не хочу, чтобы жизнь Олеси закончилась так нелепо и бессмысленно. Не хочу, чтобы е

💔11

26 Jul 2026, 15:46 UTC81 views17 reactionsread 11 August 2026
Forwarded from @julie_talk

нашлась. она не выжила

😢10💔2😭2😱2🤬1

23 Jul 2026, 11:34 UTC211 views21 reactionsread 11 August 2026
Photo

Хороших новостей по ситуации с Олесей всё нет и нет Пытаюсь как-то скетчить перед тем как снова уйти в творческий отпуск на 2 недели

custom 531926488096285305914😭5💔2

15 Jul 2026, 14:54 UTC168 views3 reactionsread 11 August 2026
Forwarded from @buvanybu

Сборы закрыты! Родственник Олеси сообщил, что вы отправили более чем достаточно, он очень тронут что столько людей со всего мира заинтересованы в помощи, большое всем спасибо!

❤‍🔥3

14 Jul 2026, 20:38 UTC308 views23 reactionsread 11 August 2026

Постов не будет какое-то время, пока об Олесе не станет что-то известно Из-за всех этих новостей рисовать совсем нет настроения

💔17🤝5🍌1

12 Jul 2026, 20:11 UTC150 views1 reactionsread 11 August 2026
Forwarded from @krista_21_artsPhoto

🤩 Фото для поиска 🤩 И ну, наверное работы для понимания кто это Всё ещё надеюсь, что обойдётся всё😭 Если кто-то в Перми или около села Кын или их рек, прошу помочь распространить или поделиться хоть какой-то информацией по поводу ситуации, сама я тоже попытаюсь держать в курсе. Не знаю что говорить особо, ничего в голову не идет, очень переживаю за тебя, Олесь, найдись живой🙏

😭1

12 Jul 2026, 17:26 UTC99 views2 reactionsread 11 August 2026
Forwarded from @buvanybuPhoto

https://vk.com/wall-225524663_5515

1😭1

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

Citation-graph rank

Citation-graph rank — 1,092,485 of 1,189,255entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“Хаб-локация 🔞” (@dewulfwithdick), 352 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/dewulfwithdick.

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.