Channel
@kkkimi_chi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
116subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001851642979 |
|---|---|
| Type | Channel |
| Username | @kkkimi_chi |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kkkimi_chi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 05:17 | 116 | no change |
| 6 Aug 2026, 18:48 | 116 | first reading |
13 posts held, back to 21 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 7 August 2026 |
|---|---|
| Posts held | 13 (21 July 2026 – 7 August 2026) |
| Views total | 1,402 |
| Reactions total | 229 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 05:17 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 9 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.
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.
229 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 30.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5042120292143465157 | 69 | 30.1% | |
| custom 5370744260188460632 | 59 | 25.8% | |
| custom 5251534689813956060 | 56 | 24.5% | |
| custom 5886230865029110301 | 18 | 7.86% | |
| custom 5316979941181496594 | 11 | 4.80% | |
| custom 5888827572191500918 | 11 | 4.80% | |
| custom 5249317460192010965 | 3 | 1.31% | |
| custom 5888810796049242458 | 2 | 0.873% |
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 13 of the 13 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 229reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 21 July 2026 to 7 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.
🔠🔠🔠🔠🔠🔠 💫🔠🔠🔠🔠 🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 🤩⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀🤩 ⠀⠀⠀⠀⠀⠀⠀⠀🔠Рудо⠀⠀⠀🤩 ⠀⠀⠀🤩⠀⠀⠀🔠Энжин ⠀⠀⠀⠀⠀⠀⠀⠀🔠Тамзи ⠀⠀⠀⠀⠀⠀⠀⠀🔠Джаббер⠀⠀⠀⠀⠀🤩 🤩⠀⠀⠀⠀⠀⠀🔠Амо ⠀⠀⠀⠀⠀⠀⠀⠀🔠Занка⠀⠀⠀⠀🤩 ⠀⠀⠀⠀🤩 🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠 Фотограф #косплей@kkkimi_chi #фестиваль@kkkimi_chi
custom 52515346898139560608custom 53707442601884606325custom 58888275721915009185custom 52493174601920109653
Well....🌌 #процесс@kkkimi_chi
custom 52515346898139560605custom 53707442601884606322custom 58888275721915009182
🤩Жесть, опять тикток 🤩🤩 На этом все, больше не буду🥺 https://www.tiktok.com/@kkimi__chi/video/7670138535126519060
custom 58862308650291103019custom 50421202921434651576custom 52515346898139560603custom 53707442601884606321
Я тут учусь тиктоками баловаться 😐 Не умею я там красивые нарезки делать, что-то трендовое и тд (да и ваще не люблю тиктоки снимать, я кринжую, да)🤩 Благо, тикток сам умеет нарезать видосик под музыку Так что держите видео с недавнего фотосетика в Занке 🤩
custom 50421202921434651578custom 53707442601884606324custom 52515346898139560602custom 58862308650291103012
Ой, а что это тут у нас?🥰 #процесс@kkkimi_chi ? #процесс@kkkimi_chi
custom 504212029214346515710custom 52515346898139560604custom 58888275721915009182custom 53707442601884606321
Вы были услышаны Добро пожаловать в мой ЩП 💅
custom 50421202921434651574custom 52515346898139560602custom 58862308650291103011
Интересно ли вам наблюдать за простой жизнью косплееров? Я про вот те самые "щит-посты", в которых ребята делятся чем-либо, оставляя "годный контент" в основном канале Я не люблю "засорять" этот канал всяким разным и периодически чищу канал от разных постов, оставляя вам только красивые, полезные или просто важные для меня посты Вот опять задумалась над созданием своего щп-канала ибо делиться то есть чем...😐
custom 53707442601884606329
Люблю собирать бумажки, фоточки, наклеечки, визиточки и прочую шушеру, что б потом клеить в альбом🩷 За все время попыток начать вести подобный альбом было несколько. Каждый раз я забрасывала по той причине что просто переставала ходить на фестивали (одной - скучно, а компанию в той же Казани было не найти, да и фестов в этой самой Казани особо и нет). Благодаря поездке в Питер собрался аж целый разворот🩷 1 страничка …
custom 53707442601884606328custom 52515346898139560605custom 50421202921434651572custom 58862308650291103012custom 58888107960492424581
Покажу немножко Беков, так уж и быть🩵🩵 🪐Над красотой вчера люто старались 2 фотографа: Персик и ее подопечный ✨За беки и моральную поддержку отвечали: Надзиратель барахла и Даня 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 У меня даже контент для тик тока есть... Жесть... Когда-нибудь я выложу, да...
custom 504212029214346515711custom 53707442601884606326custom 52515346898139560605custom 58862308650291103011custom 58888275721915009181
Эта банда отфоткала красоту💕 Можно снова пропадать из инфополя на неопределенное время 💕
custom 537074426018846063211custom 50421202921434651577custom 52515346898139560607custom 58862308650291103011
Video message, posted without a caption
custom 53707442601884606329custom 50421202921434651574custom 52515346898139560604
Оу щит... Хир ви гоу эгеин...🤩
custom 504212029214346515710custom 52515346898139560605custom 53707442601884606323custom 58862308650291103011
Showing the 12 most recent of 13 posts we hold for @kkkimi_chi. 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 — 148,873 of 1,345,403entries 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.
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 3 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“‧₊˚⋅ Кузница KkimiChi ‧₊˚⋅” (@kkkimi_chi), 116 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/kkkimi_chi.
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.