Telegram RegisterThe public register of Telegram

Channel

KATVIX

@KATVIX_26

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

23subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003886304031
TypeChannel
Username@KATVIX_26
DescriptionПо вопросам коллабов, пиара и другого в Директ Директ - t.me/KATVIX_26?direct Буст - https://t.me/boost/KATVIX_26
CreatedBetween 1 February 2026 and 19 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/KATVIX_26

Growth

2311 Aug 2026, 18:17 — 23 subscribers11 Aug 2026, 18:30 — 23 subscribers11 Aug 2026, 18:1711 Aug 2026, 18:30
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 22–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 18:3023no change
11 Aug 2026, 18:1723first reading

Engagement

19 posts held, back to 19 February 2026the 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.

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 3 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
31
Links
5

Lifetime counters from Telegram’s own channel header, read 11 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.

Reaction mix

180 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 18.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52380810011119532473418.9%
custom 52065401270897510903217.8%
custom 52377126861914837813016.7%
custom 52382365004029039732916.1%
custom 52381202614080053652111.7%
custom 5238176121752656881116.11%
custom 523799390347015798284.44%
custom 523787349406201431573.89%
custom 523588912897695393052.78%
custom 523802572058788664121.11%
custom 523817275020332943610.556%

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 18 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 180reactions 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 19 February 2026 to 3 April 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.

Recent posts

3 Apr 2026, 05:03 UTC74 views12 reactionsread 11 August 2026
Photo

Пока хайп Цирка не ушёл, вот вам Джекс Нужно будет ещё Помни нормально перерисовать, но это другая история

custom 52382365004029039737custom 52377126861914837813custom 52065401270897510902

1 Apr 2026, 07:03 UTC74 views11 reactionsread 11 August 2026
Photo

Увидела фотку челика в этом костюме, когда он был маленьким. Черт, не нарисовать это - самое настоящее злодейство

custom 52382365004029039736custom 52065401270897510904custom 52377126861914837811

31 Mar 2026, 21:06 UTC63 views5 reactionsread 11 August 2026

Кстати, всех с 1 апреля

custom 52358891289769539305

31 Mar 2026, 21:06 UTC63 views0 reactionsread 11 August 2026

Люди, мне сказали, что тг полностью блочат буквально 7 минут назад. Знаете, у меня стоит прокси, так что я изменений не чувствую особо, но как там у вас? Как-то ощущается?

29 Mar 2026, 13:37 UTC68 views7 reactionsread 11 August 2026

Кстати, Наконец-то нарисовала пиар пост в своём стиле. Теперь он хоть адекватно выглядит

custom 52377126861914837815custom 52065401270897510901custom 52382365004029039731

29 Mar 2026, 13:35 UTC66 views12 reactionsread 11 August 2026
Photo

Кажется я нашла свой вайб) По арту: Этого перса я нарисовала ещё год назад(см. Референс на скрине) и смотря на то, что получилось у меня сейчас.. Ну, я определённо вижу прогресс

custom 52065401270897510907custom 52377126861914837812custom 52378734940620143152custom 52381761217526568811

27 Mar 2026, 16:22 UTC58 views8 reactionsread 11 August 2026
Photo

Ну что, ребят, как вам 8 серия УЦЦ🙃? Все только-только в себя пришли после этого, теперь можно и обсудить

custom 52381761217526568814custom 52378734940620143153custom 52379939034701579821

24 Mar 2026, 23:30 UTC59 views9 reactionsread 11 August 2026
Photo

🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠

custom 52382365004029039734custom 52377126861914837813custom 52379939034701579822

24 Mar 2026, 12:44 UTC50 views11 reactionsread 11 August 2026
Photo

Недавно была на стриме у BVS, и вдохновилась❤️

custom 52382365004029039736custom 52379939034701579823custom 52065401270897510902

19 Mar 2026, 02:32 UTC66 views9 reactionsread 11 August 2026
Photo

Мне нравится то, как я обработала одежду, но мне кажется, что причёска должна была быть другой..

custom 52377126861914837817custom 52065401270897510901custom 52382365004029039731

14 Mar 2026, 13:29 UTC68 views13 reactionsread 11 August 2026
Photo

Фуух, закончила🥹 Нарисовала на одном дыхании ночью. Я думаю, что начинаю находить себя в этом стиле. Конечно, много чего стоит доработать, но мне это нравится✊ Как вам результат? 😍- красиво ☕️- норм/средне 😭- плохо

custom 52381761217526568816custom 52377126861914837815custom 52378734940620143152

13 Mar 2026, 23:24 UTC54 views11 reactionsread 11 August 2026
Photo

Достаем тяжёлую артиллерию

custom 52065401270897510907custom 52377126861914837812custom 52382365004029039732

Showing the 12 most recent of 19 posts we hold for @KATVIX_26. 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

Citation-graph rank — 1,118,077 of 1,169,250entries 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.

Mentions

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.

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.

Cite this entry

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“KATVIX” (@KATVIX_26), 23 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/KATVIX_26.

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.