🤔 به علت مشکلاتفنی از سمت ارتباطاتزیرساخت اینترنت دیتاسنترپرواز قطع شده بود و کانفیگ های حجمی نیز قطع شده بودند، طی اعلامیه دیتاسنتر مشکل رفع گردیده است.
❤7

Channel
@WixmoreVpn
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
23,385subscribers
-4,205 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002469393323 |
|---|---|
| Type | Channel |
| Username | @WixmoreVpn |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 October 2026 |
| Measurements held | 51 |
| Confirmed unchanged | 1 time, most recently 26 October 2026 |
| On Telegram | t.me/WixmoreVpn |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 26 Oct 2026, 21:37 | 23,385 | -24 |
| 25 Oct 2026, 22:36 | 23,409 | -29 |
| 24 Oct 2026, 21:06 | 23,438 | -32 |
| 23 Oct 2026, 20:47 | 23,470 | -40 |
| 22 Oct 2026, 17:51 | 23,510 | -62 |
| 21 Oct 2026, 10:16 | 23,572 | -28 |
| 20 Oct 2026, 05:56 | 23,600 | -28 |
| 19 Oct 2026, 03:55 | 23,628 | -48 |
| 18 Oct 2026, 04:40 | 23,676 | -55 |
| 17 Oct 2026, 02:17 | 23,731 | -39 |
| 16 Oct 2026, 05:27 | 23,770 | -25 |
| 15 Oct 2026, 05:37 | 23,795 | -19 |
| 14 Oct 2026, 03:01 | 23,814 | -79 |
| 11 Oct 2026, 15:20 | 23,893 | -111 |
| 7 Oct 2026, 05:36 | 24,004 | -155 |
| 2 Oct 2026, 12:02 | 24,159 | -1,009 |
| 18 Sept 2026, 13:38 | 25,168 | -497 |
| 16 Sept 2026, 03:38 | 25,665 | -251 |
| 14 Sept 2026, 10:19 | 25,916 | -88 |
| 12 Sept 2026, 20:19 | 26,004 | first reading |
36 posts held, back to 18 May 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 105 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 22 October 2026 |
|---|---|
| Posts held | 36 (18 May 2026 – 22 October 2026) |
| Views total | 4,847 |
| Reactions total | 70 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Oct 2026, 13:17 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.
443 reactions across 36 posts, in 9 distinct kinds. The most used accounts for 64.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 287 | 64.8% | |
| 🔥 | 49 | 11.1% | |
| 👍 | 35 | 7.90% | |
| 🙏 | 27 | 6.09% | |
| 🥰 | 22 | 4.97% | |
| 👌 | 10 | 2.26% | |
| ⚡ | 8 | 1.81% | |
| 🕊 | 3 | 0.677% | |
| 😍 | 2 | 0.451% |
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 36 of the 36 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 443 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 18 May 2026 to 22 October 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.
🤔 به علت مشکلاتفنی از سمت ارتباطاتزیرساخت اینترنت دیتاسنترپرواز قطع شده بود و کانفیگ های حجمی نیز قطع شده بودند، طی اعلامیه دیتاسنتر مشکل رفع گردیده است.
❤7
🔐 فیلترشکن V2ray 🛡 همراه تست ✅سرعت بینظیر 🔑 بدون ضریب 🧭 اتصال با تمامی اینترنت ها 🙋 بدون محدودیت کاربر 🔔 بدون محدودیت زمانی 🌐 دارای لینک ساب 💎 تحویل آنی 🚨لیست تعرفه کانفیگ هامون 0️⃣1️⃣ گیگ 90.000 💸 0️⃣2️⃣ گیگ 180.000 💸 0️⃣3️⃣ گیگ 270.000 💸 0️⃣5️⃣ گیگ 450.000 💸 0️⃣0️⃣1️⃣ گیگ 800.000 💸 👑 قبل از خرید نهایی نیز می توانید با دریافت کانفیگ تست رضایت خود را از سرویس ما کسب کنید. 🤖 همین حالا از ربات اقدام ب…
❤3
💸 قیمت کانفیگ های ملی به گیگی 5,000 تومان کاهش پیدا کرد. 🤖 همین حالا از ربات اقدام به خرید کنید: • @MelliConfigBot
❤5
⚡️ بروزرسانی جدید انجام شد! 🔺 اضافه شدن دو سرور به کانفیگ های ملی و افزایش سرعت کانفیگ ها 🔺 تغییر دیزاین لینک ساب 🔺 بهبود کیفیت پنل 🔺 بهبود سرعت ربات 🔺 نشان دادن تمامی لینک کانفیگ ها در ربات حتی کانفیگ های نامحدود ‼️ همچنین فروش نامحدود تا اطلاع ثانوی بسته است، افرادی هم که از قبل تهیه کرده اند و به دلیل اختلال کلودفلر قادر به باز کردن لینک ساب خود نیستند، می توانند لینک های جدید خود را در ربات ببینند. 🤖 همین حالا…
❤6🙏4
🔴 پروتکل کانفیگ های نامحدود به کل عوض شد، با ریفرش کردن لینک ساب خود می توانید کانفیگ های جدید را که بر بستر کلودفلر هستند مشاهده و بر اساس میزان تاخیر آنها را انتخاب کنید. 🤔 به طور مرتب سعی میکنیم سرور های متفاوتی قرار دهیم تا برای هر اوپراتور حداقل یک سرور مناسب باشد. ❗️ اگر که با ریفرش کردن لینک ساب تمام سرور ها به شما پینگ نداد، با پشتیبانی در تماس باشید: • @WixmoreVpnSup
❤5
⚡️ کانفیگ های نامحدود نیز در دسترس قرار گرفت، منتها در ربات از طریق دکمه "کانفیگ های من" و انتخاب کانفیگ مورد نظر، لینک ساب جدید خود را بردارید و از طریق آن کانفیگ را بروزرسانی کنید. 🤔 همچنین 3 روز به کانفیگ های نامحدود به پاس قطعی های به وجود آمده که مربوط به ما هم نیز نبود و از طرف زیرساخت بود، اضافه شد. ❗️ با توجه به سختگیری های زیرساخت، ممکن است دوباره این پروتکل محدود شود که ناچار به تغییر موقتی روش کلودفلر هس…
❤5🙏1
☄️ کانفیگ های حجمی در دسترس قرار گرفت، به زودی کانفیگ های نامحدود نیست متصل می شود، همچنین پس از رفع مشکل، به کاربران ۳ روز اضافه خواهد شد.
❤9🔥1
🔴 قطعی به وجود آمده به دلیل محدود شدن سرور ها از سمت زیرساخت هست، در تلاشیم که مجدد اتصال را برقرار کنیم!
👍11
⁉️ اگر کانفیگ نامحدود شما متصل نشد، لینک ساب خود را دوباره بروزرسانی کنید. دامنه های جدیدی جهت اتصال اضافه شد.
❤4⚡2🔥1
🔴 قطعی به وجود آمده به دلیل محدود شدن سرور ها از سمت زیرساخت بود. 🤔 لینک ساب کانفیگ های نامحدود خود را بروزرسانی کنید. کانفیگ های حجمی بدون مشکل متصل شدند.
❤5🔥1
🔴 مشکل کانفیگ های حجمی طی اطلاعیه دیتاسنتر رفع شد. 🤖 همین حالا از ربات اقدام به خرید کنید: • @MelliConfigBot
❤6
🔴 به علت مشکلات فنی از سمت ارتباطات زیرساخت اینترنت دیتاسنتر پرواز قطع شده است، منتظر اطلاعیه دیتاسنتر جهت برقراری مجدد ارتباط هستیم. 🤔 کانفیگ های نامحدود بدون مشکل روشن هستند، تغییری ایجاد نکنید.
❤6👍2🔥1
Showing the 12 most recent of 36 posts we hold for @WixmoreVpn. 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.
@WixmoreVpn edited 3 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.
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.
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.
Named by 1 registered channel — 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Wixmore VPN | فیلترشکن ویکسمور” (@WixmoreVpn), 23,385 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/WixmoreVpn.
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.