Telegram RegisterThe public register of Telegram
Telegram profile photo for 𐔌 𐅁𝐍𝖎𝖌𝖍𝖙𝖒𝖆𝖗𝖊 )᷼ ⠷ ꒱

Channel

𐔌 𐅁𝐍𝖎𝖌𝖍𝖙𝖒𝖆𝖗𝖊 )᷼ ⠷ ꒱

@Kemushi_RS

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

43subscribers

+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-1003447210452
TypeChannel
Username@Kemushi_RS
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/Kemushi_RS

Growth

4311 Aug 2026, 05:02 — 43 subscribers11 Aug 2026, 05:15 — 43 subscribers11 Aug 2026, 05:0211 Aug 2026, 05:15
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 42–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:1543no change
11 Aug 2026, 05:0243first 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
56.3%
avg views ÷ 43 subscribers
Avg views / post
24.2
10 posts measured
Reaction rate
20.4%
reactions ÷ views · ER floor
Posts in window
13
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. It is computed over the 5 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (3 July 20266 August 2026)
Views total242
Reactions total28
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 05:15 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
1
Links
3

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

110 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 23.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54272723348158267012623.6%
custom 54476144810456842532421.8%
custom 53821797222832306192220.0%
custom 54406940818460139892018.2%
custom 54494228297810253661816.4%

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 12 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 110reactions 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 6 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

6 Aug 2026, 23:40 UTC12 views3 reactionsread 11 August 2026

— 🔡онечно, я ничего не понял... но твой рассказ очень интересный, хотя, припоминаю, один юнец как-то рассказывал мне про ленты... 🔡огда я, наверное, пойду, раз у тебя всё хорошо, или всё-таки что-то тревожит, и ты хочешь об этом высказаться кому-то? Я могу стать твоим слушателем, пока ты спишь. Кто знает, может, как проснёшься, тебе легче на душе станет.

custom 53821797222832306193

5 Aug 2026, 00:11 UTC14 viewsread 11 August 2026

🔤а, наверное, я ошибся... Он меня не знает, а я его. В принципе, зачем я пытался разглядеть и узнать его? Все существа, а особенно люди, и так уже на одно лицо для меня. — 🔡ороший вопрос... Я — Путешественник во снах. Ну и, исходя из прозвища, я посещаю различные сны, и в этот раз я решил посетить твой, особенно видя, что у тебя были явные проблемы. Ты знаешь, что могло спровоцировать подобного рода сон?

4 Aug 2026, 18:25 UTC17 viewsread 11 August 2026

— 🔡у ты чего заплакал? Всё же ведь закончилось, и всё хорошо, или тебя что-то ещё беспокоит? Неважно... ты главное сейчас ни о чём не переживай, ведь это всё — сон. Сейчас ты волен делать в нём всё, что захочешь... 🔡 теперь вытирай слёзы и приходи в себя.

3 Aug 2026, 23:36 UTC19 viewsread 11 August 2026

🔤 очередной раз осматривая различные сны, я наткнулся на пузырь, вокруг которого царила устрашающая атмосфера. Такое я встречал лишь единожды: тогда тело души умерло, и она застряла во сне, став новым путешественником. 🔤 даже не разглядел нормально, что происходило в том сне, сразу же ринулся в него, надеясь успеть спасти несчастную душу. К счастью, я смог явиться почти что вовремя. Это был уже знакомый мне юноша,

28 Jul 2026, 23:22 UTCviews —

Channel name was changed to «𐔌 𐅁𝐍𝖎𝖌𝖍𝖙𝖒𝖆𝖗𝖊 )᷼ ⠷ ꒱»

28 Jul 2026, 23:20 UTC16 viewsread 11 August 2026
Forwarded from @ReverseSide_net

