Telegram RegisterThe public register of Telegram
Telegram profile photo for Sai's secret 🎧🗝

Channel

Sai's secret 🎧🗝

@SaiR0yal

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

330subscribers

-2 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-1002146321418
TypeChannel
Username@SaiR0yal
CreatedBetween 1 December 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/SaiR0yal

Growth

33033233111 Aug 2026, 02:47 — 332 subscribers11 Aug 2026, 22:42 — 330 subscribers11 Aug 2026, 02:4711 Aug 2026, 22:42
2 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 330–332 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:42330-2
11 Aug 2026, 02:47332first reading

Engagement

15 posts held, back to 6 August 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
13.4%
avg views ÷ 330 subscribers
Avg views / post
44.1
15 posts measured
Reaction rate
17.3%
reactions ÷ views · ER floor
Posts in window
15
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. It is computed over the 6 of 15 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 10 August 2026
Posts held15 (6 August 202610 August 2026)
Views total661
Reactions total57
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 02: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

57 reactions across 6 posts, in 28 distinct kinds. The most used accounts for 15.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5399881030561708458915.8%
custom 5438367300493262582915.8%
custom 5920292133234807933610.5%
custom 538209594465114259735.26%
custom 539306628755753866135.26%
custom 523141655189836716823.51%
custom 532592459282753145123.51%
custom 546532412585570919223.51%
custom 585965951727646182223.51%
custom 522443133305229727711.75%
custom 522443540468128848911.75%
custom 522468609762738782211.75%
custom 528525717958926221011.75%
custom 532356252831845749611.75%
custom 532364166738585362811.75%
custom 532582634115566568411.75%
custom 535296336616595669711.75%
custom 538191808146548144311.75%
custom 543142133764825644311.75%
custom 546071554004775656211.75%
8 further kinds814.0%

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 6 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 57reactions 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 August 2026 to 10 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

10 Aug 2026, 23:33 UTC6 viewsread 11 August 2026
Forwarded from @OSCAT_1Photo

فعالية خفيفة لطيفة😼🍓 حولوا المنشور واخذكم من الاحصائيات الفكره: اطيكم رياكشنات مع وضعيات للرسم الهدف : وصولنه 264🍓

10 Aug 2026, 17:56 UTC20 views7 reactionsread 11 August 2026
Photo

_ #30Days / 3 ✦ ✦ ✦ _ Marios!★°•~

custom 52314165518983671682custom 52244313330522972771custom 52244354046812884891custom 52246860976273878221custom 52852571795892622101custom 54607155400477565621

9 Aug 2026, 20:19 UTC86 views21 reactionsread 11 August 2026
Photo

_ #30Days / 2 _wip ✦ ✦ ✦ _ Marios!★°•~

custom 54383673004932625829custom 59202921332348079336custom 53529633661659566971custom 53998810305617084581custom 54314213376482564431custom 58593161088713428041custom 59133634705180666901custom 59133777341044568091

8 Aug 2026, 22:00 UTC48 views3 reactionsread 11 August 2026

كانت أنظار الجميع مثبتةً على ساي الآن، تكاد نظراتهم تثقب رأسه، بينما كان ينظر إلى الأرض بعينين واسعتين وخائفتين، لا تعلمان ماذا تفعلان، وكانت أذناه متدليتين إلى الأسفل. ولم يقطع خوفه إلا صوت ناگيرا وهو يأمره بالتحرك. ركض ساي وراءه، محاولًا تجنب البلبلة والنميمة التي كان الطلاب الباقون يتهامسون بها حوله. قاد ناگيرا ساي بصمت عبر ممرات بناية فرسان الجناح الأبيض، حتى وصلا إلى غرفةٍ في أعماقها، وكانت الغرف مقسمةً إلى قسمي

custom 53235625283184574961custom 53930662875575386611custom 53998810305617084581

8 Aug 2026, 22:00 UTC82 views3 reactionsread 11 August 2026

نيران زرقاء 🎐 الفصل ⁰⁴ #روايه غطَّ ساي في نومٍ عميق، بينما كان الظلام يبتلع المكان، ولا يُسمع سوى صرصار الليل وهمسات الحراس خارج باب الغرفة. فُتح الباب، ودخل أحد الحارسين وأيقظ ساي. "انهض، إلى متى ستنام..؟" فتح ساي عينيه، وجلس على الفراش يفرك عينه بيده. "كم الساعة..؟" سأل ساي مستغربًا، فقد كان الظلام لا يزال يعمُّ المكان. "إنها الرابعة صباحًا، والآن قم وغيِّر ملابسك إلى الزي، ثم اصعد إن لم تكن تريد أن أجرَّك بنفسي

custom 53820959446511425972custom 53258263411556656841

8 Aug 2026, 19:20 UTC48 views16 reactionsread 11 August 2026
Photo

_ #30Days / 1 ✦ ✦ ✦ _ little Sai!★°•~

custom 53998810305617084587custom 53930662875575386612custom 54653241258557091922custom 53819180814654814431custom 53820959446511425971custom 54608689820493764471custom 54653338067119959271custom 54654463563299890831

8 Aug 2026, 11:34 UTC41 viewsread 11 August 2026

الكل يكدر يشارك و الي يشارك خل يكتب بتعليقات التحدي حتى بالنهايه انشر قنواتكم 🤏🏻

Showing the 12 most recent of 15 posts we hold for @SaiR0yal. 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 — 565,154 of 1,480,975entries 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 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.

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.

“Sai's secret 🎧🗝” (@SaiR0yal), 330 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/SaiR0yal.

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.