Telegram RegisterThe public register of Telegram
Telegram profile photo for [🌸] ˏˋ°•* || 𝙎𝙖𝙠𝙪𝙧𝙖 𝗽𝗼𝗿𝘁!

Channel

[🌸] ˏˋ°•* || 𝙎𝙖𝙠𝙪𝙧𝙖 𝗽𝗼𝗿𝘁!

@sakurayuic

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

13subscribers

+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-1003984362731
TypeChannel
Username@sakurayuic
CreatedBetween 1 April 2026 and 10 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/sakurayuic

Growth

1113126 August 2026 — 11 subscribers12 August 2026 — 11 subscribers13 August 2026 — 13 subscribers6 August 202613 August 2026
3 measurements spanning 7 days, 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:3513+2
12 Aug 2026, 06:1611no change
6 Aug 2026, 12:0711first reading

Engagement

18 posts held, back to 10 June 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
680.2%
avg views ÷ 13 subscribers
Avg views / post
88.4
7 posts measured
Reaction rate
8.56%
reactions ÷ views · ER floor
Posts in window
7
of 18 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held18 (10 June 20268 August 2026)
Views total619
Reactions total53
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 06:16 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

152 reactions across 18 posts, in 20 distinct kinds. The most used accounts for 13.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54156944473105776432113.8%
custom 53259693979263649272013.2%
💘2013.2%
custom 52717530980360155501811.8%
custom 5348417899197396977159.87%
custom 537741363572956075285.26%
custom 541602842826248103285.26%
custom 536198257414927830474.61%
custom 536390583902959248074.61%
custom 519313064648616210763.95%
custom 531210196643481790842.63%
custom 545864786977700720342.63%
custom 528761432636078884131.97%
custom 532374968581334383421.32%
custom 535262756844289872721.32%
custom 538227937411442191821.32%
custom 546080824262186037521.32%
custom 533687153675210945310.658%
custom 534586610880299665410.658%
custom 541570652905357948810.658%

Custom emoji. 19 of the rows above are 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 18 of the 18 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 152reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 10 June 2026 to 8 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.

Telegram Stars

Stars received
31
across the posts below
Posts paid on
4
of 18 we hold a reading for · 22%
Most on one post
13
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sakurayuic. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 10 June 2026 to 8 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Aug 2026, 17:47 UTC29 views4 reactionsread 12 August 2026
Photo

work №31 | name: Arlecchino | banner

custom 52876143263607888412custom 51931306464861621071custom 53121019664348179081

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 ` [why me?]

8 Aug 2026, 17:15 UTC32 views5 reactionsread 12 August 2026
Photo

work №30 | name: Mugi | banner

custom 51931306464861621073custom 52876143263607888411custom 53121019664348179081

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 ` [why me?]

4 Aug 2026, 18:46 UTC75 views6 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿➿➿ work №29 | name: Linnea ☁️ | banner

custom 51931306464861621072custom 53121019664348179082custom 54608082426218603752

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 ` [why me?]

2 Aug 2026, 14:47 UTC81 views4 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ work №28 | name: Sua 💜 |banner

custom 53526275684428987272custom 53368715367521094531custom 53458661088029966541

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 ` [why me?]

22 Jul 2026, 10:37 UTC132 views15 reactionsread 12 August 2026

[🪄] что ж, по окончанию опроса вот такие итогии 😀😀 ✨✨✨✨✨✨✨✨ 🔤орядок выполнения баннеров: 🌸🌸🌸🌸 • 🌸 • Линнея • 🌸• Суа • 🌸 • Шарлотта • 🌸 • Моланг 🌸🌸🌸🌸

custom 53259693979263649276custom 53619825741492783043custom 54156944473105776433custom 52717530980360155501custom 53639058390295924801custom 53774136357295607521

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 .

19 Jul 2026, 20:58 UTC152 views10 reactions13 Starsread 12 August 2026

➿➿➿➿➿➿➿➿➿➿➿➿ 🙂🙂🙂🙂 🍼🍼 𝑺𝒂𝒌𝒖𝒓𝒂 𝒚𝒖𝒌𝒊 🍼intj [🏁] - [私は彼氏をとても愛しています] [🌸]𝒕𝒊𝒎𝒆 𝒛𝒐𝒏𝒆 - 𝑼𝑻𝑪+5 (𝑮𝑴𝑻+5) [🌸]𝒐𝒓𝒊𝒆𝒏𝒕𝒂𝒕𝒊𝒐𝒏 - 𝒃𝒊𝒔𝒆𝒙𝒖𝒂𝒍 [🌸]𝒓𝒆𝒍𝒂𝒕𝒊𝒐𝒏𝒔𝒉𝒊𝒑 ✔️ [🌸]𝒃𝒅𝒂𝒚 - 25.09 [🌸]𝒆𝒙𝒕𝒓𝒐𝒗𝒆𝒓𝒕 ✔️ [🌸]𝒂𝒏𝒙𝒊𝒐𝒖𝒔 𝒂𝒕𝒕𝒂𝒄𝒉𝒎𝒆𝒏𝒕 𝒔𝒕𝒚𝒍𝒆 ✔️ ➿➿➿➿➿➿➿➿➿➿➿➿

custom 54586478697770072034custom 53259693979263649272custom 53639058390295924802custom 52717530980360155501custom 53619825741492783041

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 .

19 Jul 2026, 11:13 UTC118 views9 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ work №27 | name: Diluc🌟| avatar

custom 54156944473105776434custom 53619825741492783043custom 53639058390295924802

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 .

17 Jul 2026, 22:34 UTC113 views8 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ work #26 | name: Angel | avatar

custom 52717530980360155503custom 54156944473105776433custom 53259693979263649272

Signed #ˏˋ°•* . 𝙨𝙖𝙠𝙪𝙧𝙖 𝙮𝙪𝙠𝙞 .

13 Jul 2026, 12:42 UTC119 views8 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ 🍓 id. - @Mad1nkss work №25 | name: Power | banner

custom 52717530980360155503custom 53774136357295607523custom 53639058390295924802

13 Jul 2026, 12:20 UTC102 views10 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ 🍓 id. - @dry_texter work №24 | name: Mononga | banner

custom 52717530980360155503custom 53774136357295607523custom 53259693979263649272custom 54156944473105776432

11 Jul 2026, 20:01 UTC106 views12 reactionsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ work №23 | name: Sakura | banner

custom 52717530980360155504custom 53259693979263649274custom 54156944473105776434

3 Jul 2026, 12:32 UTC122 views11 reactions6 Starsread 12 August 2026
Photo

➿➿➿➿➿➿➿➿➿➿➿➿ work №22 | name: Nana | banner

💘3custom 53259693979263649273custom 53237496858133438342custom 54156944473105776432custom 54157065290535794881

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 409,910 of 1,548,671entries 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

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

“[🌸] ˏˋ°•* || 𝙎𝙖𝙠𝙪𝙧𝙖 𝗽𝗼𝗿𝘁!” (@sakurayuic), 13 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/sakurayuic.

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.