Telegram RegisterThe public register of Telegram
Telegram profile photo for 𓂀 Последний 𝒮tar °༒︎

Channel

𓂀 Последний 𝒮tar °༒︎

@estellawin

On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Cite this entry

129subscribers

-1 since we began measuring on 14 September 2026

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

Register entry

Telegram ID-1003696778534
TypeChannel
Username@estellawin
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live15 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/estellawin

Growth

129130129.514 Sept 2026, 18:47 — 130 subscribers14 Sept 2026, 19:22 — 130 subscribers15 Sept 2026, 20:19 — 129 subscribers14 Sept 2026, 18:4715 Sept 2026, 20:19
3 measurements spanning 1 day, 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 129–130 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 20:19129-1
14 Sept 2026, 19:22130no change
14 Sept 2026, 18:47130first reading

Engagement

18 posts held, back to 11 September 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.5%
avg views ÷ 129 subscribers
Avg views / post
17.4
18 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
18
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 14 September 2026
Posts held18 (11 September 202614 September 2026)
Views total313
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Sept 2026, 19: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

Video runtime
46s
Average length
23s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

14 Sept 2026, 18:41 UTC8 viewsread 14 September 2026
Poll

𝒟oes this 𝒮rofile 𝒮icture fit the 𝒞hannel?

  1. 𝒩o0%

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

14 Sept 2026, 18:08 UTC9 viewsread 14 September 2026
Forwarded from @autheholic

🖤🪦Forward this message to your elegant channels. 👼👼 🤩akan tell you a drink based on ur vibe. 🤩urora tell you a brand based on ur vibe. Limit: You must join both chnls, n first 15 chnls.🔝

13 Sept 2026, 19:00 UTC16 viewsread 14 September 2026
Photo

Forward this message, and based on who you are, I’ll give you a song by whatsaheart + a short meme video. Private Please join Limit: idk

13 Sept 2026, 16:59 UTC15 viewsread 14 September 2026
Forwarded from @luvkissangel

این پیامو فور کنید یه ایراد و یه چیز خوب از چنلتون بگم جوین باشید بعد چلنج لفت بدید بن میشید

13 Sept 2026, 11:59 UTC16 viewsread 14 September 2026
Sticker

Sticker, posted without a caption

Signed 八岐大蛇 ✥ 𖤓

13 Sept 2026, 11:58 UTC17 viewsread 14 September 2026
Video

Video, posted without a caption

Signed 八岐大蛇 ✥ 𖤓

13 Sept 2026, 11:57 UTC15 viewsread 14 September 2026
File

File, posted without a caption

Signed 八岐大蛇 ✥ 𖤓

13 Sept 2026, 09:12 UTC16 viewsread 14 September 2026
Sticker

Sticker, posted without a caption

Signed ‌مریجین • Эстелла‌‌

13 Sept 2026, 09:12 UTC16 viewsread 14 September 2026
Photo

天叢雲剣 — 草薙剣 むかしむかし、出雲の国に、ヤマタノオロチという恐ろしい大蛇がいました。 その大蛇は八つの頭と八つの尾を持ち、毎年、一人の娘をさらっていました。 ある年、須佐之男命(すさのおのみこと)がその地を訪れました。 彼は最後に残された少女、櫛名田比売(くしなだひめ)を救うことを約束しました。 須佐之男命は酒を八つの桶に入れ、大蛇を待ちました。 やがて、山の向こうから――「ゴォォォ……」 大地を揺らすような音とともに、八つの頭を持つ大蛇が現れました。 大蛇は八つの酒を飲み干し、眠りにつきました。 その瞬間、須佐之男命は剣を抜きました。 「今こそ、終わりだ。」 彼は大蛇の尾を次々と斬り裂いていきました。 しかし、最後の尾を斬ったとき―― カキィィンッ! 剣が何か硬いものにぶつかりました。 尾の中から現れたのは、 雲のような輝きを放つ一本の神秘的な剣でした。 それが、 天叢雲剣(あめのむらくものつるぎ)。後に、この剣は

Signed ‌مریجین • Эстелла‌‌

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

14 Sept 2026, 18:41 UTCAnonymous Poll5 voters

𝒟oes this 𝒮rofile 𝒮icture fit the 𝒞hannel?

  1. 𝒩o0%

Shares as published, totalling 0%. 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 18 most recent posts we hold, published 11 September 2026 to 14 September 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.

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.

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

“𓂀 Последний 𝒮tar °༒︎” (@estellawin), 129 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/estellawin.

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.