Telegram RegisterThe public register of Telegram
Telegram profile photo for ‌ ‌ ‌‌ ‌ 𝓢𝗍𝖺𝗋𝗅ı𝗀𝗁𝗍

Channel

‌ ‌ ‌‌ ‌ 𝓢𝗍𝖺𝗋𝗅ı𝗀𝗁𝗍

@starryrina

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

96subscribers

+38 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002292347427
TypeChannel
Username@starryrina
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 October 2026
Last confirmed live16 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 October 2026
On Telegramt.me/starryrina

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 40% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

58967712 August 2026 — 58 subscribers12 September 2026 — 62 subscribers30 September 2026 — 60 subscribers10 October 2026 — 88 subscribers12 October 2026 — 88 subscribers16 October 2026 — 96 subscribers12 August 202616 October 2026
6 measurements spanning 65 days, net +38. 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 52–102 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Oct 2026, 13:5596+8
12 Oct 2026, 00:2288no change
10 Oct 2026, 00:3988+28
30 Sept 2026, 17:3560-2
12 Sept 2026, 12:2162+4
12 Aug 2026, 23:1758first reading

Engagement

19 posts held, back to 6 October 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
93.1%
avg views ÷ 96 subscribers
Avg views / post
89.4
19 posts measured
Reaction rate
13.0%
reactions ÷ views · ER floor
Posts in window
19
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 16 of 19 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 11 October 2026
Posts held19 (6 October 2026 – 11 October 2026)
Views total1,698
Reactions total205
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Oct 2026, 00:22 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

Video runtime
54s
Average length
14s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

205 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 27.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52355074652981347715627.3%
custom 52943070149843571483014.6%
custom 57826969632123211732914.1%
custom 58976771590313827312210.7%
custom 5897621401765946206188.78%
custom 5780841730613977401167.80%
custom 546064544618148786273.41%
custom 578090235837232697862.93%
custom 586143578690106757062.93%
custom 592493939951822979162.93%
custom 547234882833614649652.44%
custom 586193377547413624641.95%

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 are Telegram’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 16 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 205 reactions 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 6 October 2026 to 11 October 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

11 Oct 2026, 20:30 UTC48 views7 reactionsread 12 October 2026

خدایا خودت بهم نامجون بده

custom 52355074652981347715custom 52943070149843571481custom 54606454461814878621

11 Oct 2026, 11:18 UTC62 views1 reactionsread 12 October 2026

she's in everywhere slaying btw

custom 54606454461814878621

11 Oct 2026, 11:16 UTC64 views7 reactionsread 12 October 2026
Video

Video, posted without a caption

custom 52355074652981347713custom 59249393995182297912custom 52943070149843571481custom 54606454461814878621

11 Oct 2026, 11:16 UTC63 views8 reactionsread 12 October 2026
Photo

Photo, posted without a caption

custom 52355074652981347713custom 52943070149843571482custom 57826969632123211732custom 58976771590313827311

11 Oct 2026, 11:16 UTC63 views8 reactionsread 12 October 2026
Photo

Photo, posted without a caption

custom 58619337754741362463custom 54606454461814878622custom 58976771590313827312custom 52943070149843571481

10 Oct 2026, 21:55 UTC95 views19 reactionsread 12 October 2026
File

File, posted without a caption

custom 57808417306139774018custom 52355074652981347716custom 59249393995182297914custom 58619337754741362461

10 Oct 2026, 16:39 UTC97 views8 reactionsread 12 October 2026
Forwarded from @MehrsaCottage

وحشتناک‌ترین بخش ماجرا اینجاست که حتی دیگه نمی‌تونی راجع بهش بنویسی. اون‌قدر گره افکار مرتبط بهش، کور می‌شه که دیگه خودت هم نمی‌تونی بازش کنی. می‌خوای کلمه بنویسی، ازش بنویسی و بگی چی سرت اومد، ولی... نتیجه فقط یه کاغذ پر از دایره‌های سیاه منحنی برهمه.

custom 52355074652981347716custom 57826969632123211731custom 58976771590313827311

9 Oct 2026, 21:01 UTC122 views30 reactionsread 12 October 2026

1:35 take my heaven for free, your words and face don't kill me, you know you're not lovable, I'm happy where the devils are.

custom 578269696321232117315custom 58976771590313827316custom 52943070149843571485custom 52355074652981347714

9 Oct 2026, 21:01 UTC121 views29 reactionsread 12 October 2026
File

File, posted without a caption

custom 523550746529813477113custom 58614357869010675706custom 58976771590313827316custom 57826969632123211734

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

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

“‌ ‌ ‌‌ ‌ 𝓢𝗍𝖺𝗋𝗅ı𝗀𝗁𝗍” (@starryrina), 96 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/starryrina.

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.