Channel
@KirikAttik
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
56subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002536826004 |
|---|---|
| Type | Channel |
| Username | @KirikAttik |
| Description | Навигация: https://t.me/KirikAttik/8 Возрастной рейтинг [16/18+] |
| 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 |
| On Telegram | t.me/KirikAttik |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 07:46 | 56 | no change |
| 9 Aug 2026, 11:46 | 56 | first reading |
17 posts held, back to 14 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 8 August 2026 |
|---|---|
| Posts held | 17 (14 July 2026 – 8 August 2026) |
| Views total | 985 |
| Reactions total | 179 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 07:46 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.
Measured directly from 3 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.
189 reactions across 15 posts, in 46 distinct kinds. The most used accounts for 20.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 38 | 20.1% | |
| custom 5231145320418667557 | 14 | 7.41% | |
| custom 5467630171106338914 | 9 | 4.76% | |
| custom 5362004753360382609 | 8 | 4.23% | |
| custom 5262881392114543892 | 7 | 3.70% | |
| custom 5371101867755446871 | 7 | 3.70% | |
| custom 5242502850331841529 | 6 | 3.17% | |
| custom 5244732333495455096 | 6 | 3.17% | |
| custom 5262477699548457626 | 6 | 3.17% | |
| custom 5230940025276870039 | 5 | 2.65% | |
| custom 5436243400510702502 | 5 | 2.65% | |
| custom 6329942755262863026 | 5 | 2.65% | |
| custom 5282900144486916982 | 4 | 2.12% | |
| custom 5310061332983205289 | 4 | 2.12% | |
| custom 5312102984342081714 | 4 | 2.12% | |
| 💘 | 4 | 2.12% | |
| custom 5244833200802405147 | 3 | 1.59% | |
| custom 5253624251532986193 | 3 | 1.59% | |
| custom 5292062069938472671 | 3 | 1.59% | |
| custom 5307859818646624826 | 3 | 1.59% | |
| 26 further kinds | 45 | 23.8% |
Custom emoji. 18 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 15 of the 17 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 189reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 14 July 2026 to 8 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.
⭐️ >🧊апоздалая мстя Дроне 🥩🧊 Лизонька любимая 🐇 🥩🥩🧊🧊🧊🧊🧊🧊 #art@KirikAttik #oc(?) #ArtFight
❤4💘4custom 53259416309627933243custom 54113706350142054443custom 61183395520640508783custom 54676301711063389141
⏱️ > Теперь точно мстя (12) на 🤩🤩Артфайт 🤩🩸 🤩 🤩🤩🤩💔 😁 #art@KirikAttik #oc(?) #ArtFight
custom 53121029843420817144custom 52425028503318415292custom 52426449707996689152custom 52579753497565943451custom 54676301711063389141
🫐 > Атака (11) на Артфайт 🫐🥩🫐🫐🫐🫐🎁🥩🤩 #art@KirikAttik #oc(?) #ArtFight
❤7custom 52425028503318415294custom 54000671400845803773custom 53144405675375602992custom 54676301711063389141
🌌 > Десятая атака на Артфайт 🌟 ⁉️ 🌟 😁😏 🌟💣 #art@KirikAttik #oc(?) #ArtFight
custom 53711018677554468717custom 53620047533603826093custom 53866117376906719453custom 53867141941355202092custom 54676301711063389141
🌟 > Девятая атака на Артфайт ✉️🥩🌟 🌟 🎵🥩 🌟 ⚔️⚔️⚔️⚔️⚔️⚔️⚔️⚔️ #art@KirikAttik #oc(?) #ArtFight
❤5custom 52829001444869169824custom 53775951195726411463custom 53620047533603826092custom 52335674371604642641custom 52491008091567171241custom 54676301711063389141
✨ > Восьмая атака на Артфайт 🥩⭐️⚔️🥩🌟🌟🌟🥩✨ #art@KirikAttik #oc(?) #ArtFight
❤5custom 54676301711063389144custom 52448332008024051473custom 52920620699384726712custom 52311453204186675571
🌷 > Атака на Артфайт uwaaa 🤩🤩🤩🤩✨🤩🤩🤩 🤩🤩🤩🤩🤩🌼🤩🤩 #art@KirikAttik #oc(?) #ArtFight
custom 52311453204186675576custom 63299427552628630265❤2custom 53620047533603826092🍓1🔥1custom 53686861891696444111custom 54700249289064702441
🔥🔥🔥🔥🔥🔥🔥🔥 ❌SCREECHER PURSUER 🔥🔥🔥🔥🔥🔥🔥🔥 📱 Twitter
custom 54362434005107025025custom 52311453204186675573custom 54339884610759215262🍓1
Ответка для @spacecrow63 + @KirikAttik! ↫oame↬
custom 52447323334954550964custom 52628813921145438921custom 53078598186466248261custom 53210119448098535121
Я В СЛЕЗАХ СЧАСТЬЯ МЕСТИ БЫТЬ
❤3custom 52311453204186675571
🎫 > Карусельный тренд с моими 🥩 крутыми крутанами🌟♾ 🎪 🤩🤩🤩🥩🤩🤩 🌟 🌟 ⭐ 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 #art@KirikAttik featured #oc by: Балтика, Виша, #fandom_TheFreakCircus
custom 52628813921145438926❤4custom 52311453204186675573custom 52447323334954550962custom 53078598186466248262🍓1
🕊 > Шестая атака на Артфайт ✉️⭐️ 😁😏🌟 😜🌟🌟 #art@KirikAttik #oc(?) #ArtFight
custom 52624776995484576266custom 52335238733071795541custom 52920620699384726711custom 52942869446021773001
Showing the 12 most recent of 17 posts we hold for @KirikAttik. 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 — 367,449 of 1,480,944entries 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.
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.
“Киркин чердач 🎲” (@KirikAttik), 56 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/KirikAttik.
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.