такие классные фоточкииии🥹
custom 532554289908391862314custom 53865912807614446867custom 52356096726348810424custom 52267643120428177531custom 53709617530373711141custom 53911956875662138911

Channel
@lkkr_k
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
179subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002354547969 |
|---|---|
| Type | Channel |
| Username | @lkkr_k |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/lkkr_k |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 04:14 | 179 | -8 |
| 24 Aug 2026, 06:54 | 187 | -1 |
| 15 Aug 2026, 14:47 | 188 | +2 |
| 8 Aug 2026, 12:16 | 186 | no change |
| 8 Aug 2026, 01:51 | 186 | +1 |
| 7 Aug 2026, 15:59 | 185 | first reading |
7 posts held, back to 29 July 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 7 posts for this entry, the most recent from 5 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.
131 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5325542899083918623 | 41 | 31.3% | |
| custom 5235609672634881042 | 26 | 19.8% | |
| custom 5370961753037371114 | 21 | 16.0% | |
| custom 5391195687566213891 | 14 | 10.7% | |
| custom 5343609159323505397 | 11 | 8.40% | |
| custom 5226764312042817753 | 10 | 7.63% | |
| custom 5386591280761444686 | 8 | 6.11% |
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 7 of the 7 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 131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 29 July 2026 to 5 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.
такие классные фоточкииии🥹
custom 532554289908391862314custom 53865912807614446867custom 52356096726348810424custom 52267643120428177531custom 53709617530373711141custom 53911956875662138911
🍒
custom 537096175303737111410custom 53911956875662138919custom 53255428990839186236
.’💖,🌈 3/26
custom 52356096726348810426custom 52267643120428177534custom 53911956875662138914custom 53865912807614446861
бармалдааааа
custom 53255428990839186236custom 52356096726348810424custom 52267643120428177533
🫂
custom 523560967263488104210custom 52267643120428177532custom 53436091593235053972
провести лето перед 11 классом в лагере в роли вожатой>>>
custom 532554289908391862311custom 52356096726348810422custom 53709617530373711142
вожатим вожатим
custom 53436091593235053979custom 53709617530373711148custom 53255428990839186234
Showing the 7 most recent of 7 posts we hold for @lkkr_k. 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“karpushova vlog” (@lkkr_k), 179 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/lkkr_k.
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.