а че она не горит
custom 52268025415467417656custom 52289142008725254654
Signed ㅤ𝒹estroy 𝓂e

Channel
@komakimeow
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
56subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004454174966 |
|---|---|
| Type | Channel |
| Username | @komakimeow |
| Created | Between 1 June 2026 and 5 July 2026— 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 |
| On Telegram | t.me/komakimeow |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 07:45 | 56 | no change |
| 8 Aug 2026, 20:02 | 56 | first reading |
19 posts held, back to 5 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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 19 (5 July 2026 – 9 August 2026) |
| Views total | 1,338 |
| Reactions total | 229 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 07:45 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 10 August 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.
269 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 50.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5228914200872525465 | 135 | 50.2% | |
| custom 5226802541546741765 | 134 | 49.8% |
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 19 of the 19 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 269reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 5 July 2026 to 9 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.
а че она не горит
custom 52268025415467417656custom 52289142008725254654
Signed ㅤ𝒹estroy 𝓂e
я щас закрою свою арт деятельность
custom 52268025415467417654
Signed ㅤ𝒹estroy 𝓂e
смешная нарезка детей
custom 522891420087252546511custom 52268025415467417658
Signed ㅤ𝒹estroy 𝓂e
обосраться перед любимым художником своим дерьмоскиллом ✅ сделано
custom 52268025415467417656custom 52289142008725254651
Signed ㅤ𝒹estroy 𝓂e
лесбиянки потом будут
custom 522891420087252546511custom 52268025415467417655
Signed ㅤ𝒹estroy 𝓂e
эта я и мой кентик брошечка forever
custom 522891420087252546512custom 52268025415467417653
Signed ㅤ𝒹estroy 𝓂e
моя очень старенькая ос, люблю ее всем сердцем, а с редизайном так ваще пушка
custom 522680254154674176511custom 52289142008725254655
Signed ㅤ𝒹estroy 𝓂e
давно хотел нарисовать кого то из бандори
custom 522680254154674176513custom 52289142008725254657
Signed ㅤ𝒹estroy 𝓂e
арт будет.. не отписывайтесь..
custom 52289142008725254655
Signed ㅤ𝒹estroy 𝓂e
челеки которые были в моем прошлом щп простите... короче я создаю новый но там я буду ведать о своих планах по поводу развития моих персонажей и какие проектики в будущем планирую. спойлеры к артам и текстам песен тоже будут кому интересен я как личность сюда
custom 52289142008725254658
Signed ㅤ𝒹estroy 𝓂e
ойййй друзья я так счастлив что добавили сообщество или че это за херь теперь когда я захочу создать канал по своим персонажам в очередной раз или может быть новеллуу с ними.... будет удобнее короче сори за щп мне надо было поделиться радостью
custom 52289142008725254654custom 52268025415467417652
Signed ㅤ𝒹estroy 𝓂e
снова стих в этот раз про моих пидорасов артем хыхы🤍🤍я старался оцените цветок раскрылся в тишине, как будто ждал меня давно. "мой свет... мой смысл... иди ко мне..." шептал так ласково, темно. лепестки касались пальцев, словно помнили тепло. в них я видел то, что раньше безвозвратно унесло. "разве боль тебя покинет? разве сможешь все забыть? я один храню то имя, что ты боишься повторить." каждый вдох давался болью,…
custom 52268025415467417658custom 52289142008725254654
Signed ㅤ𝒹estroy 𝓂e
Showing the 12 most recent of 19 posts we hold for @komakimeow. 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 — 250,526 of 1,350,102entries 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“владек—чян” (@komakimeow), 56 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/komakimeow.
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.