Telegram RegisterThe public register of Telegram

Channel

CUMыш

@CUMyshhh

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

709subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002038327826
TypeChannel
Username@CUMyshhh
DescriptionФурри художник/графический дизайнер — МЕНЮ С ИНФОЙ В ЗАКРЕПЕ [ЗАКРЫТЫ] Заказы в лс телеграм канала🧊 Pricelist & links: RU/EN - https://kamyshhh.tilda.ws/ru/price-list http://t.me/anonaskbot?start=9mxc9ynibg800o7 To do: https://trello.com/b/017cBHWb
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/CUMyshhh

Growth

7099 Aug 2026, 12:17 — 709 subscribers9 Aug 2026, 12:30 — 709 subscribers9 Aug 2026, 12:179 Aug 2026, 12:30
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 708–710 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 12:30709no change
9 Aug 2026, 12:17709first reading

Engagement

14 posts held, back to 25 May 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
47.5%
avg views ÷ 709 subscribers
Avg views / post
337
1 post measured
Reaction rate
4.75%
reactions ÷ views · ER floor
Posts in window
1
of 14 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 23 July 2026
Posts held14 (25 May 202623 July 2026)
Views total337
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 12:30 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
268
Videos
3
Links
48

Lifetime counters from Telegram’s own channel header, read 9 August 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.

Reaction mix

538 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 48.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 531659498755773269826248.7%
custom 533228065050437701014226.4%
custom 57852906810774686569918.4%
custom 5958602717529117064305.58%
🍓50.929%

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

Measured over the 14 most recent posts we hold, published 25 May 2026 to 23 July 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

23 Jul 2026, 15:56 UTC337 views16 reactionsread 9 August 2026
Forwarded from @Kamyshhh_shitpostPhoto

Я развеялся по ветру в связи с тем, что занимаюсь выполнением сложной задачи с коротким дедлайном аха ПОЭТОМУ, я до 5 августа точно не алё. Как же тяжело ебашить верстку журнала в такие сжатые сроки эххххх бляяяятьь🙆‍♂️ Те, кто нарисовал мне атаку на АФ, не переживайте, я отвечу вам даже после окончания ивента 🙏 Не теряйте, я обязательно вернусь и буду и дальше показывать вам красоту 🥰

custom 53165949875577326989custom 53322806505043770106custom 57852906810774686561

11 Jul 2026, 11:16 UTC603 views56 reactionsread 9 August 2026
Photo

🩸 👁‍🗨👁‍🗨 🩸 🍊Облизываю TIZZFLO👽 🌧️🌧️🌧️🌧️🌧️🌧️🌧️ Поздравляю с созданием фурсоны 👋 Ками она очень понравилась и ему показалось отличной идеей выразить это вот так 😳 [Мой AF профиль] #ArtFight #Mystery

custom 531659498755773269834custom 578529068107746865612custom 533228065050437701010

8 Jul 2026, 08:47 UTC593 views60 reactionsread 9 August 2026
Photo

🩸 👁‍🗨👁‍🗨 🩸 Я снова нападаю, ГАВ ГАВ ГАВ 🌧️🌧️🌧️🌧️🌧️🌧️🌧️ В этот раз на voltRA 😋 [Мой AF профиль] #ArtFight #Mystery

custom 578529068107746865638custom 531659498755773269813custom 53322806505043770108🍓1

2 Jul 2026, 15:23 UTC646 views36 reactionsread 9 August 2026
Photo

🩸 👁‍🗨👁‍🗨 🩸 🖱 И мой первый удар приходится по @Afftii 🖥 🌧️🌧️🌧️🌧️🌧️🌧️ Ой, чего-то у меня техника барахлит...... Аффти?.... [Мой AF профиль] #ArtFight #Mystery

custom 531659498755773269827custom 53322806505043770105custom 59586027175291170644

1 Jul 2026, 18:53 UTC621 views11 reactionsread 9 August 2026

Напоминаю про возможность прислать свой профиль с карточкой 🕺 Всем приятного времяпровождения в артфайте!

custom 533228065050437701011

