Telegram RegisterThe public register of Telegram
Telegram profile photo for вонючее сообщество

Channel

вонючее сообщество

@shanlesshugger

2 usernames

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

28subscribers

+9 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003950221015
TypeChannel
Usernames@co9lover @shanlesshugger
CreatedBetween 1 April 2026 and 12 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live4 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/shanlesshugger

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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 the other topics.

Growth

19370194.514 August 2026 — 19 subscribers14 August 2026 — 19 subscribers21 August 2026 — 20 subscribers28 August 2026 — 30 subscribers5 September 2026 — 31 subscribers13 September 2026 — 28 subscribers26 September 2026 — 203 subscribers26 September 2026 — 203 subscribers8 October 2026 — 27 subscribers14 October 2026 — 240 subscribers20 October 2026 — 234 subscribers28 October 2026 — 329 subscribers3 November 2026 — 370 subscribers4 November 2026 — 28 subscribers2814 August 20264 November 2026
14 measurements spanning 83 days, net +9. 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
Measured (UTC)SubscribersChange
4 Nov 2026, 20:2028-342
3 Nov 2026, 07:18370+41
28 Oct 2026, 00:39329+95
20 Oct 2026, 02:31234-6
14 Oct 2026, 00:05240+213
8 Oct 2026, 13:0127-176
26 Sept 2026, 01:22203no change
26 Sept 2026, 00:47203+175
13 Sept 2026, 09:1728-3
5 Sept 2026, 04:3731+1
28 Aug 2026, 09:4430+10
21 Aug 2026, 04:5520+1
14 Aug 2026, 06:0119no change
14 Aug 2026, 05:4819first reading

Engagement

40 posts held, back to 12 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 2 pages 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 40 posts for this entry, the most recent from 25 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

704 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 16.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 541596969028974736911616.5%
custom 541590400305991898111516.3%
custom 541594646740157094611416.2%
custom 541606220818026533011416.2%
custom 5827904805422504933425.97%
custom 5830355681265327096354.97%
custom 5827789013104205442334.69%
custom 5827777468232113980314.40%
custom 5827751131492654847273.84%
custom 5827966322239086572263.69%
custom 5828036690983263688263.69%
custom 5827830309214755939253.55%

Custom emoji. Every 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 counts beside them are Telegram’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 11 of the 40 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 704 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 12 August 2026 to 25 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
2
across the posts below
Posts paid on
1
of 40 we hold a reading for · 3%
Most on one post
2
single highest reading

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

Recent posts

23 Sept 2026, 16:19 UTC115 viewsread 26 September 2026
Photo

💌🤩 этого dня ( 𝟤𝟥.О𝟗.𝟤𝟨 ) 💙 🎀 🤩🎀🎀🖤 🤩 🤩🤩 ⭐️ @shanlesshugger и @satiraskisser ⭐️ 🤩 заключают (платоник) брак!! 🎁

23 Sept 2026, 14:36 UTC43 viewsread 26 September 2026
Forwarded from @cheriescoquettePhoto

😀🌟🌟😀😀😀😀😀😀😀😀 🎀🤩озыгрыш с призовым 🥹🥹 🥹🥹фондом 7000 зв ! 🥹 by : @cheriescoquette & @tek3ra 💕ризовые места :: 😀😀😀😀 𝟣-𝟦 место – нфт до 𝟩𝟢𝟢 💜 𝟧 место – нфт 🤍 𝟨-𝟪 место – 𝟧𝟢𝟢 💜 𝟫-𝟣𝟢 – 𝟤𝟢𝟢 зв 💜 💕словия розыгрыша :: 🤍🤍🤍 𝟢𝟣. подписка на @cheriescoquette & @tek3ra без дальнейшей отписки ! 🤍 𝟢𝟤. рт в своё инфо/тгк от 𝟥𝟢+ пдп не стикером ! 🤍 𝟢𝟥. скинуть в комы ссылку на рт, свой юз моно и свой порядковый номер, прошу не путат…

22 Sept 2026, 18:37 UTC129 viewsread 26 September 2026

https://t.me/shanlesskisser резы все идут по порядку

14 Sept 2026, 15:04 UTC281 views110 reactionsread 26 September 2026

🤩🤩 ო⃪𝆋‌ꫀ‌‌⃪ᷓۢࠖ‌‌ᤐֹ‌𝆋𐇽ܵۜ/ᥙ𝐧⃪ֵֶׂۭ֘֯ۚო⃪𝆋‌ꫀ‌‌⃪ᷓۢࠖ‌‌ᤐֹ‌𝆋𐇽ܵۜ թ⃪‌ܵۜ𖹭⃪ְۣׅؔ᤺ᝳડָׅ֗ꪳۢࠖ𝐭᪰‌⃔‌ܵۜ‌︪‌‌..🪐 3️⃣десь можно стать моим мью либо же наоборот сделать анмью! 🙂🙂🙂 — Я буду тапать вам рк на посты, активничать в яикто/интерактивах/анонтаймах и всякой такой белеберде в вашем инфо! 🌟🌟 — Жду от вас тоже актив, хоть интерактивов я почти не делаю, но всё же..🌟 акт писать в @rannanonimbot

custom 541590400305991898128custom 541594646740157094628custom 541596969028974736928custom 541606220818026533026

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

12 Aug 2026, 17:54 UTCAnonymous Poll19 voters

Am I ??

  1. ɢυɪʟ੮ⲩ ,, 🎁53%
  2. ⅈɳɳσ ,, 👁47%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 40 most recent posts we hold, published 12 August 2026 to 25 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

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

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.

Mentions

Named by 2 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.

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

“вонючее сообщество” (@shanlesshugger), 28 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/shanlesshugger.

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.