Telegram RegisterThe public register of Telegram

Channel

ㅤ@. 霧雨 s͟͟͟͟h͟͟͟͟e͟͟͟͟𝗇𝗄𝖾–

@shenkecos

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

157subscribers

-2 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-1003955014094
TypeChannel
Username@shenkecos
CreatedBetween 1 April 2026 and 6 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/shenkecos

Growth

1571591589 Aug 2026, 18:17 — 159 subscribers9 Aug 2026, 18:30 — 159 subscribers10 Aug 2026, 17:28 — 157 subscribers9 Aug 2026, 18:1710 Aug 2026, 17:28
3 measurements taken within a single day, net -2. 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 157–159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:28157-2
9 Aug 2026, 18:30159no change
9 Aug 2026, 18:17159first reading

Engagement

15 posts held, back to 6 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
77.9%
avg views ÷ 157 subscribers
Avg views / post
122
7 posts measured
Reaction rate
30.7%
reactions ÷ views · ER floor
Posts in window
7
of 15 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 2 August 2026
Posts held15 (6 July 20262 August 2026)
Views total856
Reactions total263
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 18: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

Video runtime
7s
Average length
4s

Measured directly from 2 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

575 reactions across 15 posts, in 16 distinct kinds. The most used accounts for 15.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54608123786753658199115.8%
custom 51953490744039565538013.9%
custom 5461084791271081938529.04%
custom 5296597439438943846508.70%
custom 5193152589474075153457.83%
custom 5260438839918369839396.78%
custom 5348449570286238634386.61%
custom 5330188335711293106366.26%
custom 5276057535734910749295.04%
custom 5258238283359493091254.35%
custom 5461022295201956875223.83%
custom 5350521496869561548172.96%
custom 5350692616956570074172.96%
custom 5438386945673691091152.61%
custom 5377656971396678459101.74%
custom 529634404925337959091.57%

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

Measured over the 15 most recent posts we hold, published 6 July 2026 to 2 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

2 Aug 2026, 11:43 UTC57 views44 reactionsread 9 August 2026
Photo

прошло 84 дня. мне аж самой не верится, что настолько мой скилл вырос, по сравнению в 10 мая, когда я была на тогучи🤍 это все без учета того, что у меня сейчас парику очень плохо))

custom 525823828335949309116custom 527605753573491074915custom 526043883991836983913

2 Aug 2026, 11:20 UTC60 views29 reactionsread 9 August 2026
Photo

мое желание сделать зарянку, это просто... но, когда я смотрю на ее пучок сзади, вспоминая свои умения в париках, я ее все время откладываю😭

custom 526043883991836983911custom 51953490744039565539custom 52582382833594930919

1 Aug 2026, 18:52 UTC234 views49 reactionsread 9 August 2026

Posted without readable text

custom 535052149686956154817custom 535069261695657007417custom 543838694567369109115

1 Aug 2026, 18:36 UTC188 views43 reactionsread 9 August 2026

Posted without readable text

custom 526043883991836983915custom 519534907440395655314custom 527605753573491074914

23 Jul 2026, 17:43 UTC95 views38 reactionsread 9 August 2026
Photo

чуть чуть реал лайфа, я постаралась сейчас поактивить у мьюшек, инет плохо работает, и второй акк ваще не грузит😭  я во всю уже думаю о новых коспланах, думаю о будущем контенте и что планирую снять когда приеду, а будет много всего, уже через неделю я буду дома, в городе.🤩

custom 519534907440395655315custom 519315258947407515313custom 546108479127108193810

22 Jul 2026, 16:42 UTC96 views22 reactionsread 9 August 2026

я тут отдыхаю на море, инета почти нет, так что ребят, извиняюмь шо не активлю. думаю по типу таких постиков сделать с кабукимоно и скарой для полного счастья🩶 через неделю буду, ребятуш🤩

custom 51931525894740751539custom 53301883357112931067custom 51953490744039565536

16 Jul 2026, 20:10 UTC126 views38 reactionsread 9 August 2026

добрый вечер, малыши. скоро я уеду на 10 дней и контента будет немаа, НО! ждите анонсов, сигны, косплей скарамуччи, фотосет в ганьюй и шэньхе(??)  а также после моего приезда ждите новое оформление, новые реакции

custom 519534907440395655314custom 519315258947407515312custom 546081237867536581912

12 Jul 2026, 20:43 UTC163 views42 reactionsread 9 August 2026
Photo

о господи, наконец пост о кошачьем фесте. на самом деле я была очень сильно разочарована в нем. помимо того, что я потеряла ушки, которые купила почти за 2к, также сама организация феста не оказалось лучше. 1600₽, за билет неоправданны. гримерки(для гостей) не было, площадь феста очень маленькая, буквально 1/20 крыши. я была в шоке конечно. но зато с подружаней время провела. сам косплей, который вышел в итоге, мне в

custom 546108479127108193816custom 546081237867536581915custom 529659743943894384611

9 Jul 2026, 18:29 UTC132 views30 reactionsread 9 August 2026
Photo

вот такое чудо у меня вышло с аэрографией и сияшками, прядки еще подравнивать буду, но в основном это конечный результат.  а также мой косплей скарамуччи приедет ≈ 1 августа с доки✨

custom 533018833571129310614custom 54608123786753658199custom 51953490744039565537

8 Jul 2026, 22:18 UTC130 views50 reactionsread 9 August 2026
Photo

➿🎁🌟НОНС. . .➿➿    еду на кошачий фест уже в это воскресенье 🎁 буду ждать всех, фотки, влог, все будет, все ждите, будет много контента, еду в амане мисе, не теряйте!🎁       🥹🥹tags – #анонс

custom 529659743943894384617custom 534844957028623863417custom 546081237867536581916

8 Jul 2026, 19:29 UTC118 views60 reactionsread 9 August 2026
Photo

➿🎁🌟МА́НЕ МИСА–. . . ㅤ@. 霧雨 s͟͟͟͟h͟͟͟͟e͟͟͟͟𝗇𝗄𝖾– ➿  🥹рэм, расскажи, как можно убить бога смерти?🥹       🥹🥹 tags:: #косплей  🥹рт, мью, вп ??

custom 529659743943894384622custom 534844957028623863421custom 546081237867536581917

8 Jul 2026, 18:27 UTC94 views33 reactionsread 9 August 2026
Photo

в этот день не спала вся россия. что это за парик и где люмин сейчас расскажу. . .  мне приехала хорошая база и она была настолько густой, длинной, что мне очень стало жалко резать ее под люмин. представлю вам укладку на амане мису с вклеенными хвостиками. самое спонтанное решение🎁

custom 546102229520195687512custom 519315258947407515311custom 537765697139667845910

Showing the 12 most recent of 15 posts we hold for @shenkecos. 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 — 471,611 of 1,478,351entries 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

Named by 1 registered channel — 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.

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

“ㅤ@. 霧雨 s͟͟͟͟h͟͟͟͟e͟͟͟͟𝗇𝗄𝖾–” (@shenkecos), 157 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/shenkecos.

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.