Channel
@pustqq
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
82subscribers
+0 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002043968578 |
|---|---|
| Type | Channel |
| Username | @pustqq |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pustqq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 08:00 | 82 | no change |
| 30 Aug 2026, 07:45 | 82 | first reading |
8 posts held, back to 9 August 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.
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 28 August 2026 |
|---|---|
| Posts held | 8 (9 August 2026 – 28 August 2026) |
| Views total | 540 |
| Reactions total | 58 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 08:00 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 30 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 3 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.
66 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 16.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5282759243789780569 | 11 | 16.7% | |
| custom 5440396741260098770 | 10 | 15.2% | |
| custom 5363837012178659786 | 9 | 13.6% | |
| custom 5382131433965908302 | 9 | 13.6% | |
| custom 5366548437917526534 | 7 | 10.6% | |
| custom 5379666620954221181 | 7 | 10.6% | |
| custom 5453897687487242789 | 7 | 10.6% | |
| custom 5188320875820106860 | 6 | 9.09% |
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 8 of the 8 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 66 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 9 August 2026 to 28 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.
😮💨помогает чем может @t9q_q
custom 53665484379175265342custom 53821314339659083022custom 52827592437897805691custom 53638370121786597861custom 53796666209542211811custom 54403967412600987701
вайбик ласт деньковвв 🧃
custom 52827592437897805692custom 51883208758201068601custom 53665484379175265341custom 53796666209542211811custom 53821314339659083021custom 54538976874872427891
🤍🪽
custom 53638370121786597865custom 53796666209542211812custom 54403967412600987702custom 53665484379175265341custom 53821314339659083021
у меня ебанный гиперфикс на человеке пауке 🫠🫠🕷️
custom 52827592437897805692custom 53665484379175265342custom 54538976874872427891
Photo, posted without a caption
custom 54403967412600987705custom 54538976874872427894custom 53796666209542211812custom 52827592437897805691custom 53638370121786597861
😝
custom 53821314339659083024custom 53796666209542211811custom 54403967412600987701
Photo, posted without a caption
custom 51883208758201068605custom 53638370121786597862custom 53665484379175265341
Video, posted without a caption
custom 52827592437897805695custom 53821314339659083021custom 54403967412600987701custom 54538976874872427891
Showing the 8 most recent of 8 posts we hold for @pustqq. 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.
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.
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.
“empty” (@pustqq), 82 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/pustqq.
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.