Telegram RegisterThe public register of Telegram

Channel

𓏺 sᴏғᴛ ɢɪʀʟྀི

@Y_ieii

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

862subscribers

-4 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002659036821
TypeChannel
Username@Y_ieii
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/Y_ieii

Growth

8628668649 Aug 2026, 19:16 — 866 subscribers10 Aug 2026, 17:13 — 862 subscribers9 Aug 2026, 19:1610 Aug 2026, 17:13
2 measurements taken within a single day, net -4. 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 861–867 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:13862-4
9 Aug 2026, 19:16866first reading

Engagement

17 posts held, back to 26 April 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
75.2%
avg views ÷ 862 subscribers
Avg views / post
648
7 posts measured
Reaction rate
13.6%
reactions ÷ views · ER floor
Posts in window
7
of 17 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 2 of 7 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 5 August 2026
Posts held17 (26 April 20265 August 2026)
Views total4,537
Reactions total167
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 19: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

579 reactions across 11 posts, in 30 distinct kinds. The most used accounts for 11.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 58232277449509519046511.2%
custom 53595540622011469886010.4%
custom 58255355511381771185910.2%
custom 5805585058681068017488.29%
custom 5197490373299046066386.56%
custom 5814319007821471403386.56%
custom 5309909136522125032366.22%
custom 5823458908680757027345.87%
custom 5312093397975064505305.18%
custom 5359705498453034699274.66%
custom 5361761194354952930244.15%
custom 5309805971407672794142.42%
custom 5812017300487805440142.42%
custom 5911218203073190213132.25%
custom 5399974802582696366111.90%
custom 536205586347119566381.38%
custom 531015247648421803661.04%
custom 591103063755640758361.04%
custom 591122580516530461650.864%
custom 591151654438647379250.864%
10 further kinds386.56%

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

Measured over the 17 most recent posts we hold, published 26 April 2026 to 5 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
4,080
across the posts below
Posts paid on
6
of 17 we hold a reading for · 35%
Most on one post
1,580
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Y_ieii. 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 17 most recent posts we hold for this entry, published 26 April 2026 to 5 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

5 Aug 2026, 20:35 UTC367 views63 reactions500 Starsread 9 August 2026

᷂ذُلَّ ᷂من ᷂لا ᷂لانا ᷂لَہُ 🪽🔤 🎀🎀🎀🎀🎀

custom 581431900782147140338custom 581201730048780544014custom 539997480258269636611

30 Jul 2026, 18:21 UTC865 views104 reactions500 Starsread 9 August 2026

᷂امرأة ᷂مليئة ᷂بالدَّهشة ᷂و ᷂الوضوح ᷂والرِّقہ🥂.

custom 535955406220114698860custom 536176119435495293023custom 535970549845303469921

6 Jul 2026, 09:26 UTC≈1,480 views87 reactions500 Starsread 9 August 2026

୭ ˚. ᵎ⋆˚꩜。.♡ྀི୭ ˚. ᵎ⋆˚꩜。.♡ྀི୭ ˚. ᵎ - ᷂انا ᷂حيثُ ᷂الأقليّـة ، ᷂لنّ ᷂تجدني ᷂فِي ᷂الضجِيج🌟 .

custom 580558505868106801748custom 519749037329904606638custom 53597054984530346991

27 Jun 2026, 15:52 UTC≈1,500 views2 reactionsread 9 August 2026

🪦🌟🪦🪦🎀🪦🪦🪦🌟

custom 53620558634711956632

27 Jun 2026, 15:52 UTC≈1,650 views136 reactions500 Starsread 9 August 2026

᷂ذات ᷂دَلال ᷂وحُسن ᷂مُلفتة ᷂للنّظر🎀 𝘪𝘵 𝘴 𝘷𝘦𝘳𝘺 𝘨𝘰𝘰𝘥 𝘵𝘰 𝘭𝘰𝘰𝘬🤍

custom 582553555113817711847custom 582322774495095190434custom 582345890868075702734custom 530990913652212503220custom 53617611943549529301

27 Jun 2026, 15:52 UTC≈1,350 views6 reactionsread 9 August 2026
Photo

🤔🤔 💗🎀🤔🤔

custom 53620558634711956636

9 May 2026, 21:04 UTC≈1,800 views3 reactionsread 9 August 2026

🪦🪦🪦🎀🪦🪦🪦

custom 53597054984530346993

Showing the 12 most recent of 17 posts we hold for @Y_ieii. 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 — 1,093,248 of 1,480,688entries 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.

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

“𓏺 sᴏғᴛ ɢɪʀʟྀི” (@Y_ieii), 862 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Y_ieii.

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.