Posted without readable text

Channel
💘”/𝓼𝔀𝓮𝓮𝓽 ᵉᶰᵗ
@sweet_entt
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
29subscribers
+0 since we began measuring on 8 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004355366567 |
|---|---|
| Type | Channel |
| Username | @sweet_entt |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 November 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sweet_entt |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 09:22 | 29 | no change |
| 8 Nov 2026, 08:47 | 29 | first reading |
Engagement
20 posts held, back to 7 November 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
- 67.2%
- avg views ÷ 29 subscribers
- Avg views / post
- 19.5
- 19 posts measured
- Reaction rate
- 19.9%
- 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 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 20 (7 November 2026 – 8 November 2026) |
| Views total | 370 |
| Reactions total | 33 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 09: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
- Photos
- 11
- Videos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 8 November 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
33 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 30.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🦄 | 10 | 30.3% | |
| custom 5391143933210297862 | 5 | 15.2% | |
| 💘 | 5 | 15.2% | |
| custom 5391080457888630125 | 3 | 9.09% | |
| 🆒 | 3 | 9.09% | |
| custom 5389083027513048994 | 2 | 6.06% | |
| custom 5391034626292615280 | 2 | 6.06% | |
| custom 5215445866332059048 | 1 | 3.03% | |
| custom 5389079260826733012 | 1 | 3.03% | |
| 🐳 | 1 | 3.03% |
Custom emoji. 6 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 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 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 33 reactions 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 7 November 2026 to 8 November 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
Telegram’s own ‘edited’ marker: 1 of 20 posts held from the last 30 days (5.00%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
୨୧ ⚠️ 🤩АБОР В GL!TCH ⚠️ ୨୧ 𖦹 😀l!tch—группа с прототипом aespa🤩 ➿➿➿➿➿➿➿➿➿➿ анкета: ୨ৎ 01. ⚠️ Ⲡⲥⲉⲃⲇⲟⲏυⲙ : ୨ৎ 02. ⚠️ 00.00.0000 : ୨ৎ 03. ⚠️ Ⲥⲟⲗⲟ / Ⲅⲣⲩⲡⲡⲁ / Ⲧⲣⲉύⲏυ : ୨ৎ 04. 🤩 Ⲃⲁⲱⲉ ⲯυⲃⲟⲧⲏⲟⲉ (эⲙⲟⲇⳅυ / ⲧⲟⲧⲉⲙ) ୨ৎ 05. 🖥️ Ⲩⲙⲉⲉⲧⲉ ⲡⲟⲗьⳅⲟⲃⲁⲧьⲥя Ⲃⲁⲛⲇⳑⲁⲃ? : ୨ৎ 06. 💚 Ⲃⲁⲱ ⲧυⲡ ⲗυⳡⲏⲟⲥⲧυ? (ⲘⲂⲦⲒ) : ୨ৎ 07. 🤩 Ⲯⲉⲗⲁⲉⲙыύ ⲡⲣⲟⲧⲟⲧυⲡ?: 😈 анкету заполнить строго по пунктам! писать: @sweet_enterbot 😃
custom 53911439332102978625🦄3custom 53910804578886301252💘1custom 52154458663320590481custom 53890792608267330121custom 53890830275130489941custom 53910346262926152801
Signed шуві шака
Sticker, posted without a caption
💘1
Sticker, posted without a caption
🆒1
╭─⊹₊˚ 🩷🫧 ˚₊⊹─╮ 🍬 ୨୧ 𝓢𝓦𝓔𝓔𝓣 𝓟𝓡𝓞𝓕𝓘𝓛𝓔 ୨୧ 🍬 ╰─⊹₊˚ 🩵🍭 ˚₊⊹─╯ ୨୧ 🩷 𝓓𝓘𝓡𝓔𝓒𝓣𝓞𝓡 🩷 ୨୧ ╭┈┈┈┈┈┈┈┈┈┈╮ 🫧 𝓢𝓣𝓐𝓖𝓔 𝓝𝓐𝓜𝓔: Shuvi 🍭 𝓑𝓘𝓡𝓣𝓗𝓓𝓐𝓨: 04.09 🍬 𝓜𝓑𝓣𝓘 ୨୧: ╰┈┈┈┈┈┈┈┈┈┈╯ 🩷₊˚⊹ 🍬 ⊹˚₊🩵₊˚⊹ 🍭 ⊹˚₊🩷 🍬🩷 𝓜𝓘𝓛𝓚𝓘𝓢 🩵🍭
🦄4💘1custom 53910804578886301251
5 реакций=2 профайл
╭─⊹₊˚ 🩷🫧 ˚₊⊹─╮ 🍬 ୨୧ 𝓢𝓦𝓔𝓔𝓣 𝓟𝓡𝓞𝓕𝓘𝓛𝓔 ୨୧ 🍬 ╰─⊹₊˚ 🩵🍭 ˚₊⊹─╯ ୨୧ 🩷 𝓓𝓘𝓡𝓔𝓒𝓣𝓞𝓡 🩷 ୨୧ ╭┈┈┈┈┈┈┈┈┈┈╮ 🫧 𝓢𝓣𝓐𝓖𝓔 𝓝𝓐𝓜𝓔: Milkis 🍭 𝓑𝓘𝓡𝓣𝓗𝓓𝓐𝓨: 13.02 🍬 𝓜𝓑𝓣𝓘 ୨୧: ENFP ╰┈┈┈┈┈┈┈┈┈┈╯ 🩷₊˚⊹ 🍬 ⊹˚₊🩵₊˚⊹ 🍭 ⊹˚₊🩷 🍬🩷 𝓜𝓘𝓛𝓚𝓘𝓢 🩵🍭
🆒2🐳1💘1🦄1custom 53890830275130489941
через минуту кидаю профайл!
💘1
новый директор…
profiles?
4 minutes
are you ready??
Showing the 12 most recent of 20 posts we hold for @sweet_entt. 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“💘”/𝓼𝔀𝓮𝓮𝓽 ᵉᶰᵗ” (@sweet_entt), 29 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/sweet_entt.
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.