Telegram RegisterThe public register of Telegram
Telegram profile photo for StarRy bloodline

Channel

StarRy bloodline

@StarRy1Empire

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002635269037
TypeChannel
Username@StarRy1Empire
Created3 April 2025 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live12 October 2026
Measurements held2
On Telegramt.me/StarRy1Empire

Growth

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 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–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:032no change
7 Aug 2026, 15:412first reading

Engagement

3 posts held, back to 3 April 2025 — 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 4 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

14 reactions across 2 posts, in 5 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🗿750.0%
⚡214.3%
👻214.3%
😇214.3%
🔥17.14%

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

Measured over the 3 most recent posts we hold, published 3 April 2025 to 4 June 2025, 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

4 Jun 2025, 20:36 UTC108 views6 reactionsread 14 August 2026
Photo

🎉 IPL 2025 Success! Recap 🎉 What a season it’s been! Over the course of IPL 2025, we crossed 2400+ followers across our 3 Telegram channels — CIL(800+), CRXC(250+), and CrixZy(1350+)! 💥 But that’s not all — we also hit a massive 220,000+ web page views 👁️‍🗨️ That’s right — 220K+ fans, that watch our live page during this IPL season Thank you to everyone who joined the ride — we're just getting started. Bigger thi…

⚡2👻2🗿2

3 Apr 2025, 18:16 UTC203 views8 reactionsread 14 August 2026

𝑆𝑜𝑚𝑒 𝑠𝑡𝑎𝑟𝑠 𝑎𝑛𝑑 𝑎 𝑐𝑒𝑙𝑒𝑠𝑡𝑖𝑎𝑙 𝑏𝑜𝑑𝑦 𝑓𝑟𝑜𝑚 𝑜𝑢𝑟 ℎ𝑒𝑎𝑟𝑡 𝑜𝑓 𝑡ℎ𝑒 𝑔𝑎𝑙𝑎𝑥𝑦 𝑐𝑟𝑖𝑐𝑘𝑒𝑡 𝑠𝑡𝑢𝑓𝑓 🏏 | | 𝐶𝑅𝑋𝑐- 𝐽𝑂𝐼𝑁 | | 𝐶𝐼𝐿- 𝐽𝑂𝐼𝑁 | | 𝐶𝑅𝐼𝑋𝑍𝑌🌟- 𝐽𝑂𝐼𝑁 𝑠𝑜𝑚𝑒 𝑑𝑤𝑎𝑟𝑓 𝑠𝑡𝑎𝑟𝑠 🎆 | |. 𝐶𝑂𝑆𝑀𝑂 🍽 𝐽𝑂𝐼𝑁 | | 𝐵𝐻𝐴𝐺𝑊𝐴𝑇 𝑆𝑇𝑈𝐹𝐹 𝐽𝑂𝐼𝑁 | | 𝐴𝐿𝐵𝐸𝑅𝑇-𝐸𝐴𝐼𝑁𝑆𝑇𝐸𝐼𝑁-𝐽𝑂𝐼𝑁 | |. 𝐽𝐸𝐸-𝑁𝐸𝐸𝑇 𝑆𝑇𝑈𝐹𝐹 ----𝐽𝑂𝐼𝑁 | | Apex-Blood----join

🗿5😇2🔥1

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

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.

“StarRy bloodline” (@StarRy1Empire), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/StarRy1Empire.

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.