Sticker, posted without a caption

Channel
ᝡᥱᥣ᥎ᥱ𝗍 𑜀ᦅᦅᥒ
@Veunsa
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,089subscribers
-28 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002393047362 |
|---|---|
| Type | Channel |
| Username | @Veunsa |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Veunsa |
Topic
Music — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 07:59 | 1,089 | -11 |
| 14 Sept 2026, 12:55 | 1,100 | +18 |
| 13 Sept 2026, 20:22 | 1,082 | no change |
| 11 Sept 2026, 08:38 | 1,082 | -12 |
| 6 Sept 2026, 23:58 | 1,094 | -3 |
| 2 Sept 2026, 00:05 | 1,097 | +18 |
| 29 Aug 2026, 18:27 | 1,079 | -11 |
| 26 Aug 2026, 20:43 | 1,090 | -11 |
| 23 Aug 2026, 11:26 | 1,101 | -11 |
| 19 Aug 2026, 13:54 | 1,112 | -1 |
| 16 Aug 2026, 05:47 | 1,113 | -4 |
| 14 Aug 2026, 19:24 | 1,117 | first reading |
Engagement
18 posts held, back to 12 September 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 · 30 days
- 3.22%
- avg views ÷ 1,089 subscribers
- Avg views / post
- 35.1
- 18 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 18
- of 18 held
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 13 September 2026 |
|---|---|
| Posts held | 18 (12 September 2026 – 13 September 2026) |
| Views total | 631 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Sept 2026, 20:22 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.
Recent posts
Sticker, posted without a caption
🖤:𝖳𝗁𝖾𝗒 𝗅𝗈𝗈𝗄 𝖿𝗈𝗋 𝖼𝗋𝖺𝖼𝗄𝗌 𝗂𝗇 𝗆𝗒 𝖺𝗋𝗆𝗈𝗋, 𝖻𝗎𝗍 𝖺𝗅𝗅 𝗍𝗁𝖾𝗒 𝖿𝗂𝗇𝖽 𝗂𝗌 𝗍𝗁𝖾 𝖺𝖻𝗒𝗌𝗌 𝗌𝗍𝖺𝗋𝗂𝗇𝗀 𝖻𝖺𝖼𝗄. 💬💬 𝖨’𝗆 𝗇𝗈𝗍 𝗉𝗅𝖺𝗒𝗂𝗇𝗀 𝖺 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋, 𝖨 𝖺𝗆 𝗍𝗁𝖾 𝖺𝖾𝗌𝗍𝗁𝖾𝗍𝗂𝖼 𝗂𝗍𝗌𝖾𝗅𝖿—𝗍𝗁𝖾 𝗋𝖾𝖽 𝗂𝗇 𝗍𝗁𝖾 𝗌𝗁𝖺𝖽𝗈𝗐𝗌, 𝗍𝗁𝖾 𝗌𝗍𝖺𝗋 𝗂𝗇 𝗍𝗁𝖾 𝗆𝗂𝖽𝗇𝗂𝗀𝗁𝗍, 𝖺𝗇𝖽 𝗍𝗁𝖾 𝗌𝗂𝗅𝖾𝗇𝖼𝖾 𝗂𝗇 𝗍𝗁𝖾 𝖼𝗁𝖺𝗈𝗌. 𝖯𝖾𝗈𝗉𝗅𝖾 𝗍𝗋𝗒 𝗍𝗈 𝖽𝖾𝖼𝗈𝖽𝖾 𝗍𝗁𝖾 𝗆𝗒𝗌𝗍𝖾𝗋𝗒, 𝖻𝗎𝗍 𝗍𝗁𝖾𝗒 𝖿𝗈𝗋𝗀𝖾𝗍 𝗍𝗁𝖺𝗍 𝗌𝗈𝗆𝖾 𝗍𝗁𝗂𝗇𝗀𝗌 𝖺𝗋𝖾 𝗆𝖾𝖺𝗇𝗍 𝗍𝗈 𝖻𝖾 𝖿𝖾𝗅𝗍, 𝗇𝗈𝗍 𝗎𝗇𝖽𝖾𝗋𝗌𝗍𝗈𝗈𝖽. 𝖨 𝖺𝗆 𝖺𝗍 𝗉𝖾𝖺𝖼𝖾 𝗐𝗂𝗍𝗁 𝗆𝗒 𝗈𝗐𝗇 𝖽𝖺𝗋𝗄𝗇𝖾𝗌𝗌; 𝗂𝗍’𝗌 𝗍𝗁𝖾 𝗈𝗇𝗅𝗒 𝗉𝗅𝖺𝖼𝖾 𝗐𝗁𝖾𝗋𝖾 𝖨 𝗍𝗋𝗎𝗅𝗒 𝗌𝗁𝗂𝗇𝖾. 💬💬💬 🖤🖤🖤🖤🖤🖤🖤🖤
Sticker, posted without a caption
࣪ ⨍𝗈𝗋𝗐𝖺𝗋𝖽 𝗍𝗁𝗂𝗌 𝗆𝖾𝗌𝗌𝖺𝗀𝖾𝂅 𝖺𝗇𝖽 𝖨’𝗅𝗅 𝗆𝖺𝗄𝖾 𝗒𝗈𝗎 𝖺 𝗉𝗅𝖺𝗒𝗅𝗂𝗌𝗍 𝖻𝖺𝗌𝖾̧𝖽 𝗈𝗇 𝗒𝗈𝗎𝗋 𝗏𝗂𝖻𝖾𝂅 𝖿𝖾𝖺𝗍𝗎𝗋𝗂𝗇𝗀 𝖺 𝖻𝖺𝗇𝖽 𝗈𝗋 𝖺𝗋𝗍𑪒𝗂𝗌𝗍 𝗍𝗁𝖺𝗍 ꭑ𝖺𝗍𝖼𝗁𝖾𝗌 𝗒𝗈𝗎 𝂅 𓎟𓎟𓎟𓎟 ⧾ 𓎟𓎟𓎟𓎟ㅤ 𝗅𝗂𝗆𝗂𝗍 𓏻 𝟣𝟧 𝂅 𝗉𝗋𝗂𝗏𝖺𝗍𝖾 𝂅 𝗆𝗎𝗌𝗍ׅ 𝗃𝗈𝗂𝗇
Sticker, posted without a caption
Signed ㅤㅤᥳᩛᦅɾ𐔎
الان میام خوشحالت کنم
Signed ㅤㅤᥳᩛᦅɾ𐔎
بمیرم برا بچم
Signed ㅤㅤᥳᩛᦅɾ𐔎
خیلی رندم ناراحتم
این پیامو فوروارد کنید تا ازتون یک سوال درمورد چنلتون بپرسم و جواب بدید 🦌 توی چنلتون میگردم و اگر چیز بامزهای بود فوروارد میکنم اینجا
Photo, posted without a caption
«اه از اینکه همه چیز به مرگ ختم بشود ناراحتم! باید بستنی بخوریم، لطفا صف بگیرید!!»
Showing the 12 most recent of 18 posts we hold for @Veunsa. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Named by 5 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“ ᝡᥱᥣ᥎ᥱ𝗍 𑜀ᦅᦅᥒ” (@Veunsa), 1,089 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Veunsa.
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.