Sticker, posted without a caption
❤68👻11🕊8

Channel
@stikery_emodzi_memy
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,263,332subscribers
-7,889 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001440674296 |
|---|---|
| Type | Channel |
| Username | @stikery_emodzi_memy |
| Description | Больше мемов тут: @evo_memy Реклама: @evoanna @evo_milena (сразу кидайте ник канала) Канал в реестре: https://clck.ru/3JfAGV Любые жалобы правообладателей сразу удаляем стикеры. |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/stikery_emodzi_memy |
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 74% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:26 | 1,263,332 | -1,712 |
| 10 Aug 2026, 20:04 | 1,265,044 | -1,142 |
| 9 Aug 2026, 23:34 | 1,266,186 | -1,269 |
| 8 Aug 2026, 23:21 | 1,267,455 | -1,047 |
| 8 Aug 2026, 01:26 | 1,268,502 | -1,478 |
| 7 Aug 2026, 03:58 | 1,269,980 | -1,154 |
| 6 Aug 2026, 05:31 | 1,271,134 | -87 |
| 6 Aug 2026, 01:30 | 1,271,221 | no change |
| 6 Aug 2026, 01:04 | 1,271,221 | first reading |
35 posts held, back to 31 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 18 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 35 (31 July 2026 – 12 August 2026) |
| Views total | 1,977,400 |
| Reactions total | 6,737 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00:25 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 20 of this channel’s own posts over the last 30 days: across 17of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 24 hours of being posted; a typical post has already reached 20.3% of its 24-hour view count within the first hour, and 48.9% within the first six; the median 24-hour reach across those posts is 27,300 views — 2.16% of this channel’s own subscriber count (90th percentile 30,060).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /273212 Aug 2026, 13:49 UTC | 193 minutes – 11 hours old | 15,200 views ~87 reactions | 60 minutes: 5,401 interp. → 3.0 hours: 8,870 → 6.0 hours: 12,800still climbing at last reading | not yet at 24h | 2.1 hoursprovisional — final view count still climbing |
| /273112 Aug 2026, 08:53 UTC | 2728 minutes – 16 hours old | 22,000 views ~122 reactions | 60 minutes: 5,500 → 3.0 hours: 9,364 interp. → 6.0 hours: 14,900 → 12 hours: 20,800still climbing at last reading | not yet at 24h | 4.3 hoursprovisional — final view count still climbing |
| /273011 Aug 2026, 16:43 UTC | 593 minutes – 32 hours old | 32,100 views ~234 reactions | 60 minutes: 6,728 interp. → 3.0 hours: 11,100 → 6.0 hours: 14,300 → 12 hours: 16,200 → 24 hours: 28,200still climbing at last reading | 28,200measured | 12 hours |
| /272911 Aug 2026, 08:21 UTC | 7415 minutes – 40 hours old | 37,100 views ~181 reactions | 60 minutes: 5,140 interp. → 3.0 hours: 9,020 → 6.0 hours: 12,700 → 12 hours: 21,900 → 24 hours: 26,700still climbing at last reading | 26,700measured | 9.5 hours |
| /272811 Aug 2026, 07:42 UTC | 7424 minutes – 41 hours old | 35,900 views ~216 reactions | 60 minutes: 6,109 interp. → 3.0 hours: 10,600 → 6.0 hours: 13,700 → 12 hours: 22,100 → 24 hours: 26,700still climbing at last reading | 26,700measured | 9.4 hours |
| /272710 Aug 2026, 19:53 UTC | 9053 minutes – 2 days old | 41,200 views ~191 reactions | 60 minutes: 6,502 interp. → 3.0 hours: 9,150 → 6.0 hours: 10,500 → 12 hours: 17,300 → 24 hours: 29,900 → 2 days: 40,000still climbing at last reading | 29,900measured | 14 hours |
| /272610 Aug 2026, 13:26 UTC | 10044 minutes – 2 days old | 44,500 views ~199 reactions | 60 minutes: 5,547 interp. → 3.0 hours: 9,324 interp. → 6.0 hours: 13,100 → 12 hours: 20,700 → 24 hours: 29,600 → 2 days: 40,400still climbing at last reading | 29,600measured | 16 hours |
| /272510 Aug 2026, 10:02 UTC | 614 minutes – 3.0 hours old | 8,600 views ~172 reactions | 60 minutes: 5,002 interp. → 3.0 hours: 8,600still climbing at last reading | not yet at 24h | 44 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
6,502 reactions across 34 posts, in 3 distinct kinds. The most used accounts for 73.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4,778 | 73.5% | |
| 👻 | 954 | 14.7% | |
| 🕊 | 770 | 11.8% |
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 35 of the 35 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 6,737reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 31 July 2026 to 12 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqwacL58 | 1 | 7 August 2026 | 7 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 35 most recent posts we hold, published 31 July 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Sticker, posted without a caption
❤68👻11🕊8
Sticker, posted without a caption
❤104🕊10👻8
Sticker, posted without a caption
❤161👻50🕊23
Sticker, posted without a caption
❤151🕊16👻14
😱 ЕГЭ нужно усложнить, — экс-глава Минобразования По его словам, более сложный экзамен позволит точнее распределять выпускников по уровню знаний на фоне высокой конкуренции за места в вузах. Снижения среднего балла при этом бояться не нужно, считает он.
👻128🕊46❤42
Sticker, posted without a caption
❤155👻18🕊18
Sticker, posted without a caption
❤148👻27🕊24
Sticker, posted without a caption
❤146👻17🕊17
Sticker, posted without a caption
❤142🕊22👻14
Sticker, posted without a caption
❤147🕊28👻15
Sticker, posted without a caption
❤147👻19🕊19
Sticker, posted without a caption
❤134👻27🕊18
Showing the 12 most recent of 35 posts we hold for @stikery_emodzi_memy. 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 — 349,328 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.
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.
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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
One domainthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Стикерач” (@stikery_emodzi_memy), 1,263,332 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/stikery_emodzi_memy.
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.