Telegram RegisterThe public register of Telegram
Telegram profile photo for BLUE SAPPHIRE

Channel

BLUE SAPPHIRE

@sapphe1r0s

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

325subscribers

-1 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-1001566095393
TypeChannel
Username@sapphe1r0s
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/sapphe1r0s

Growth

325326325.57 August 2026 — 326 subscribers8 August 2026 — 326 subscribers15 August 2026 — 325 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net -1. 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 325–326 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 16:37325-1
8 Aug 2026, 07:19326no change
7 Aug 2026, 15:54326first reading

Engagement

20 posts held, back to 27 July 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
26.9%
avg views ÷ 325 subscribers
Avg views / post
87.5
20 posts measured
Reaction rate
2.12%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 8 of 20 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 7 August 2026
Posts held20 (27 July 20267 August 2026)
Views total1,750
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:19 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

16 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 31.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
531.3%
🤣531.3%
👀318.8%
😢212.5%
🥰16.25%

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

Measured over the 20 most recent posts we hold, published 27 July 2026 to 7 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

7 Aug 2026, 10:06 UTC44 views2 reactionsread 8 August 2026

#meme 经群友指示,本频道将成为LLM(Langdon‘s Language Model)概念频道。

😢2

7 Aug 2026, 06:16 UTC54 viewsread 8 August 2026

#吐槽 小道消息说美团把小红书顶级AI网红,300万package的Agent之母招进去了,他们的HR真不上网吗...

7 Aug 2026, 05:24 UTC42 viewsread 8 August 2026
Forwarded from @Gooaye

納斯達克正式宣佈,23小時交易制度(23/5)將於2026年12月6日正式上線,並已獲得美國證券交易委員會(SEC)批准。屆時,美股市場每天僅休市1小時(美東時間20:00-21:00),用於系統清算和數據處理,其餘時間將連續開放交易。

4 Aug 2026, 13:09 UTC134 views3 reactionsread 8 August 2026
Photo

#meme 晚安,维京群岛。 more info

👀3

2 Aug 2026, 11:27 UTC98 views2 reactionsread 8 August 2026

#Rating 《1999!神秘学对策部》5/5 我是一个游戏!我出了两集番剧! 看起来时间线是接着游戏剧情的,不错。拉普拉斯的大家都太可爱了。

2

2 Aug 2026, 09:22 UTC91 viewsread 8 August 2026

我Chovy,映后找演员你给我找好的啊,没见过这么水的映后。

2 Aug 2026, 09:20 UTC90 viewsread 8 August 2026
Photo

#Rating 《八仙!》3.5/5 一款子供向悬疑/警匪片,感觉未来重新把很多现有的电影类型开发出子供向版本是个好主意。

2 Aug 2026, 05:28 UTC75 views1 reactionsread 8 August 2026

#九 期待已久的9泡面番终于上了,等我吃晚饭的时候品鉴一下。

1

2 Aug 2026, 05:27 UTC64 viewsread 8 August 2026
Forwarded from @CFWL1999Photo

#重返未来1999# #1999神秘学对策部# #重返未来泡面番# 不擅长与人交流、性格腼腆的马库斯在一场乌龙中意外成为了“神秘学事件对策部”的负责人。面对星锑、兔毛手袋等一众行事乖张、性格跳脱的怪咖同事,原本连大声说话都会紧张的马库斯,能否在危机中挺身而出,成为凝聚这支奇妙团队的主心骨呢?——看似古怪的他们……实际上真的“不靠谱”吗? 《重返未来:1999》泡面番《1999!神秘学对策部》现已正式开播,欢迎前往收看! ▶▶更新时间◀◀ 8月2日10:00连更2集,后续每周六12:00更新1集 bilibili追番页:https://www.bilibili.com/bangumi/media/md424262502 图文地址:https://www.bilibili.com/opus/1231786830171471895 via 重返未来1999 的 bilibili 动态

31 Jul 2026, 16:01 UTC43 viewsread 8 August 2026

#parody 据说 Dario Amodei 从来不喝白兰地、威士忌和伏特加这类烈酒,因为烈酒是蒸馏得到的。

30 Jul 2026, 14:43 UTC92 views5 reactionsread 8 August 2026

#Daily 反省了一下,有的时候应该抛弃“你都想得到,别人能想不到?”的这种想法。有的时候别人确实想不到。

🤣5

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

29 Jul 2026, 13:35 UTCAnonymous Poll36 voters

你的giffgaff +44还好吗?

  1. 活得好好的39%
  2. 已被杀头14%
  3. 我没有,只是路过47%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 27 July 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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.

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

“BLUE SAPPHIRE” (@sapphe1r0s), 325 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/sapphe1r0s.

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.