Channel
@cche3se
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
147subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002662797523 |
|---|---|
| Type | Channel |
| Username | @cche3se |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/cche3se |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 16:53 | 147 | no change |
| 10 Aug 2026, 10:31 | 147 | first reading |
20 posts held, back to 27 December 2025 — 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.
| Window | Rolling 30 days · latest post in window 31 July 2026 |
|---|---|
| Posts held | 20 (27 December 2025 – 31 July 2026) |
| Views total | 1,107 |
| Reactions total | 273 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 10:31 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 15 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.
1,145 reactions across 20 posts, in 20 distinct kinds. The most used accounts for 17.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5303175478205498353 | 198 | 17.3% | |
| custom 5395574819041340145 | 170 | 14.8% | |
| custom 5303509321718448407 | 139 | 12.1% | |
| custom 5395737039956107988 | 90 | 7.86% | |
| custom 5458923722641539503 | 90 | 7.86% | |
| custom 5346110969183506654 | 80 | 6.99% | |
| 🆒 | 60 | 5.24% | |
| custom 5287771908710869266 | 59 | 5.15% | |
| custom 5325877949482689753 | 56 | 4.89% | |
| custom 5328175842885397886 | 36 | 3.14% | |
| custom 5395522691023267511 | 33 | 2.88% | |
| custom 5310018035417906039 | 32 | 2.79% | |
| 🐳 | 32 | 2.79% | |
| custom 5275973908426697839 | 18 | 1.57% | |
| 👻 | 14 | 1.22% | |
| custom 5453993967769124590 | 11 | 0.961% | |
| 👾 | 11 | 0.961% | |
| 🌚 | 9 | 0.786% | |
| 👀 | 5 | 0.437% | |
| custom 5409030822730692575 | 2 | 0.175% |
Custom emoji. 14 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 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 20 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 1,145reactions 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 27 December 2025 to 31 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @cche3se. 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 20 most recent posts we hold for this entry, published 27 December 2025 to 31 July 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.
time remap practice #edit #persona #1003grp
custom 530350932171844840721custom 528777190871086926616custom 530317547820549835316custom 53461109691835066545🌚2👀2🆒2custom 53100180354179060392
ib kyuvaki mattxs21 lvca.ae delirium.aepp #edit #genshin #1003grp
🆒31custom 531001803541790603930custom 534611096918350665429👻5🌚3custom 53031754782054983533custom 53035093217184484073👀2
тору адачи эдит смотреть онлайн без смс и регистрации ib delirium.aepp kyuvaki akir5n art cr : Ilikejagabata , Yu_asu5210 , highugkomori2 , rhxorb on twt(X) #edit #persona #1003grp
custom 530350932171844840731custom 530317547820549835328🆒23👾3custom 52877719087108692663custom 53461109691835066543🌚2custom 52759739084266978391
ib dollauxs meowdenjii outro: wppshrr #edit #aespa #1003grp
custom 539552269102326751126custom 528777190871086926620custom 530317547820549835320custom 53035093217184484078custom 54539939677691245902🌚1custom 52759739084266978391custom 53461109691835066541
с днём варенья изури 🍀 art cr : 6145797760 on rednote #edit #pjsk
custom 530317547820549835320custom 528777190871086926616custom 534611096918350665416custom 52759739084266978396custom 53035093217184484074custom 53955226910232675114custom 54539939677691245904🌚1
🌟 ib delirium.aepp kyuvaki qwennsi #edit #persona
custom 534611096918350665426custom 530317547820549835324custom 530350932171844840723custom 52759739084266978399custom 52877719087108692663custom 53955226910232675112
с днём рождения, лия !! 🤩 #edit #pjsk
custom 532817584288539788616🐳14custom 532587794948268975314custom 53031754782054983537custom 53035093217184484074
фу скрап #edit #jjk
custom 539557481904134014518custom 539573703995610798815custom 545892372264153950312custom 53258779494826897534custom 53031754782054983533custom 53035093217184484072🐳1
всех с первым днём лета, удачи на огэ егэ сессии и других экзаменах ❤️ а ещё этому каналу сегодня год исполняется ого
custom 539573703995610798811
это видео должно было выйти вчера, но я чуутка не успела, поэтому uh happy late birthday toya бтв оцените анимки, я их почти год не делала, о боже
custom 53955748190413401453custom 54589237226415395033
о господи privet ib ni6lou qwennsi #edit #pjsk
custom 530350932171844840725custom 539557481904134014523custom 545892372264153950319custom 53031754782054983537custom 53281758428853978864custom 53258779494826897533custom 53957370399561079882
hbd ` ๑ #edit #pjsk
custom 530317547820549835320custom 545892372264153950318custom 539557481904134014515custom 53035093217184484075custom 53258779494826897534custom 53281758428853978864custom 54539939677691245904👾2
Showing the 12 most recent of 20 posts we hold for @cche3se. 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 — 629,645 of 1,336,469entries 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 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.
@cche3se named 1 handle 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“ㅤcheese.mp4” (@cche3se), 147 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/cche3se.
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.