#𝐔𝗇𝗋𝖾𝗌𝗍 🤩 𝗿𝗲𝘃𝑒𝗿𝘀𝗲 𝑠𝗶𝗱𝗲 🔤 𝒄𝒂𝒏 𝓼𝒆𝒆 𝐲𝐨𝐮 𝒂𝒈𝓪𝒊𝒏🔤 ׄ‌ ︶ㅤࣦ ‎⃟🤩 Д𝐲ш𝐚 вд𝐨в𝐨ль 𝐨тд𝐨𝐱н𝐲л𝐚 и в𝐨𝐜𝐜т𝐚н𝐨вил𝐚 𝐜в𝐨и 𝐜илы и г𝐨т𝐨ва п𝐩𝐨д𝐨лжить в𝐞𝐜ти 𝐤𝐚н𝐚л! ㅤׄ ⃨⏜᷼💙 💙 💙 𝓽 . 𝗆𝖾 ⋮ Кэмуси , Аига , Шион ⌢ Не пропустите самые свежие новости от данных саппортов ‼️

19 Jul 2026, 20:12 UTCviews —

Channel name was changed to «застрял в кошмаре 𐔌 𐅁𝐍𝖎𝖌𝖍𝖙𝖒𝖆𝖗𝖊 )᷼ ⠷ ꒱»

19 Jul 2026, 20:11 UTC39 viewsread 11 August 2026
Forwarded from @ReverseSide_net

ᅠᅠREVERSE SIDE : #𝐑est 💤 ᅠ⌢ Кэмуси Кайто уходит в рест до 28.07 ᅠПросьба не тревожить и не отписываться от саппорта. ‼️ ᅠᅠ٬٬ִ @Kemushi_RS ❓

18 Jul 2026, 00:34 UTC48 views6 reactionsread 11 August 2026

— 🔡печален?.. А, это... Я всегда так выгляжу, просто не привык показывать эмоции, да и сейчас это не имеет смысла, наверное, поэтому выгляжу слегка грустным. 🔡 межсонном пространстве, да и во снах, любой вкус отсутствует, тем не менее твой подарок я приму, спасибо, если не вкус, то текстуру шоколада я буду рад вспомнить. 🔡аз теперь у тебя всё хорошо, то я, наверное, пойду? Всё равно надолго я тут остаться не могу,

custom 54272723348158267012custom 54476144810456842532custom 54406940818460139891custom 54494228297810253661

18 Jul 2026, 00:05 UTC36 views6 reactionsread 11 August 2026

— 🔡ожно и так сказать... Да, я пришёл помочь тебе. Кошмары хоть и не снятся таким как ты каждый день, но всё равно неприятно оказаться в одном из них, учитывая, что они могут быть так же опасными для жизни. 🔡асчёт вопроса "кто я" ты уже ответ получал, и он был таков: тебе не нужно знать, кем я являюсь, ты всё равно забудешь. Но если тебе так интересно, то можешь звать меня Кэмуси, и я — путешественник во снах. Кажды

custom 54272723348158267012custom 53821797222832306191custom 54406940818460139891custom 54476144810456842531custom 54494228297810253661

17 Jul 2026, 23:31 UTC23 views6 reactionsread 11 August 2026

🔤сновная часть была позади. Из-за резкого страха мальчишка, кажется, позабыл о слезах и пытался осознать происходящее. Дело оставалось за малым. 🔤адовало, что он не пытался убежать или ещё что, просто стоял как вкопанный. Единственное, что заставляло меня переживать, так это то, что мальчишка явно находился в небольшой стадии шока, и услышит ли он меня сейчас или нет — неизвестно. 🔤ыбора как такового в любом случае

custom 54272723348158267012custom 53821797222832306191custom 54406940818460139891custom 54476144810456842531custom 54494228297810253661

Showing the 12 most recent of 20 posts we hold for @Kemushi_RS. 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,305,666 of 1,481,217entries 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 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.

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.

“𐔌 𐅁𝐍𝖎𝖌𝖍𝖙𝖒𝖆𝖗𝖊 )᷼ ⠷ ꒱” (@Kemushi_RS), 43 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Kemushi_RS.

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.