кто хочет вступайте

Channel
꒰ 🩵 𝚡𝚡𝚡𝚊𝚟𝚎𝚛 • ᶦᶰᶠᵒ
@xxxaverr
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
126subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002713017695 |
|---|---|
| Type | Channel |
| Username | @xxxaverr |
| Created | Between 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/xxxaverr |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 14:26 | 126 | -3 |
| 9 Aug 2026, 01:31 | 129 | no change |
| 7 Aug 2026, 23:58 | 129 | -1 |
| 7 Aug 2026, 18:49 | 130 | first reading |
Engagement
20 posts held, back to 12 March 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 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 20 posts for this entry, the most recent from 4 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 18s
- Average length
- 9s
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.
Reaction mix
53 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 15.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5283011418499605504 | 8 | 15.1% | |
| custom 5215594184437692518 | 7 | 13.2% | |
| custom 5454363506755264892 | 7 | 13.2% | |
| custom 5215437327937075664 | 6 | 11.3% | |
| custom 5215527273142189115 | 5 | 9.43% | |
| custom 5215601674860653342 | 5 | 9.43% | |
| custom 5215706553667056716 | 5 | 9.43% | |
| ☃ | 5 | 9.43% | |
| custom 5215228760030214227 | 3 | 5.66% | |
| 🐳 | 2 | 3.77% |
Custom emoji. 8 of the rows above are 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 7 of the 20 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 53reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 March 2026 to 4 May 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.
Recent posts
йоу
custom 52830114184996055042custom 52155941844376925181custom 52156016748606533421custom 52157065536670567161
@cutedarkinfo
custom 54543635067552648922custom 52155272731421891151custom 52157065536670567161custom 52830114184996055041
File, posted without a caption
custom 52154373279370756641custom 52155272731421891151custom 52155941844376925181custom 52156016748606533421custom 52157065536670567161custom 52830114184996055041custom 54543635067552648921
Sticker, posted without a caption
Sticker, posted without a caption
🤩🤩🤩🤩🤩🤩🤩🤩 🎀🎀🎀🤩ew 🤩ideo 🎀🎀🎀 Tik tok 🎀🎀🎀 (click) 🎀🌸 C r : J ennie 🎀🎀 поддержать нас 🎀🎀 #xxxrp ⭐
☃3custom 52155941844376925183custom 52152287600302142272custom 52154373279370756642custom 52156016748606533422custom 52830114184996055042custom 54543635067552648922🐳1
Sticker, posted without a caption
🤩🤩🤩🤩🤩🤩🤩🤩 🎀🎀🎀🤩ew 🤩ideo 🎀🎀🎀 ⚫️ik tok 🎀🎀🎀 (click) 🎀🌸 C r : J ennie 🎀🎀 поддержать нас 🎀🎀 #xxxrp ⭐
☃2custom 52154373279370756642🐳1custom 52152287600302142271custom 52155272731421891151custom 52155941844376925181custom 52156016748606533421custom 52157065536670567161
Sticker, posted without a caption
🎀🎀🎀 🎀ew 🎀nion [ 🤩 クソだりぃな 酒が空いたグラスあれば直ぐに注ぎなさい 皆がつまみ易いように串外しなさい 会計や注文は先陣を切る 不文律最低限のマナーです はぁ?うっせぇうっせぇうっせぇわ くせぇ口塞げや限界です 絶対絶対現代の代弁者は私やろがい もう見飽きたわ 二番煎じ言い換えのパロディ うっせぇうっせぇうっせぇわ 丸々と肉付いたその顔面にバツ 🤩 ] 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 😂 @xxxaver & @Malivatmii
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @xxxaverr. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@xxxaverr named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 10 August 2026 – 10 August 2026
Cite this entry
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“꒰ 🩵 𝚡𝚡𝚡𝚊𝚟𝚎𝚛 • ᶦᶰᶠᵒ” (@xxxaverr), 126 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/xxxaverr.
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.