Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 86% 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
35 measurements spanning 43 days, net +2,280. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,050–16,014 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
18 Sept 2026, 08:59
15,672
+103
16 Sept 2026, 05:19
15,569
+198
14 Sept 2026, 11:00
15,371
+237
12 Sept 2026, 20:20
15,134
+113
10 Sept 2026, 22:37
15,021
+313
7 Sept 2026, 20:17
14,708
+95
4 Sept 2026, 18:38
14,613
+14
3 Sept 2026, 01:02
14,599
+9
1 Sept 2026, 20:15
14,590
+8
31 Aug 2026, 22:08
14,582
+21
31 Aug 2026, 01:13
14,561
+61
30 Aug 2026, 00:34
14,500
+53
28 Aug 2026, 23:03
14,447
+16
28 Aug 2026, 01:04
14,431
+28
27 Aug 2026, 02:43
14,403
+10
26 Aug 2026, 05:17
14,393
+6
25 Aug 2026, 04:23
14,387
+44
24 Aug 2026, 03:15
14,343
+96
22 Aug 2026, 12:39
14,247
+95
21 Aug 2026, 05:04
14,152
first reading
Engagement
27 posts held, back to 19 July 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 50 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
35.3%
avg views ÷ 15,672 subscribers
Avg views / post
5,530
4 posts measured
Reaction rate
3.25%
reactions ÷ views · ER floor
Posts in window
4
of 27 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 2 September 2026
Posts held
27 (19 July 2026 – 2 September 2026)
Views total
22,100
Reactions total
718
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
2 Sept 2026, 18:27 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.
Reaction mix
5,012 reactions across 27 posts, in 12 distinct kinds. The most used accounts for 78.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
3,914
78.1%
👍
443
8.84%
🔥
393
7.84%
🕊
106
2.11%
❤🔥
56
1.12%
😍
34
0.678%
👏
29
0.579%
🤝
18
0.359%
⚡
8
0.16%
🎉
5
0.1%
🏆
4
0.08%
🙏
2
0.04%
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 27 of the 27 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 5,012 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 19 July 2026 to 2 September 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.
Telegram Stars
Stars received
112
across the posts below
Posts paid on
6
of 27 we hold a reading for · 22%
Most on one post
79
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @CluvexStudio. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 27 most recent posts we hold for this entry, published 19 July 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
یه توضیحی بدم درباره کلاینت که دارم روش کار میکنم یکی دو ماه شده فکر کنم. :))
دقیق دارم تست هاشو انجام میدم روی همه پلتفرما یکم زمان میبره
که یه اپ بینقص منتشر کنم... تمومه ولی یکم وسواسی هستیم ولی در آخر بدون باگ منتشر میکنیم
و راحت بشید برای کسانی که سختشونه کار با ترموکس...
از طرفی دیگه داریم تلاش میکنیم روی استور های رسمی هم بیاریم. و قطعا میاریم روی همه پلتفرما
Android - iOS - Linux - MacOS - Windows
اینجور…
درود.
ما به دنبال چند دولوپر C / Rust میگردیم که توی تست و توسعه زبان Cyrus کمک مون کنن.
(کار بلد و متخصص، وایب کدر نه)
در حال حاضر میشود برنامه های کوچک-متوسط با این زبان ساخت و کتابخانه C رو از طریق FFI صدا زد.
هدف ما این است که مشارکت کنندگان با دقت و حوصله درستی جزییات را در سرتاسر زبان تست و تایید کنند. که بتوانیم زبان را استیبل کنیم و قویتر به توسعه کامپایلر stage1 بپردازیم.
اگر کسی علاقه مند هست لطفا در گر…
جدیدا خیلیا میبینم که دانش شبکه ای ندارن (اسم نمیبرم) و اصلا نحوه کارکرد فایروال و DPI ایران رو هم خبر ندارن پروژه میزنن و به اسم خودشون ثبت میکنن و اسمی از وایب کد کردنشون نمیبرن.
باید یه رسمی بین ما ایرانیا ترند بشه که هر پروژه وایب کدی حداقل بنویسه زیرش وایب کد شده
(سر همین خیلی از چینیا هیت خوردیم)
با اسباببازیشون (Claude) صفر تا صد وایب کد میکنن و پروژه میزنن بدون اینکه ازش سر در بیارن
قصد بی احترامی نیست …
آپدیت جدید Aether v1.8.0:
توی این آپدیت بیشتر روی پایداری و کرش کار شده
(بهتره آپدیت کنید. استیبل ترین ورژنهستش)
کرش gool فیکس شد:
اگه Gool رو انتخاب میکردید به محض اینکه یکی از دو تانل یا سرور socks متوقف میشد
کل هسته کرش میکرد و بعدش هرچی reconnect میزدی بالا نمیومد
(این رو یکی Contributor ها توی #91 فیکس کرد issue #87)
///
تانل وایرگارد دیگه با یه panic از کار نمیوفته
اگه یکی از تسک های داخلی panic…
یه اپدیت میدم برای این Aether و اکثر مشکلات گزارش شده رو فیکس میکنم. + کلاینت هم براش زدم این مدت :))
اپدیتشو میدم وارپ داره + سایفون
(کلاینت شناخته شدهست و از قبل بوده فقط الان Maintainerاش من شدم و قراره دسکتاپ و iOS هم منتشر کنم).
---
یه پروژه دیگه هم توسعه دادم قبلا
خیلی وقته ( نزدیک 6 ماه یا شایدم بیشتر کارش بود. توسعهاش دادم بلاخره )...
تقریبا تمومه و باید یه داکیومنت تمیز و کامل براش بنویسم و منتشرش کنم …
آپدیت جدید Aether:
توی این آپدیت روی مسیریابی (روتینگ) و اتصال از پشت پروکسی کار شده
پروکسی بالادست :)) یا همون upstream اضافه شد
اگه یه پروکسی دیگه روی سیستمتون اجراست میتونی Aether رو پشتش chain کنی:
aether --upstream socks5://127.0.0.1:1080
با رمز: socks5://user:[email protected]:1080
روی هر سه حالت کار میکنه: مسک H3، مسک H2، وارپ و gool
یه نکته بگم: H3 و وارپ و gool روی UDP هستن پس SOCKS5 لازم دارن که UDP associa…
یک چندوقتیه درگیرم همونطور که میدونید کاراموزی و پروژه دانشگاه رو برداشتم و امروز برای یک کاری لازم شد تا یک سیستمی مثل شکن بالا بیارم که ترافیک رو از طریق dns برای یک سری سایت منتخب بتونه route کنه.
خب حالت منطقیش اینه که شما یک ریزالور مثل dnsmasq بیارید بالا و یک چیزی مثل nginx بذارید جلوش ( به این روش میگن smart dns) که باهاش برای سایتهای منتخبتون ترافیک رو فوروارد کنید.
خب این برای DNS، DoH و DoT معقول و اوک…
آپدیت جدید Aether:
برای بهتر شدن اتصال توی این وضعیت اختلال
روی Warp و مسک کار کردم و شانس وصل شدن بیشتر شده
توصیه میکنم آپدیت کنید حتما
\\\
اسکن وایرگارد درست شد
آیپی رو بهتر و واقعی تر پیدا میکنه.
و برای هر آیپی فقط یه پورت رو امتحان میکرد
یعنی بقیه پورت های جایگزین عملا هیچوقت تست نمیشدن. الان همهشون چک میشن.
(این رو یکی مشارکت کننده هامون #76 گزارش داد)
\\\
پروکسی HTTP اضافه شد
پورتش 1820 هستش
قبلا فقط SOC…
ستینگ دیفیکس DefyxVPN رو چک کنید
بخش Connection Method گزینه FASTLANE رو فعال کنید و اولویت اول قرار بدید
چند سرور پرسرعت و با کیفیت اضافه کردیم تا اتصال بهتر و پایدارتری داشته باشید.
(نسبت به گزینه های دیگه توی این شرایط پرسرعت تر و بهتره)
⭕️ اطلاعیه:
چند پورت مهم مانند پورت ٢٢ بر روی آی پیهای ایران به سمت شبکه بین الملل از سمت زیرساخت محدود شده است.
همچنین شواهد و بررسیها نشان میدهند که ارتباطات زیرساخت برای ایجاد یک قطعی گسترده در حالت آماده باش میباشد.
منبع: منیجیت
از وقت و زمانی که گذاشتید Pr بدید
و issue باز کنید و باگ گزارش بدید ممنونم.
اونایی که بدرد نمیخوردن و وایب کد بودن (کد بیکیفیت Ai)
قبول نشدن.
"سر این قضیه خیلی جدیام"
نکته:
(مگر اینکه کدی که وایب کد شده اوکی باشه و بدون هیچ ایرادی)
بازم میگم از قبل باید دانش شبکه داشته باشید که بتونید
توی پروژه مشارکت کنید.
من دست تنهام و مشارکت کننده کمه سر همین دیر آپدیت میدم
///
هدف این پروژه کمک به دسترسی بهتر مردم به اینتر…
❤161🔥8👍5⚡3🤝1
Showing the 12 most recent of 27 posts we hold for @CluvexStudio. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@CluvexStudio edited 2 posts 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.
First edit seen
19 August 2026
Most recent edit
30 August 2026
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
از کدوم پروتکل Xray/v2ray بیشتر استفاده میکنید؟
و اگه پروتکل Trojan - Shadowsocks حذف بشه و فقط Vless/Vmess و ... بمونن اوکیه؟ نظرتون رو بگید خیلی مهمه بگید توی نظرسنجی کدوم پرکاربرد تره و بیشتر استفاده میشه:
Vless71%
Vmess5%
Trojan5%
Shadowsocks3%
Hysteria4%
Wireguard11%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 27 most recent posts we hold, published 19 July 2026 to 2 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
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.
Mentions
Named by 6 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.
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“CluvexStudio” (@CluvexStudio), 15,672 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CluvexStudio.
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.