Video message, posted without a caption
custom 52627340747363104605custom 52875879509666334245custom 53616212986801753984custom 52222174835696160901

Channel
@karicka000
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Handles named that no longer answer · Cite this entry
317subscribers
+15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002938816812 |
|---|---|
| Type | Channel |
| Username | @karicka000 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/karicka000 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 22:03 | 317 | +10 |
| 24 Aug 2026, 03:46 | 307 | +5 |
| 8 Aug 2026, 08:01 | 302 | no change |
| 7 Aug 2026, 16:54 | 302 | first reading |
20 posts held, back to 4 January 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 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 20 posts for this entry, the most recent from 28 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.
1,854 reactions across 20 posts, in 34 distinct kinds. The most used accounts for 16.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5379958678730328817 | 301 | 16.2% | |
| custom 5361621298680175398 | 291 | 15.7% | |
| custom 5287587950966633424 | 259 | 14.0% | |
| custom 5398094792318016386 | 150 | 8.09% | |
| custom 5368782237523270996 | 146 | 7.87% | |
| custom 5465259379223717133 | 88 | 4.75% | |
| custom 5257975113533368914 | 69 | 3.72% | |
| custom 5467477287450471538 | 58 | 3.13% | |
| custom 5262734074736310460 | 55 | 2.97% | |
| custom 5280576940841921315 | 48 | 2.59% | |
| custom 5222217483569616090 | 46 | 2.48% | |
| custom 5260596864650063552 | 44 | 2.37% | |
| custom 5278397017305936161 | 44 | 2.37% | |
| custom 5431758874833079432 | 42 | 2.27% | |
| custom 5467468809185030214 | 39 | 2.10% | |
| custom 5316890348163722564 | 36 | 1.94% | |
| custom 5316594824348982424 | 25 | 1.35% | |
| custom 5298911335889783077 | 11 | 0.593% | |
| custom 5247101716628798313 | 10 | 0.539% | |
| custom 5262876092124912289 | 10 | 0.539% | |
| 14 further kinds | 82 | 4.42% |
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 20 of the 20 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,854reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 January 2026 to 28 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @karicka000. 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 20 most recent posts we hold for this entry, published 4 January 2026 to 28 July 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.
Video message, posted without a caption
custom 52627340747363104605custom 52875879509666334245custom 53616212986801753984custom 52222174835696160901
Video message, posted without a caption
custom 527839701730593616110custom 52875879509666334246custom 52627340747363104604custom 53616212986801753982
Video message, posted without a caption
custom 52783970173059361617custom 52875879509666334245custom 53616212986801753983custom 52627340747363104602
Video message, posted without a caption
custom 528758795096663342426custom 527839701730593616116custom 536162129868017539815custom 52627340747363104606custom 52222174835696160902custom 54291787247696367002custom 53165948243489824241custom 53799586787303288171
Video, posted without a caption
custom 536162129868017539822custom 522221748356961609015custom 536878223752327099612custom 52627340747363104605custom 52805769408419213154custom 52783970173059361612custom 52989113358897830772custom 53165948243489824241
Sticker, posted without a caption
custom 526273407473631046013custom 53616212986801753987custom 53799586787303288176
File, posted without a caption
custom 528758795096663342411custom 53687822375232709968custom 53799586787303288178
Video, posted without a caption
custom 537995867873032881715custom 528758795096663342410custom 53165948243489824248custom 52805769408419213155custom 52627340747363104604custom 52783970173059361613custom 52989113358897830772custom 53168903481637225642
Video message, posted without a caption
custom 536878223752327099618custom 531689034816372256410custom 52875879509666334248custom 52989113358897830774custom 52627340747363104603custom 52805769408419213152custom 53165948243489824241custom 53799586787303288171
Video message, posted without a caption
custom 522221748356961609021custom 531659482434898242413custom 537995867873032881711custom 53168903481637225643custom 53616212986801753983custom 52989113358897830772custom 52627340747363104601custom 52783970173059361611
буся
custom 528758795096663342449custom 537995867873032881725custom 536162129868017539822custom 54291787247696367006custom 52222174835696160902custom 52783970173059361612custom 52805769408419213152custom 53168903481637225642
🌹🌹
custom 528758795096663342430custom 531689034816372256415custom 536162129868017539815custom 53799586787303288174custom 52222174835696160903custom 53687822375232709963custom 52605968646500635521
Showing the 12 most recent of 20 posts we hold for @karicka000. 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.
@karicka000 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“кариша” (@karicka000), 317 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/karicka000.
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.