Channel
@yplaqs
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
244subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001921256729 |
|---|---|
| Type | Channel |
| Username | @yplaqs |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 27 August 2026 |
| On Telegram | t.me/yplaqs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 10:37 | 244 | -4 |
| 14 Aug 2026, 14:47 | 248 | -1 |
| 8 Aug 2026, 09:32 | 249 | no change |
| 7 Aug 2026, 14:18 | 249 | first reading |
12 posts held, back to 2 August 2025 — 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.
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 8 August 2026 |
|---|---|
| Posts held | 12 (2 August 2025 – 8 August 2026) |
| Views total | 307 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:32 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.
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.
381 reactions across 11 posts, in 20 distinct kinds. The most used accounts for 30.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5328104482003771571 | 115 | 30.2% | |
| custom 5278403318022947329 | 44 | 11.5% | |
| custom 5416080444611393491 | 30 | 7.87% | |
| custom 5258346022614093298 | 26 | 6.82% | |
| custom 5368690419712401425 | 25 | 6.56% | |
| custom 5188589697823170361 | 22 | 5.77% | |
| custom 5323734490219036081 | 17 | 4.46% | |
| custom 5190653446788765900 | 15 | 3.94% | |
| custom 5336997344934112901 | 14 | 3.67% | |
| custom 5213080413093785150 | 13 | 3.41% | |
| custom 5416016780311167293 | 10 | 2.62% | |
| custom 5334936598150675332 | 9 | 2.36% | |
| custom 5418034899544208681 | 8 | 2.10% | |
| custom 6273614830406472816 | 8 | 2.10% | |
| custom 5345989967069858881 | 6 | 1.57% | |
| custom 5415800631787026377 | 6 | 1.57% | |
| custom 5271704436056537349 | 5 | 1.31% | |
| custom 5416008241916179177 | 4 | 1.05% | |
| custom 5237905066366631362 | 2 | 0.525% | |
| custom 5258230286130366593 | 2 | 0.525% |
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 12 of the 12 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 381reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 2 August 2025 to 8 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 @yplaqs. 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 12 most recent posts we hold for this entry, published 2 August 2025 to 8 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.
hi
custom 62736148304064728167custom 52717044360565373493custom 53459899670698588812custom 52130804130937851501custom 52379050663666313621custom 53349365981506753321
Signed нурик???
топ способов убить канал: 1. начать щитпостить
custom 52130804130937851506custom 52379050663666313621custom 53349365981506753321custom 53459899670698588811
Signed нурик???
Video message, posted without a caption
custom 52130804130937851506custom 53349365981506753322custom 53459899670698588812custom 52717044360565373491custom 62736148304064728161
Signed нурик???
фак
custom 53349365981506753325custom 52717044360565373491custom 53459899670698588811
Signed нурик???
доигрался
Signed нурик???
Photo, posted without a caption
custom 53281044820037715714custom 54158006317870263773custom 54160804446113934912custom 54180348995442086812
Signed нурик???
мы с тобой махнулись местами
custom 541608044461139349123custom 532810448200377157111custom 54160167803111672939custom 54158006317870263773custom 54160082419161791772custom 54180348995442086812
Video, posted without a caption
custom 532373449021903608117custom 533699734493411290114custom 532810448200377157113custom 54160804446113934915custom 54160167803111672931
⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️
custom 527840331802294732944custom 532810448200377157130custom 536869041971240142525custom 54160082419161791772
27
custom 532810448200377157119custom 518858969782317036110custom 51906534467887659009custom 52583460226140932984custom 54180348995442086812
🗣
custom 532810448200377157121custom 518858969782317036110custom 52583460226140932989
send him 2-3 years dagestan and forget
custom 532810448200377157117custom 525834602261409329813custom 51906534467887659006custom 51885896978231703612custom 52582302861303665932custom 54180348995442086812
Showing the 12 most recent of 12 posts we hold for @yplaqs. 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.
Citation-graph rank — 286,540 of 1,628,524entries 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.
Named by 3 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“it's time плагс” (@yplaqs), 244 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/yplaqs.
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.