Channel
@avspizdatt
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
255subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002676416986 |
|---|---|
| Type | Channel |
| Username | @avspizdatt |
| Created | 25 July 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/avspizdatt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 17:37 | 255 | -4 |
| 8 Aug 2026, 09:16 | 259 | no change |
| 7 Aug 2026, 19:38 | 259 | first reading |
7 posts held, back to 25 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 29 March 2026. An engagement rate over an empty window would be a number about nothing.
507 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 21.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5460939299253936355 | 109 | 21.5% | |
| custom 5273805783165862374 | 95 | 18.7% | |
| custom 5291867984661344035 | 88 | 17.4% | |
| custom 5273964636826271675 | 74 | 14.6% | |
| custom 5202139821425856754 | 72 | 14.2% | |
| custom 5303547383718634410 | 64 | 12.6% | |
| custom 5276243748336989084 | 4 | 0.789% | |
| custom 5274105331364956037 | 1 | 0.197% |
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 5 of the 7 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 507reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 25 July 2025 to 29 March 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.
🩸 avspizdatt 🩸 буст|сс
custom 529186798466134403563custom 546093929925393635555custom 520213982142585675439custom 527380578316586237427custom 52739646368262716758custom 53035473837186344104custom 52741053313649560371
Signed q1ww #iloved1rww
🩸 avspizdatt 🩸 буст|сс
custom 527380578316586237437custom 527396463682627167527custom 546093929925393635521custom 529186798466134403514custom 530354738371863441014custom 52021398214258567541
Signed q1ww #iloved1rww
🩸 avspizdatt 🩸 буст|сс
custom 530354738371863441029custom 527396463682627167515custom 527380578316586237413custom 54609392992539363557custom 52021398214258567544custom 52918679846613440354
Signed авы от пиздатого
🩸 avspizdatt 🩸 буст|сс
custom 527396463682627167524custom 546093929925393635517custom 527380578316586237413custom 53035473837186344105custom 52021398214258567544custom 52918679846613440353
Signed авы от пиздатого
🩸 avspizdatt 🩸 буст|сс
custom 520213982142585675424custom 530354738371863441012custom 54609392992539363559custom 52738057831658623745custom 52762437483369890844custom 52918679846613440354
Channel photo removed
Channel created
Showing the 7 most recent of 7 posts we hold for @avspizdatt. 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 — 867,189 of 1,350,102entries 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 2 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“авы от пиздатого” (@avspizdatt), 255 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/avspizdatt.
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.