3 measurements spanning 7 days, net +4. 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 708–714 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Aug 2026, 00:52
713
+4
19 Aug 2026, 10:14
709
no change
18 Aug 2026, 20:31
709
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 page of Telegram’s post history, 20 posts per page.
ERR · 30 days
14.6%
avg views ÷ 713 subscribers
Avg views / post
104
1 post measured
Reaction rate
1.92%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 15 August 2026
Posts held
20 (12 March 2026 – 15 August 2026)
Views total
104
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
18 Aug 2026, 20:31 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
60 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 63.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
38
63.3%
🔥
12
20.0%
🎉
6
10.0%
👍
3
5.00%
💯
1
1.67%
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 14 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 60 reactions 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 15 August 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.
📣 #اطلاعیه
کاربران گرامی،
به اطلاع میرساند از روز گذشته، دسترسی به سرویس Gemini از طریق بسیاری از سرویسهای فیلترشکن با اختلال مواجه شده و برخی کاربران هنگام استفاده، با پیام خطای زیر روبهرو میشدند:
“The service is not available in your country”
این اختلال ناشی از محدودیتهای اعمالشده در دسترسی به سرویس Gemini بوده است.
این مشکل از ساعاتی پیش در سرورهای مجموعه ما بهطور کامل برطرف شده است و در حال حاضر کاربران …
📣 #اطلاعیه
‼️ کاربران گرامی،لطفاً توجه داشته باشید که برای استفادهی صحیح و بدون اختلال از سرویسها، نصب و استفاده از آخرین نسخهی نرمافزارها الزامی است.
📌 با وجود اطلاعرسانیهای قبلی مبنی بر بهروزرسانی نرمافزارها، همچنان برخی کاربران با پشتیبانی در ارتباط هستند در حالی که نرمافزار مورد استفادهی آنها بهروز نیست. لازم به ذکر است استفاده از نسخههای قدیمی ممکن است باعث اتصال ناموفق، ناپایداری یا اختلال در عمل…
📣 #اطلاعیه
کاربران گرامی،
از دقایقی پیش، سیستم مانیتورینگ ما اختلالاتی را بر روی برخی اپراتورها برای اتصال به بعضی سرویسهای نامحدود شناسایی کرد. به همین منظور، سرویسها جهت بهبود پایداری و کیفیت سرویس بهروزرسانی شدند.
در صورتی که با مشکل اتصال مواجه هستید، کافی است سرورها را در نرمافزار خود بهروزرسانی کنید تا سرویسهای جدید دریافت شده و مشکل برطرف شود.
از همراهی و شکیبایی شما سپاسگزاریم.
🆔 @KaktosVPN
🤖 @Kakt…
📣 #اطلاعیه
➖سرورها به روز شدند.
🔻 برای بهبود کیفیت سرویس خود لینک خود را آپدیت کنید.
🔺اطمینان حاصل کنید که نرمافزار شما بهروز است.
✍️ همچنین لازم به ذکر است که کشورهای 🇵🇱 و 🇺🇸 نیز به لیست سرورها اضافه شدند.
🆔 @KaktosVPN
🤖 @KaktosVPNbot
📣 #اطلاعیه
➖سرورها به روز شدند.
🔻 برای بهبود کیفیت سرویس خود لینک خود را آپدیت کنید.
✍️ اطمینان حاصل کنید که نرمافزار شما بهروز است.
🆔 @KaktosVPN
🤖 @KaktosVPNbot
📣 #اطلاعیه
‼️ کاربران گرامی، لطفاً به هیچ عنوان ساعت گوشی خود را به صورت دستی تنظیم نکنید؛ زیرا این کار باعث اختلال در اتصال به ویپیان و وبسایتها میشود.
خواهشمند است تنظیمات ساعت گوشی خود را حتماً روی حالت خودکار (Automatic) قرار دهید.
📣 #اطلاعیه
‼️ کاربران گرامی، در صورت بروز مشکل هنگام اضافه کردن یا آپدیت لینک اشتراک. کافیست لینک اشتراک اضطراری جدید را با گزینهی مدیریت سرویس از ربات دریافت نمایید.
🆔 @KaktosVPN
🤖 @KaktosVPNbot
📣 #اطلاعیه
‼️ کاربران گرامی، لطفاً توجه داشته باشید که برای استفاده از سرویسها، نصب آخرین نسخهی نرمافزارها الزامی است. برای سیستمعامل iOS برنامهی Happ و برای Android برنامهی v2rayNG پیشنهاد میشود.
🔗👩💻 لینک دانلود نسخهی بهروز V2rayNG
🔗📱 لینک دانلود Happ از اپاستور
🔗❤️ لینک دانلود Happ برای windows
🙏 همچنین به اطلاع میرساند بهدلیل حجم بسیار بالای پیامها، پاسخگوییِ تیم پشتیبانی با تأخیر همراه است.
د…
📣 #اطلاعیه
🖥 تعدادی سرور جدید مخصوص اینترنت همراه اول و زیتل اضافه شده است. لطفاً با بهروزرسانی (آپدیت) اشتراک خود، به این سرورها دسترسی پیدا کنید.
‼️ ممکن است برای بهروزرسانیِ اشتراک، به فیلترشکن نیاز داشته باشید. در این صورت میتوانید از طریق گزینهی «دریافت کانفیگ دستی»، سرورها را دریافت کنید.
🆔 @KaktosVPN
🤖 @KaktosVPNbot
📣 #اطلاعیه
‼️ به اطلاع کاربران محترم میرساند، با توجه به اختلالات و قطعیهای ایجادشده ناشی از جنگ و قطع اینترنت، تصمیم به اعمال زمان جبرانی برای سرویسهای اصلی اتخاذ شده است. لازم به ذکر است که زمان اضافه شده به سرویسها از مدت زمان اختلالات اینترنتی بیشتر میباشد.
✔️ فرآیند اعمال این افزایش، بهطور کامل صورت گرفته است.
📌 دقت داشته باشید که اینترنت هنوز بهطور کامل متصل نشده و سرویسها بهطور کامل در دسترس نیستند…
📣 #اطلاعیه
➖سرورها به روز شدند.
🔻 برای بهبود کیفیت سرویس خود لینک خود را آپدیت کنید. سرورها در همین لحظه تغییر پیدا کردند و به روز شدند.
🆔 @KaktosVPN
🤖 @KaktosVPNbot
📣 #اطلاعیه
🌐 به نظر بعضی از دوستان نمیتوانند سابسکریپشن رو به نرمافزارهاشون اضافه کنند. در صورتی که امکان اضافه کردن ساب رو ندارید میتونید کانفیگ دستی رو از ربات دریافت کنید.
🆔 @KaktosVPN
🤖 @KaktosVPNbot
❤2
Showing the 12 most recent of 20 posts we hold for @kaktosvpn. 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.
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.
آیا شما موافق با تامین و فروش کانفیگ حجمی در این شرایط با قیمت معقول(نسبت به شرایط) هستید؟
بله.89%
خیر.11%
Shares as published. 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 20 most recent posts we hold, published 12 March 2026 to 15 August 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
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
iProxy | پروکسی نیم بها | نت ملی | فیلتر شکن | فیلترشکن رایگان @iProxy_IR · 79,766 Telegram ranks this channel #4 of 32 here — alongside 31 others — read 18 August 2026
Bull Vpn 🦬 فیلترشکن @BullVpnNet · 65,133 Telegram ranks this channel #13 of 28 here — alongside 27 others — read 21 August 2026
IranProxy | ایران پروکسی @iranproxy · 391,201 Telegram ranks this channel #31 of 58 here — alongside 57 others — read 1 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 26 August 2026 — this
entry's latest reading, not the date you are reading this.
“Kaktos VPN | کانفیگ فیلترشکن” (@kaktosvpn), 713 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/kaktosvpn.
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.