Channel
@stellasolo
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
40subscribers
+9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003899277622 |
|---|---|
| Type | Channel |
| Username | @stellasolo |
| Description | Все вопросы сюда: @svyaze_miku_bot Во флуды/компании/шоу не вступаю Архив: @stellarhiv тт: @stellasollo |
| Created | Between 1 February 2026 and 28 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 4 |
| On Telegram | t.me/stellasolo |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 8 November 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
@stellasolo was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 07:22 | 40 | no change |
| 8 Nov 2026, 06:47 | 40 | +9 |
| 11 Aug 2026, 03:31 | 31 | no change |
| 7 Aug 2026, 19:14 | 31 | first reading |
38 posts held, back to 28 July 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 2 pages of Telegram’s post history, 20 posts per page.
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 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 38 (28 July 2026 – 7 November 2026) |
| Views total | 511 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 07: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.
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.
Measured directly from 1 video 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.
35 reactions across 7 posts, in 16 distinct kinds. The most used accounts for 11.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5201717407097313264 | 4 | 11.4% | |
| custom 5172640658892002083 | 3 | 8.57% | |
| custom 5199530392570318567 | 3 | 8.57% | |
| custom 5215169094344538986 | 3 | 8.57% | |
| custom 5215610144536159263 | 3 | 8.57% | |
| custom 5215619885521990996 | 3 | 8.57% | |
| custom 5244978473776211351 | 3 | 8.57% | |
| custom 5474126025673685883 | 3 | 8.57% | |
| custom 5390927453973677368 | 2 | 5.71% | |
| custom 5391034626292615280 | 2 | 5.71% | |
| custom 5264820608503401887 | 1 | 2.86% | |
| custom 5388959457008975425 | 1 | 2.86% | |
| custom 5391143933210297862 | 1 | 2.86% | |
| 💅 | 1 | 2.86% | |
| 💘 | 1 | 2.86% | |
| 🦄 | 1 | 2.86% |
Custom emoji. 13 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 7 of the 38 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 28 July 2026 to 7 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.
Telegram’s own ‘edited’ marker: 2 of 18 posts held from the last 30 days (11.1%) 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).
🎀🧊 𝖻︪︩ɑ𝖽 𑜑ֺ𑄋ωֺ᥍ 🗝ı๋𝗏𝗎ׁ𝘀ᧉ 🗝🗝 ხᦅᦅო , ხᦅᦅო , ხᦅᦅო I'ო 'ხᦅυƗ Ɨᦅ ех𝗉Ꙇᦅᑯе🤩 ➿*➿ .🎀🌙 @rivuseoi➿🤩 🩷 𝗿ִı๋𝗏𝗎ׁ𝘀ᧉ ~~ 𝗇ׄαrı𝗇ׄ 🩷 ™️ 📺 : @rivusecov 🤩 𑜑ֺ𑄋ωֺ᥍ : сегодня наша группа пришли к вам с плохими новостями . Нарин решила взять рест на неопределенный срок , по поводу личных причин .🔠 но из - за этого .. мы открываем набор на временную участницу. ➿*➿ .🎀🌙 @group➿🤩 How can I feel more than this? I don't know 🧁 𝗊𝗎𑄋᥍Ɨⲓ𑄝𑜑ֺ𑜑ֺɑ…
Репост
🎀EꙆαr𐑦s Aυᑯ𐑦t𐑦𑄝𐓣🎀 𝕐ᦅ𝗎 dᧉsᧉrvᧉ sᦅmᧉᦅ𝗇ׄᧉ t𝕙ׄαt lᦅvᧉs ɥׄᦅ𝗎 rıgׄ𝕙ׄt💎 ➿➿➿➿➿➿➿➿➿➿ 🎀Frᧉᧉ:𑄝t5🏍 🎀Bυsყ:Phαr𐑦tα.👄 I ϲ𑄝υꙆᑯ Ꙇ𑄝ѵᧉ ყ𑄝υ 't𐑦Ꙇ thᧉ ᧉ𐓣ᑯ 𑄝ẜ t𐑦𝗆ᧉ🎁 🪦01.ПрαвиꙆα и Aн𝕜ᧉтα в 𝕜ᦅмᧉнтαриях 🐈⬛ 🎀02.Bᦅт: @elaris1bot🎀 ➿➿➿➿➿➿➿➿➿➿ 🤩#ᧉƖ⍺ִꭈı𝗌#Ɨhᧉ𝖻ᧉ𝗌Ɨ#⍺ִ𝗎d᳢ıƗı𐐫n🎁
Так что скоро будет актив
Я планирую на свой др сделать нью эру🐠
Ну попробую
Video message, posted without a caption
Video message, posted without a caption
Sticker, posted without a caption
До вашего дня рождения осталось 10 дней
Voice message, posted without a caption
Как вам форточки?🤩
custom 52151690943445389863custom 52156198855219909963custom 51726406588920020831custom 52156101445361592631custom 52449784737762113511
Showing the 12 most recent of 38 posts we hold for @stellasolo. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@stellasolo named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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.
“𝗦ֺ𝘁ֺ𝝴ֵ𝗹𝗹𝝰ֺ 𝘀ׅ𝝾ֺ𝗹𝝾ֺ❄️” (@stellasolo), 40 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/stellasolo.
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.