Channel
@kotova_and_cat
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
130subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002418477350 |
|---|---|
| Type | Channel |
| Username | @kotova_and_cat |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 13 September 2026 |
| On Telegram | t.me/kotova_and_cat |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 15:26 | 130 | -1 |
| 21 Aug 2026, 18:57 | 131 | -1 |
| 15 Aug 2026, 07:23 | 132 | -1 |
| 9 Aug 2026, 00:17 | 133 | no change |
| 7 Aug 2026, 17:54 | 133 | first reading |
5 posts held, back to 4 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 5 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
116 reactions across 5 posts, in 13 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 37 | 31.9% | |
| 🔥 | 11 | 9.48% | |
| 🤣 | 10 | 8.62% | |
| custom 5278250374237542691 | 9 | 7.76% | |
| custom 5447432232698389583 | 9 | 7.76% | |
| custom 5278512874048738913 | 8 | 6.90% | |
| custom 5319208427912711629 | 8 | 6.90% | |
| 👍 | 8 | 6.90% | |
| custom 5287295223175604777 | 7 | 6.03% | |
| custom 5287256147563140310 | 3 | 2.59% | |
| 🎉 | 3 | 2.59% | |
| 🍓 | 2 | 1.72% | |
| custom 5278681790817522448 | 1 | 0.862% |
Custom emoji. 7 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 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 5 of the 5 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 4 June 2026 to 3 July 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.
Иногда пройтись пешком - лучшее решение 👍 По пути от фонопеда до стоматолога забрела в Воскресенский Новодевичий монастырь. Здесь нереальной красоты храм, ухоженная территория, вкусная трапезная! А ещё старинное кладбище, где захоронено много известных людей. Будете в районе Московских ворот - обязательно загляните сюда.
❤9👍8
День Молодёжи в двух шагах от моего дома) Было классно! И даже видеопривет Газану записали 😉
custom 53192084279127116297🎉3
Сегодня училась снимать липсинги. Правда у меня получается не совсем lip, и не совсем sing 🤣, а вот девочки справились отлично! https://www.tiktok.com/t/ZTB3w8GYg/
❤13🤣10custom 52872561475631403103custom 52785128740487389131custom 52786817908175224481custom 53192084279127116291
Photo, posted without a caption
❤15custom 54474322326983895839custom 52785128740487389137🍓1
Я думала, что этот чудный день уже не сделать лучше… но я ошибалась 😉
🔥11custom 52782503742375426919custom 52872952231756047777🍓1
Showing the 5 most recent of 5 posts we hold for @kotova_and_cat. 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Котова 👠 и Кот 🐾” (@kotova_and_cat), 130 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/kotova_and_cat.
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.