Channel
@krrevetko_hoi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
43subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002973768102 |
|---|---|
| Type | Channel |
| Username | @krrevetko_hoi |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 12 September 2026 |
| On Telegram | t.me/krrevetko_hoi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 10:14 | 43 | -1 |
| 18 Aug 2026, 22:24 | 44 | +1 |
| 12 Aug 2026, 02:42 | 43 | no change |
| 11 Aug 2026, 02:46 | 43 | first reading |
19 posts held, back to 5 June 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
314 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 36.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5256028995132098305 | 113 | 36.0% | |
| custom 5211192800736977450 | 72 | 22.9% | |
| custom 5391022621858996061 | 52 | 16.6% | |
| custom 5255929579524097188 | 21 | 6.69% | |
| custom 5197450820945221476 | 16 | 5.10% | |
| custom 5451895532647636648 | 13 | 4.14% | |
| custom 5255802680420370489 | 12 | 3.82% | |
| custom 5422491018308111110 | 9 | 2.87% | |
| custom 5393584681520209609 | 6 | 1.91% |
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 are Telegram’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 314 reactions 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 June 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.
🤍🔠🔠🔠🔠🤍 🍄 как упоминалось выше, вместе с обновлением дизайна коматоз также должен был получить новый окрас. но настоящая классика никогда не выходит из стиля!1! 🦐: такие вот были варианты..
custom 52111928007369774507custom 52559295795240971886
🪽🔠🔠🔠🔠🔠🔠🪽 🔠🔠🔠🔠 🔠🔠🔠🔠 🐾сахарный призовой артик для @rainy_carroTisha_13 выходит в свет, duh!1! такую вот мимимишность с послевкусием энергетика мы имеем::))
custom 52560289951320983058custom 52111928007369774506custom 53935846815202096091
🌟🌟🌟🌟🌟🌟🌟🌟 🗣 долгожданный арт для @Liro_StarWolf готов!1! stay tchuned, товарищи.
custom 525602899513209830510custom 52558026804203704894custom 54224910183081111103
🕺YOK YOK EVERYONE!1!🕺 😸поздравляю всех нас, мы фактически дожили до августа!1! вот щас как сяду и дорисую долги. ну и доброшу новых дизайнов по "долбокритикам". с любовью, ваш амбассадор кислотных дизайнов котов-инопланетян.
custom 525602899513209830510custom 53910226218589960617
аргончик традишка 🤓🤓🤓 #долбокритики афтар пирсанажа @krrevetko_hoi
custom 52111928007369774509custom 51974508209452214763custom 54518955326476366481
🦐: @Liro_StarWolf и @rainy_carroTisha_13, про ваши арты я не забыла!1! я всë ещë работаю над ними, fr qvq обещаю доделать всë до конца лета уж точно 😭
custom 539102262185899606112
⛓🔠🔠🔠⛓ 🐇 ну и, наконец, наша тонконогая принцесса жу! 🦐: создание этого образа было весьма утомляющим, поверьте мне на слово.. #dolbokritiki
custom 52560289951320983057custom 53935846815202096095custom 54518955326476366482custom 53910226218589960611
🟩🔠🔠🔠🔠🔠🔠🔠🟩 🍄 товарищи, встречайте: новый импровизированный дизайн коматоза!1! 🦐: палитра данного персонажа изменилась столько раз.. только для того, чтобы остаться прежней xd #dolbokritiki
custom 525602899513209830513custom 52559295795240971885
🔥🔠🔠🔠🔠🔠🔠🔥 🤩 а следующий на очереди у нас телеведущий хардкорщик! 🦐: зрачки мистера интеллигента увеличились раз в 20.. в природе такой взгляд бывает у кошек, готовых к бою! #dolbokritiki
custom 525602899513209830512custom 54224910183081111104custom 52559295795240971883
🖤🔠🔠🔠🔠🔠🖤 🦷 еженочный вброс новых экспериментальных дизайнов продолжается!1! 🦐: эйха не сильно изменился... разве что получил что-то типа витилиго и более серьëзную травму шеи в подарок xd #dolbokritiki
custom 52558026804203704898custom 52560289951320983055custom 54224910183081111102
⚠️🔠🔠🔠🔠🔠⚠️ 😸получите, распишитесь: свежий экспериментальный редизайн Аргона! 🦐: так то, ноги-протезы были идеей @holodoska, и идеей вполне логичной. Аргон, всë таки, является киборгом. #dolbokritiki
custom 521119280073697745012custom 52559295795240971886custom 53910226218589960611
🦐: вот вам пока скетчи, изображающие моих фурри товарищей! ^v^ уже возвращаюсь на рельсы, ëтить..
custom 539102262185899606110custom 52560289951320983057custom 52111928007369774504
Showing the 12 most recent of 19 posts we hold for @krrevetko_hoi. 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.
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 2 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.
@krrevetko_hoi 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“ᎷИᏢ ᏦᏒᏒᎬᏙᎬᎢᏦᏫ 🧠” (@krrevetko_hoi), 43 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/krrevetko_hoi.
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.