Telegram RegisterThe public register of Telegram

Channel

эсхе 50% quaso

@silkyashe

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

1,035subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001984771155
TypeChannel
Username@silkyashe
Created18 March 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/silkyashe

Growth

1,0351,0361,035.57 August 2026 — 1,035 subscribers7 August 2026 — 1,035 subscribers10 August 2026 — 1,036 subscribers13 August 2026 — 1,035 subscribers7 August 202613 August 2026
4 measurements spanning 6 days. 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 1,035–1,036 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:251,035-1
10 Aug 2026, 04:311,036+1
7 Aug 2026, 11:181,035no change
7 Aug 2026, 10:471,035first reading

Engagement

12 posts held, back to 13 January 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
52.5%
avg views ÷ 1,035 subscribers
Avg views / post
543
2 posts measured
Reaction rate
29.0%
reactions ÷ views · ER floor
Posts in window
2
of 12 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 1 August 2026
Posts held12 (13 January 20261 August 2026)
Views total1,086
Reactions total315
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 10: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

2,235 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
76934.4%
custom 529188647449554727850522.6%
❤‍🔥42419.0%
💋30413.6%
💘1165.19%
🍓411.83%
🔥381.70%
💯180.805%
custom 5395411099182978508130.582%
💔70.313%

Custom emoji. 2 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 12 of the 12 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 2,235reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Telegram Stars

Stars received
247
across the posts below
Posts paid on
9
of 12 we hold a reading for · 75%
Most on one post
116
single highest reading

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

1 Aug 2026, 06:40 UTC443 views129 reactions70 Starsread 7 August 2026
Photo

дудлы

65custom 529188647449554727833❤‍🔥22🍓2💋2💯2🔥2💘1

28 Jul 2026, 18:54 UTC643 views186 reactions26 Starsread 7 August 2026
Photo

Photo, posted without a caption

💋9453custom 529188647449554727829💘4🍓3🔥2❤‍🔥1

11 Jul 2026, 18:45 UTC≈1,100 views183 reactions116 Starsread 7 August 2026
Photo

Photo, posted without a caption

99custom 529188647449554727843🔥28💋4💘4🍓3❤‍🔥2

7 Jul 2026, 08:14 UTC967 views116 reactionsread 7 August 2026
Photo

что-то старое и не очень

custom 52918864744955472786026💯14💘6❤‍🔥4💋3🔥2🍓1

18 Jun 2026, 07:22 UTC≈1,420 views163 reactionsread 7 August 2026
Photo

😮

custom 529188647449554727876❤‍🔥4128🍓5💋4🔥4💘3💯2

27 May 2026, 17:19 UTC≈1,520 views183 reactions5 Starsread 7 August 2026
Photo

какой-то кантрисайд наброске

💋93custom 52918864744955472784534❤‍🔥7🍓2💘2

22 May 2026, 05:07 UTC≈1,800 views189 reactions10 Starsread 7 August 2026
Photo

Photo, posted without a caption

❤‍🔥90💋44💘32custom 5291886474495547278128🍓3

1 May 2026, 14:06 UTC≈1,720 views197 reactionsread 7 August 2026
Photo

Photo, posted without a caption

99❤‍🔥48custom 529188647449554727831💋8🍓5💔3💘3

12 Apr 2026, 06:24 UTC≈2,120 views252 reactions3 Starsread 7 August 2026
Photo

Photo, posted without a caption

125custom 529188647449554727865❤‍🔥45💋10🍓4💘3

3 Mar 2026, 04:20 UTC≈3,210 views234 reactions10 Starsread 7 August 2026
Photo

хэппи безде ту ми

121❤‍🔥55custom 529188647449554727839custom 539541109918297850811🍓4💘4

13 Feb 2026, 08:52 UTC≈2,170 views194 reactions1 Starread 7 August 2026
Photo

всем приве что-то скетчу

❤‍🔥104💘46custom 529188647449554727835🍓43custom 53954110991829785082

13 Jan 2026, 20:06 UTC≈2,040 views209 reactions6 Starsread 7 August 2026
Photo

не серчайте у меня сессия

108💋42custom 529188647449554727837💘8❤‍🔥5🍓5💔4

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 842,122 of 1,345,403entries 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.

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

“эсхе 50% quaso” (@silkyashe), 1,035 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/silkyashe.

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.