ПОДАРКИ ВЫШЛИ
custom 535938641244772973822custom 535931059339005422418custom 535949102067119482411custom 53593409330390359231

Channel
@snyalcepik
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
358,339subscribers
+8,935 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1002672842945 |
|---|---|
| Type | Channel |
| Username | @snyalcepik |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/snyalcepik |
Gambling & betting — 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 99% 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 |
|---|---|---|
| 13 Aug 2026, 00:27 | 358,339 | +4,520 |
| 11 Aug 2026, 23:54 | 353,819 | +463 |
| 11 Aug 2026, 03:23 | 353,356 | +3,172 |
| 10 Aug 2026, 02:33 | 350,184 | -58 |
| 9 Aug 2026, 03:53 | 350,242 | +630 |
| 8 Aug 2026, 01:03 | 349,612 | +208 |
| 7 Aug 2026, 17:46 | 349,404 | first reading |
32 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 17 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 | 32 (31 July 2026 – 12 August 2026) |
| Views total | 1,163,240 |
| Reactions total | 27,669 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 17:48 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.
27,669 reactions across 32 posts, in 8 distinct kinds. The most used accounts for 19.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5359385394540483186 | 5,247 | 19.0% | |
| custom 5359497609151023850 | 4,729 | 17.1% | |
| custom 5359310593390054224 | 4,525 | 16.4% | |
| custom 5359340933039035923 | 4,422 | 16.0% | |
| custom 5359386412447729738 | 3,556 | 12.9% | |
| custom 5359367450167118414 | 2,221 | 8.03% | |
| custom 5359491020671194824 | 1,951 | 7.05% | |
| custom 5359288723416583653 | 1,018 | 3.68% |
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 32 of the 32 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 27,669reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @snyalcepik. 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 32 most recent posts we hold for this entry, published 31 July 2026 to 12 August 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.
ПОДАРКИ ВЫШЛИ
custom 535938641244772973822custom 535931059339005422418custom 535949102067119482411custom 53593409330390359231
Раздача 3.000⭐️ на 1 день ❤️ условия: нажми кнопку внизу и забусти канал
custom 535931059339005422482custom 535934093303903592333custom 535938641244772973822custom 535949760915102385010custom 53593674501671184147custom 53594910206711948243custom 53592887234165836532
подарю пепе тогда
custom 5359385394540483186382custom 535949102067119482484custom 535931059339005422477custom 535938641244772973835custom 535934093303903592318custom 535949760915102385013custom 535936745016711841410custom 53592887234165836535
я тебя найду
custom 5359385394540483186671custom 5359497609151023850134custom 5359310593390054224108custom 535934093303903592328custom 535938641244772973820custom 535949102067119482420custom 535936745016711841419custom 535928872341658365312
ебать ахуел
custom 53593853945404831861,760custom 5359497609151023850396custom 5359491020671194824278custom 535931059339005422481custom 535938641244772973870custom 535934093303903592350custom 535936745016711841450custom 535928872341658365340
снесли саба...
custom 5359497609151023850787custom 5359310593390054224168custom 5359367450167118414133custom 535934093303903592336custom 535938641244772973818custom 535949102067119482418custom 535928872341658365314custom 535938539454048318610
ЫХВХАХВХАХ
custom 5359340933039035923638custom 5359310593390054224150custom 5359497609151023850100custom 535936745016711841431custom 535938641244772973827custom 535949102067119482419custom 535928872341658365316custom 535938539454048318616
ПУТИН В ТГ
custom 5359385394540483186730custom 5359310593390054224162custom 5359386412447729738102custom 535936745016711841423custom 535934093303903592322custom 535949102067119482414custom 535949760915102385011custom 53592887234165836539
@soap ЕБАТЬ ЮЗ КУПИЛ
custom 5359367450167118414436custom 535931059339005422474custom 535938641244772973847custom 535949760915102385018custom 535934093303903592313custom 535949102067119482410custom 53593853945404831867custom 53592887234165836533
раздача в чатике 🧸 раздача включена 24/7 🧸 🧸🧸🧸🧸🧸🧸🧸
custom 5359288723416583653117custom 535949760915102385034custom 535931059339005422432custom 535949102067119482410custom 53593674501671184143custom 53593864124477297383
МАХ В КОСМОСЕ
custom 5359288723416583653258custom 535936745016711841456custom 535938641244772973840custom 535931059339005422416custom 53594976091510238506custom 53593409330390359235custom 53594910206711948243
custom 5359497609151023850925custom 5359367450167118414208custom 5359385394540483186142custom 535931059339005422469custom 535949102067119482442custom 535938641244772973834custom 535934093303903592333custom 535928872341658365327
Showing the 12 most recent of 32 posts we hold for @snyalcepik. 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.
@snyalcepik edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 125,216 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 8 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“#снялцепи” (@snyalcepik), 358,339 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/snyalcepik.
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.