22 Jun 2026, 11:38 UTC750 views61 reactionsread 9 August 2026
Photo

🌟 Вафельное 🌟 🌧️🌧️🌧️🌧️🌧️🌧️🌧️ Кусочек арта, который закинул в щитпост несколько дней назад. Скорее всего когда-нибудь сделаю из этого свопку! ➡️[щитпост] #Kamy #sfw

custom 531659498755773269839custom 595860271752911706411custom 533228065050437701010custom 57852906810774686561

22 Jun 2026, 07:01 UTC649 views27 reactionsread 9 August 2026

Это просто песня ✋ 🔞 🤚 Мой сладенький малышок

custom 531659498755773269821custom 53322806505043770103custom 57852906810774686563

22 Jun 2026, 06:59 UTC650 views42 reactionsread 9 August 2026
Photo

💫🌨️🌨️📌 👤📌🌨️🌨️✨ трейд с Камышом было больно, тяжко с этим артом. в какой-то момент я почти дропнула работу, хотела перерисовать все (оставалась светотень). а спустя время решила сделать шейд через чб, и результат мне зашел очень даже. похоже только через чб и буду дальше рисовать. заодно поигралась с картой градиента, веселая штука 🌨️🌨️🖤🌨️🌨️

custom 531659498755773269831custom 57852906810774686568custom 53322806505043770103

16 Jun 2026, 07:33 UTC739 views33 reactionsread 9 August 2026
Forwarded from @Kamyshhh_shitpostPhoto

Импульсивно решил принять участие в артфайте❗️ [профиль] Дай бог мне сил и времени рисовать многа картинок, аминь Кто участвует, кидайте оформленные шаблоны со ссылками! Любопытно поглядеть 🗣 #ArtFight #Mystery

custom 533228065050437701020custom 53165949875577326989🍓4

15 Jun 2026, 11:46 UTC679 views40 reactionsread 9 August 2026
Photo

— Хмм... Почему бы нам не пойти куда-нибудь где потише? @Kamyshhh_shitpost 😄 🌧️🌧️🌧️🌧️🌧️ Йоу, я решил все таки создать щитпост! Буду публиковать там процессы работ, рассказывать как у меня дела и показывать, чем я занимаюсь когда не рисую! Уже выкатил там пару постов! Мне будет приятно, если вы хотите узнать меня получше, мяу 🎧 Не планирую туда плакаться, писать о каждом переживании или что-то вроде, чисто френдли хих

custom 578529068107746865621custom 53165949875577326989custom 53322806505043770109custom 59586027175291170641

7 Jun 2026, 14:19 UTC992 views42 reactionsread 9 August 2026
Photo

🥞 Темно-грушевый и насыщенно-византийский ❤️‍🔥 🌧️🌧️🌧️🌧️🌧️🌧️🌧️ Сочнейший трейд с @nemphelis #sfw #trade Eng.ver 🥞 Dark Pear and Rich Byzantine ❤️‍🔥 🌧️🌧️🌧️🌧️🌧️🌧️🌧️ An absolutely juicy art trade with @nemphelis

custom 533228065050437701025custom 57852906810774686569custom 53165949875577326988

2 Jun 2026, 10:02 UTC834 views24 reactionsread 9 August 2026
Photo

Мои три свопочки для @tastyswop 🌧️🌧️🌧️🌧️🌧️🌧️🌧️🌧️ 🔴Коробок спичек «White Ash» с Лаймой «White Ash» («Белый Пепел») - именно так называется команда наёмников Лаймы в AU-вселенной, по которой была создана сайд-стори «The Last Client». Поэтому мне захотелось оформить её карточку в виде коробка спичек - важной искры, с которой всё началось.🌟 🟣Набор зажигалок «Last Spark» с Ками Мне показалось интересным провести связь м

custom 531659498755773269818custom 53322806505043770103custom 59586027175291170643

Showing the 12 most recent of 14 posts we hold for @CUMyshhh. 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 — 982,751 of 1,340,412entries 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

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 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.

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

“CUMыш” (@CUMyshhh), 709 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/CUMyshhh.

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.