Telegram RegisterThe public register of Telegram

Channel

шизамунрет

@moonrettt

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

300subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002681820371
TypeChannel
Username@moonrettt
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/moonrettt

Growth

299300299.56 August 2026 — 300 subscribers6 August 2026 — 299 subscribers6 August 2026 — 299 subscribers14 August 2026 — 300 subscribers6 August 202614 August 2026
4 measurements spanning 8 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 299–300 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 16:06300+1
6 Aug 2026, 22:33299no change
6 Aug 2026, 20:20299-1
6 Aug 2026, 17:47300first reading

Engagement

18 posts held, back to 11 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
87.8%
avg views ÷ 300 subscribers
Avg views / post
264
6 posts measured
Reaction rate
17.7%
reactions ÷ views · ER floor
Posts in window
6
of 18 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 6 August 2026
Posts held18 (11 May 20266 August 2026)
Views total1,581
Reactions total280
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:33 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

959 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 16.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 538432156663915389115516.2%
custom 521789325036647832515416.1%
custom 521747057833991135312112.6%
custom 536848911459526382810210.6%
custom 62851977172536575329710.1%
custom 5217485645085185715879.07%
custom 5274120007268212392808.34%
custom 6284995879560549461727.51%
custom 5273884226448560649424.38%
custom 5204161677280447050303.13%
custom 5217682891458256352161.67%
custom 527379703431748281830.313%

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

Measured over the 18 most recent posts we hold, published 11 May 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.

Telegram Stars

Stars received
9
across the posts below
Posts paid on
3
of 18 we hold a reading for · 17%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @moonrettt. 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 18 most recent posts we hold for this entry, published 11 May 2026 to 6 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

6 Aug 2026, 16:39 UTC68 views24 reactionsread 6 August 2026
Photo

• оно живое.💗 (нет, умираю от жары)

custom 521789325036647832513custom 53684891145952638284custom 62851977172536575324custom 52174705783399113533

30 Jul 2026, 05:12 UTC191 views47 reactionsread 6 August 2026
Photo

• коммишечко коммишки кмм.💗

custom 538432156663915389120custom 521789325036647832510custom 52174705783399113538custom 53684891145952638286custom 52174856450851857151custom 62849958795605494611custom 62851977172536575321

24 Jul 2026, 14:17 UTC302 views54 reactionsread 6 August 2026
Photo

• ладно, скетч с Нией вам все таки покажу.я его вчера ещё наскетчила , но сначала не хотела постить в основу .🌟

custom 521747057833991135320custom 628519771725365753216custom 521748564508518571510custom 53684891145952638285custom 53843215666391538912custom 62849958795605494611

24 Jul 2026, 11:36 UTC288 views34 reactionsread 6 August 2026
Video

• немного sad видео по дзяге.

custom 527412000726821239219custom 53684891145952638287custom 52174856450851857155custom 52178932503664783252custom 53843215666391538911

23 Jul 2026, 14:18 UTC306 views54 reactionsread 6 August 2026
Photo

• вам снился этот человек?💗

custom 538432156663915389125custom 527412000726821239213custom 536848911459526382813custom 52178932503664783252custom 62851977172536575321

18 Jul 2026, 05:58 UTC426 views67 reactionsread 6 August 2026
Photo

• 🤩 草光り夏乱れ . ( The grass shines brightly, summer is in full swing. )🤩 🤩🤩 🤩 

custom 521747057833991135322custom 538432156663915389116custom 536848911459526382814custom 52178932503664783255custom 52174856450851857153custom 52741200072682123923custom 62849958795605494612custom 62851977172536575322

14 Jul 2026, 18:01 UTC388 views65 reactionsread 6 August 2026
Photo

• мне стало скучно.а ещё мне дали тег худа в крупном дс серваке по денди.🤩

custom 521789325036647832525custom 521747057833991135315custom 536848911459526382812custom 52741200072682123923custom 62849958795605494613custom 62851977172536575323custom 52174856450851857152custom 53843215666391538912

14 Jul 2026, 15:06 UTC372 views49 reactionsread 6 August 2026
Photo

• вот они, слево на право.чонгук, чимин...💗

custom 521748564508518571521custom 628519771725365753211custom 53843215666391538918custom 53684891145952638285custom 52174705783399113531custom 52178932503664783251custom 52741200072682123921custom 62849958795605494611

12 Jul 2026, 08:22 UTC≈1,080 views62 reactionsread 6 August 2026
Photo

• гифтец о великой оливер. 💗

custom 521747057833991135322custom 628499587956054946115custom 628519771725365753213custom 52741200072682123925custom 52174856450851857152custom 52178932503664783252custom 53843215666391538912custom 53684891145952638281

1 Jul 2026, 20:52 UTC609 views60 reactionsread 6 August 2026
Photo

• я наврала про веселые картинки.💗

custom 628499587956054946125custom 527412000726821239218custom 536848911459526382812custom 62851977172536575323custom 52174856450851857151custom 53843215666391538911

23 Jun 2026, 12:58 UTC698 views42 reactionsread 6 August 2026
Photo

• адопти были, всех купили.радостна.💔

custom 521789325036647832518custom 538432156663915389110custom 52741200072682123926custom 62851977172536575323custom 52174705783399113532custom 52174856450851857151custom 53684891145952638281custom 62849958795605494611

19 Jun 2026, 12:35 UTC798 views61 reactions1 Starread 6 August 2026
Photo

• мега работа на дтиус от кто это вообще 🔎 лайк репост отписка и спасиба за звездочку, а лов ю 🫰

custom 521748564508518571531custom 536848911459526382813custom 628519771725365753211custom 52178932503664783252custom 52741200072682123922custom 52174705783399113531custom 53843215666391538911

Showing the 12 most recent of 18 posts we hold for @moonrettt. 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 — 271,809 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

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

“шизамунрет” (@moonrettt), 300 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/moonrettt.

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.