Channel
@CUPUsSolarEclipse
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
192subscribers
+4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001622045058 |
|---|---|
| Type | Channel |
| Username | @CUPUsSolarEclipse |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/CUPUsSolarEclipse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 16:31 | 192 | +4 |
| 8 Aug 2026, 12:04 | 188 | no change |
| 8 Aug 2026, 02:15 | 188 | first reading |
16 posts held, back to 22 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 1 pageof 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 14 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 16 (22 July 2026 – 6 August 2026) |
| Views total | 2,208 |
| Reactions total | 107 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:04 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.
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.
107 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 27.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5767131074018676637 | 29 | 27.1% | |
| custom 6010194414444483354 | 29 | 27.1% | |
| custom 5765160736296800390 | 21 | 19.6% | |
| custom 6021321948858945491 | 18 | 16.8% | |
| custom 5764659775606361542 | 7 | 6.54% | |
| custom 6010185790150153770 | 2 | 1.87% | |
| custom 6010475434154660323 | 1 | 0.935% |
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 14 of the 16 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 107reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 22 July 2026 to 6 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.
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ В последние дни в моей голове уселась "Raise up your bat", и я захотел зарисовать Базовое Трио ввиде троицы из дельты в теле-мире с ритм сигмента 🥾 Изворотился как мог с ними
custom 60213219488589454913custom 60101857901501537701custom 60101944144444833541
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Жёлтый цветуля на ночь глядя 🤩 Он мне ОЧЕНЬ полюбился. Тупой ковбой 🥾
custom 60213219488589454916custom 57646597756063615423
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Анонсирую своё присутствие на Андерсходке в косплее / закосе ( называйте как хотите ) на Фрола 🥾 С исполнением "Битвы против мира"..... 😱
custom 57671310740186766378custom 60101944144444833544custom 57646597756063615422
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Атака для.. Силли? С КАКИХ ПОР... Давно я эту черепушечку не рисовал. Да и обджектов в целом..... ⭐ Я в артфайте
custom 60101944144444833544custom 57646597756063615421custom 57651607362968003901
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Атака с Йолги ( Или Ëлги? ) для Джуно 🥾 Я неправильно нарисовал его бензопилу но надеюсь это не так критично ⭐ Я в артфайте
custom 60101944144444833545custom 57651607362968003903
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ РЕВЕНДЖ в сторону Мелоди 🦋 Бро нарисовала Славу так что я решил накидать её перса с ним лол. Чел реально сделал мне самую первую атаку ⭐ Я в артфайте
custom 60101944144444833547custom 57671310740186766371
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Всем привет, у меня рандомная ночная ебанца 😋 Гифкой в комменты скину
custom 57651607362968003905custom 57671310740186766374custom 60213219488589454913custom 60104754341546603231
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ По просьбе Рицу - Силеты 🥾 ⭐ Автор страшилы
custom 60101944144444833545custom 60213219488589454912
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Глупый уборщик на перерыве для ИдиотикРат'а 🥾 Он мне напоминает Уолли от одного художника в тамблере ⭐ Я в артфайте
custom 57651607362968003905custom 57671310740186766374custom 60101944144444833542
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Моей следующей жертвой была Аксоликс 🥾 Давно хотел сделать гифт этому челу, повод нашелся ⭐ Я в артфайте
custom 57671310740186766372custom 60101944144444833541
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
🔠🔠↙️🔠🔠⏸️Кожа в хуйню руки тоже и вообще МЯСО ✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Начну серию атак к артфайту с Шэмми 🥾 Я ОЧЕНЬ ЛЮБЛЮ СЕБА один из моих любимчиков среди персонажей Стеша 🦋 ⭐ Я в артфайте
custom 57651607362968003903custom 57671310740186766373custom 60213219488589454911
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
✬ ╞▒ ∫ 𝘊𝘜𝘗𝘜 𝘰𝘳 𝘏𝘈𝘓𝘛𝘌𝘙𝘐𝘟 ∫ ▒╡✬ Тц не забейте я потом отдельными постами постепенно буду выкладывать
Signed 🥾 𝘊𝘜𝘗𝘜 / 𝘏𝘢𝘭𝘵𝘦𝘳𝘪𝘹 | 𝘈𝘯𝘺 𝘗𝘳𝘯𝘴
Showing the 12 most recent of 16 posts we hold for @CUPUsSolarEclipse. 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.
Citation-graph rank — 154,617 of 1,160,990entries 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.
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 4 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“◑ CUPU HERE!! | СОЛНЕЧНОЕ ЗАТМЕНИЕ” (@CUPUsSolarEclipse), 192 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/CUPUsSolarEclipse.
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.