Telegram RegisterThe public register of Telegram
Telegram profile photo for your kamisama 🦋

Channel

your kamisama 🦋

@kavavii

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

8,700subscribers

-275 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001597515869
TypeChannel
Username@kavavii
CreatedBetween 1 September 2021 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/kavavii

Growth

8,7008,9758,837.57 August 2026 — 8,975 subscribers7 August 2026 — 8,975 subscribers7 August 2026 — 8,974 subscribers10 August 2026 — 8,954 subscribers13 August 2026 — 8,934 subscribers16 August 2026 — 8,893 subscribers20 August 2026 — 8,863 subscribers23 August 2026 — 8,846 subscribers26 August 2026 — 8,819 subscribers28 August 2026 — 8,799 subscribers31 August 2026 — 8,797 subscribers3 September 2026 — 8,765 subscribers9 September 2026 — 8,700 subscribers7 August 20269 September 2026
13 measurements spanning 33 days, net -275. 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 8,659–9,016 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 07:388,700-65
3 Sept 2026, 20:578,765-32
31 Aug 2026, 20:458,797-2
28 Aug 2026, 17:238,799-20
26 Aug 2026, 00:498,819-27
23 Aug 2026, 00:468,846-17
20 Aug 2026, 00:458,863-30
16 Aug 2026, 21:498,893-41
13 Aug 2026, 18:188,934-20
10 Aug 2026, 15:418,954-20
7 Aug 2026, 18:138,974-1
7 Aug 2026, 15:458,975no change
7 Aug 2026, 15:378,975first reading

Engagement

122 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 29 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.9%
avg views ÷ 8,700 subscribers
Avg views / post
1,730
83 posts measured
Reaction rate
6.02%
reactions ÷ views · ER floor
Posts in window
84
of 122 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held122 (1 August 202628 August 2026)
Views total143,921
Reactions total8,657
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 16:12 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.

What this channel posts

Video runtime
30s
Average length
8s

Measured directly from 4 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.

Reaction mix

13,788 reactions across 121 posts, in 28 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5,09737.0%
💘3,19223.2%
❤‍🔥2,98821.7%
🍓1,1308.20%
🥰3372.44%
👾2852.07%
💅1641.19%
😭1561.13%
🤩1180.856%
🔥740.537%
390.283%
🤯340.247%
👍290.21%
👻270.196%
💔260.189%
👀240.174%
🤡200.145%
🤪100.073%
🕊80.058%
🤬70.051%
8 further kinds230.167%

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 121 of the 122 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 13,788 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 122 most recent posts we hold, published 1 August 2026 to 28 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.

Telegram Stars

Stars received
8
across the posts below
Posts paid on
5
of 121 we hold a reading for · 4%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kavavii. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 122 most recent posts we hold for this entry, published 1 August 2026 to 28 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

28 Aug 2026, 14:24 UTC687 views121 reactionsread 28 August 2026
Photo

сегодня была вторая треня хутти фрутти и собрали примерные образы

❤‍🔥7822💘12🍓3🔥3🤔3

Signed kami

28 Aug 2026, 13:22 UTC901 views53 reactions2 Starsread 28 August 2026

Ками а икигай сейчас готовят какой-то проект? нет, сейчас почти все в отъезде в своих родных городах остальные работают или готовятся к поступлению

💘378❤‍🔥4🍓3🥰1

Signed kami

28 Aug 2026, 13:16 UTC850 views63 reactions1 Starread 28 August 2026

да и в целом если честно я не прям сильно дотошная в этом плане, иногда бывает и вправду переделываю движения более удобно или красиво не вижу в этом ничего плохого🤷🏻‍♀️

💘34❤‍🔥9🍓97🤩2🥰2

Signed kami

28 Aug 2026, 13:16 UTC888 views46 reactionsread 28 August 2026

насколько я знаю у меня только про шаги в какой то из хоряг скз был хейт, остальное из последних кб я разобрала правильно

34❤‍🔥5💘4🍓1💅1🥰1

Signed kami

28 Aug 2026, 13:15 UTC941 views57 reactionsread 28 August 2026

многие движения в кпоп выглядят по разному у разных танцоров, это связанно с разной базой и элементарно иногда даже телосложением пока не видела прям сильно отличающихся движений у меня от оригинала, но если такое есть можете всегда написать свои замечания

❤‍🔥399💘5🍓2💅1🥰1

Signed kami

28 Aug 2026, 13:14 UTC927 views29 reactions3 Starsread 28 August 2026

🩷 У тебя новое сообщение! Как вы разбираете танцы перед преподаванием на занятиях по кпопу? Часто бывает что очень неправильно преподаете, вам не так это важно? ↩️ Свайпни для ответа.

❤‍🔥233🍓1👍1💘1

Signed kami

27 Aug 2026, 19:03 UTC≈1,550 views123 reactionsread 28 August 2026
Photo

я в шоке с привоза на beyond 😭🙏🏻

💅7126💘18❤‍🔥4🍓2🤩2

Signed kami

27 Aug 2026, 11:39 UTC≈1,720 views120 reactionsread 28 August 2026

если бы девочки были против, мы бы поменяли , но опять же нам вообще не принципиально там у всех партии крутые как и сама хоряга вся

80❤‍🔥18💘14🍓8

Signed kami

27 Aug 2026, 11:38 UTC≈1,630 views109 reactionsread 28 August 2026

Просто хочешь быть в центие внимания👍 есссс👅👅👅👅

💘79❤‍🔥159🍓6

Signed kami

27 Aug 2026, 11:37 UTC≈1,550 views91 reactionsread 28 August 2026

фух ну вроде всех расписала а так, опять же, партии я распределила за секунд 5 на трене просто по ощущениям но опыта у меня очень много что бы сразу на взгляд определить как картинка будет выглядеть лучше и выгоднее для всех участников

❤‍🔥6313🍓7💘7👍1

Signed kami

27 Aug 2026, 11:36 UTC≈1,620 views111 reactionsread 28 August 2026

думаю будет легче если думать именно так но если вам интересно, то объясню со своей стороны: мы вообще не придаем большого значения распределению партий , поэтому и тут партии распределили максимально просто я больше смотрела на технику и исполнение девочек и + подбирала под стиль который они преподают (так ккк проект хореографов) софа сразу первая сказала что хочет встать за юнче, поэтому ее мы сразу поставили, а

❤‍🔥72🍓16💘158

Signed kami

27 Aug 2026, 11:33 UTC≈1,530 views92 reactionsread 28 August 2026

💘 У тебя новое сообщение! Ками,почему ты опять стоишь за Даниэлу в нрвом проекте. Ты всегда за нее. Это потому что у нее обычно прикольные партии? Что за синдром главного героя,боже ↩️ Свайпни для ответа.

😭52🤡205👍4🫡4❤‍🔥3💘2🍓1

Signed kami

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

Mentions

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.

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

“your kamisama 🦋” (@kavavii), 8,700 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/kavavii.

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.