Telegram RegisterThe public register of Telegram

Channel

(FREE UNSUBS) RUSHAEUN

@rushaeun

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

380subscribers

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

Growth

3803823816 Aug 2026, 09:40 — 382 subscribers6 Aug 2026, 20:17 — 382 subscribers6 Aug 2026, 23:00 — 380 subscribers6 Aug 2026, 09:406 Aug 2026, 23:00
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 380–382 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 23:00380-2
6 Aug 2026, 20:17382no change
6 Aug 2026, 09:40382first reading

Engagement

19 posts held, back to 10 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
56.4%
avg views ÷ 380 subscribers
Avg views / post
214
6 posts measured
Reaction rate
2.03%
reactions ÷ views · ER floor
Posts in window
7
of 19 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 4 of 6 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 22 July 2026
Posts held19 (10 May 202622 July 2026)
Views total1,285
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20:17 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

209 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 18.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍾3818.2%
3617.2%
🏆3315.8%
custom 5440748683765227563178.13%
🐳178.13%
💘157.18%
🆒146.70%
💋146.70%
🍓136.22%
104.78%
💅20.957%

Custom emoji. One 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 count beside it isTelegram’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 11 of the 19 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 209reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 10 May 2026 to 22 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

22 Jul 2026, 14:23 UTC216 views15 reactionsread 6 August 2026

Hello, Rushy! This is @RUSHAEUN speaking. We hope you're all doing well. Thank you for taking a moment to read this message. After careful consideration, we've decided that starting today, @RUSHAEUN will no longer be using the SFS system. We believe this is the best direction for our team moving forward. Thank you so much to everyone who has supported and collaborated with us through SFS. Every interaction has mean

14🏆1

17 Jul 2026, 20:01 UTC211 views0 reactionsread 6 August 2026

happy mensive! and dont forget to write down your data below, rushy!

17 Jul 2026, 20:00 UTC329 views3 reactionsread 6 August 2026

ㅤㅤㅤㅤㅤㅤ ࣪˖ ♡‌ ᨳ. 🐬🌸。 ࣪ in the midst of the blazing sun and the sparkling beach on 18, we saw the glisten and gathering from across the shore. our buddy @keonhyean @yushowl @Threnodysect @stellianz @ponytella @MinjiReverie @Rustleean @Hospectre @sanemoirr were celebrating a joyous party around us. the festive gala, filled with various warm surprises and vibrant-adorned, revel their monthversary. may this troop a

3

7 Jun 2026, 12:25 UTC629 viewsread 6 August 2026

hi rushy, dari kitaa ada yang ajakin kalian sfs ulang yaa. soalnyaa beberapa ada yang udah samperin bot dari bulan lalu, dan udah kita subs. tapi belum di setor sama kitaaa (takutnyaa yang ajakin udah leave atau rest) jadi kita ajakin ulang

3 Jun 2026, 11:42 UTC838 views18 reactionsread 6 August 2026
Video

ㅤㅤㅤㅤ a boy made of midnight thoughts and a girl made of summer dreams. ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ

🍾5custom 544074868376522756354🏆4

1 Jun 2026, 13:39 UTC503 views14 reactionsread 6 August 2026
Forwarded from @VeIoucityVideo

︎ ︎︎︎︎ ︎ ︎ ︎ ︎︎︎︎ ︎ ︎︎︎︎ ︎ ︎︎ Teenage Years Won't Come Twice ︎ ︎︎︎︎ ︎@Veioucity ︎ ︎︎︎︎ ︎ ︎@Rushaeun ︎ ︎︎︎︎ ︎ ︎ ︎ ︎︎︎︎ ︎ ︎ ︎ ︎@Eyeonus ︎ ︎︎︎︎ ︎ ︎@Kyabubbles

🍾5custom 54407486837652275635🏆4

Showing the 12 most recent of 19 posts we hold for @rushaeun. 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 — 797,435 of 1,160,990entries 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.

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

“(FREE UNSUBS) RUSHAEUN” (@rushaeun), 380 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/rushaeun.

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.