Channel
@xsvex
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
9,283subscribers
+347 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002140941881 |
|---|---|
| Type | Channel |
| Username | @xsvex |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/xsvex |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 |
|---|---|---|
| 18 Sept 2026, 16:18 | 9,283 | -58 |
| 14 Sept 2026, 04:38 | 9,341 | +100 |
| 10 Sept 2026, 12:01 | 9,241 | +83 |
| 4 Sept 2026, 21:38 | 9,158 | +70 |
| 1 Sept 2026, 11:02 | 9,088 | -42 |
| 29 Aug 2026, 14:38 | 9,130 | +46 |
| 26 Aug 2026, 17:54 | 9,084 | +93 |
| 23 Aug 2026, 10:24 | 8,991 | -15 |
| 19 Aug 2026, 13:52 | 9,006 | +27 |
| 16 Aug 2026, 20:34 | 8,979 | +16 |
| 13 Aug 2026, 17:18 | 8,963 | +79 |
| 11 Aug 2026, 02:43 | 8,884 | -52 |
| 7 Aug 2026, 16:53 | 8,936 | no change |
| 7 Aug 2026, 15:46 | 8,936 | first reading |
242 posts held, back to 4 October 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 31 pages 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 | 242 (4 October 2025 – 28 August 2026) |
| Views total | 9,891 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 15:25 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 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.
🔎 تو تلگــــرام ـت به چی نیــــاز داری💨 یه لیست از بهترین موضوعات تلگرام🦆 ☝️🏻 ✨⃟ روانشناســی / توسعــه فـردی : 𝖢𝖫𝖨𝖢𝖪➡️ 🎈⃟ سـرگـرمی / فیلم/گیم و..: 𝖢𝖫𝖨𝖢𝖪➡️ 🪐⃟ دیــراین / تـم / لنگـوئج : 𝖢𝖫𝖨𝖢𝖪➡️ ➡️ 𝒩𝖮𝖵𝖠 𝖳𝖡 💬 @NOVA𝖳𝖡⬅️
تلگرامت خستـهکننده و نامنظـم شده؟ 🍊 🎀🎀🎀🎀🎀🎀🎀🎀 پک خودمراقبتی و برنامهریزی اصولی ✍️ 𝗍𝖺𝗉 𝗍𝖺𝗉 " 𝖿𝗈𝗅𝖽𝖾𝗋 " 🍊 بوتیک دیزاینگوشی٫ تم و لنگوئج٫… ✍️ 𝗍𝖺𝗉 𝗍𝖺𝗉 " 𝖿𝗈𝗅𝖽𝖾𝗋 " 🍊 گیمنت مجازی؟ سرگرمی٫ فیلم و … ✍️ 𝗍𝖺𝗉 𝗍𝖺𝗉 " 𝖿𝗈𝗅𝖽𝖾𝗋 " 🍊
Sticker, posted without a caption
א pinned «ㅤ ㅤ₍ что ₎ 🌟 💲 ты хочешь 🌟 »
Sticker, posted without a caption
Sticker, posted without a caption
ㅤ ㅤ₍ что ₎ 🌟 💲 ты хочешь 🌟
Sticker, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
فوروارد امروز
Sticker, posted without a caption
Showing the 12 most recent of 242 posts we hold for @xsvex. 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.
@xsvex 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Republishes 53 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“א ” (@xsvex), 9,283 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xsvex.
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.