Telegram RegisterThe public register of Telegram

Channel

Котики и корона на голове Беллы Рапопорт

@kittendances

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cross-platform identity · Cite this entry

4,423subscribers

-9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001346645722
TypeChannel
Username@kittendances
Created26 February 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/kittendances

Previous handles

Recorded in 2019 as “Котики и танцы — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Growth

4,4234,4324,427.56 August 2026 — 4,432 subscribers6 August 2026 — 4,431 subscribers9 August 2026 — 4,428 subscribers12 August 2026 — 4,423 subscribers6 August 202612 August 2026
4 measurements spanning 7 days, net -9. 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 4,422–4,433 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:534,423-5
9 Aug 2026, 17:514,428-3
6 Aug 2026, 12:404,431-1
6 Aug 2026, 08:314,432first reading

Engagement

47 posts held, back to 4 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 6 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.9%
avg views ÷ 4,423 subscribers
Avg views / post
615
47 posts measured
Reaction rate
3.98%
reactions ÷ views · ER floor
Posts in window
47
of 47 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. It is computed over the 46 of 47 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held47 (4 August 20268 August 2026)
Views total28,884
Reactions total1,133
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18: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
22s
Average length
22s

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.

Reaction mix

824 reactions across 30 posts, in 15 distinct kinds. The most used accounts for 43.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁35843.4%
💯19924.2%
819.83%
👍323.88%
👎313.76%
custom 5224708023435404637263.16%
custom 5334869231588619276253.03%
🔥222.67%
😱141.70%
🕊131.58%
🎉91.09%
🤯60.728%
🗿40.485%
👏20.243%
🤔20.243%

Custom emoji. 2 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 46 of the 47 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 1,133reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 47 most recent posts we hold, published 4 August 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.

Recent posts

8 Aug 2026, 15:20 UTC227 views10 reactionsread 8 August 2026
Forwarded from @ilovevospbPhoto

"Ваня Коммунист" снова у набережной Лейтенанта Шмидта. Прислал Андрей @prokater КПРФ, такой шарой надо пользоваться)

9👎1

8 Aug 2026, 12:14 UTC360 views12 reactionsread 8 August 2026
Forwarded from @gus_vasiliPhoto

Ну в принципе и то, и другое про хлеб

😁12

8 Aug 2026, 08:15 UTC436 views20 reactionsread 8 August 2026
Forwarded from @chubbyartbodyPhoto

Иллюстрации художницы Селены Меко

🔥191

7 Aug 2026, 18:34 UTC613 views39 reactionsread 8 August 2026

Ну…

custom 522470802343540463726💯5😁5👎2🗿1

7 Aug 2026, 18:27 UTC618 views7 reactionsread 8 August 2026

Чтоб платили конечно хотелось бы…..

5👎2

7 Aug 2026, 18:27 UTC618 views7 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

😁5👎2

7 Aug 2026, 18:27 UTC616 views37 reactionsread 8 August 2026

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

😁23💯83👎2🤔1

7 Aug 2026, 18:24 UTC617 views39 reactionsread 8 August 2026

Это она конечно нашим дедам польстила))))

😁34💯3👎2

7 Aug 2026, 18:19 UTC615 views19 reactionsread 8 August 2026

Как красиво состарились комменты под этим постом и сам пост (это я себя в поиске вбила)

😁16👎2🗿1

7 Aug 2026, 18:19 UTC609 views46 reactionsread 8 August 2026

А надо на бибиси блять)))

😁42👎2💯1🗿1

7 Aug 2026, 18:11 UTC608 views7 reactionsread 8 August 2026

Целый детектив развернулся

4😁3

Showing the 12 most recent of 47 posts we hold for @kittendances. 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 — 222,899 of 1,151,006entries 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.

Forward network

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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q62398607 on Wikidata, read 9 August 2026
LabelBella Rapoport
Description(1980–)
X / Twitter@Belkitz

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

“Котики и корона на голове Беллы Рапопорт” (@kittendances), 4,423 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kittendances.

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.