Telegram RegisterThe public register of Telegram
Telegram profile photo for MuLtI VPN | PROXY مولتی وی پی ان | پروکسی

Channel

MuLtI VPN | PROXY مولتی وی پی ان | پروکسی

@multivpnsup

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

15,138subscribers

-3,118 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003149134301
TypeChannel
Username@multivpnsup
Descriptionسلام 🤍 ما تازه شروع کردیم، اما با یه هدف مشخص اومدیم: اینکه مردم عزیز کشور همیشه وصل بمونن، بدون دردسر و قطعی. هنوز اول راهیم، ولی با تمام توان داریم تلاش می‌کنیم بهترین سرویس رو ارائه بدیم و کنار شما باشیم Support : @Multivpnsuport Bot : @multiwvpnbot
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 November 2026
Measurements held69
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/multivpnsup

Topic

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 the other topics.

Growth

15,13818,25616,6976 August 202618 November 2026
69 measurements spanning 105 days, net -3,118. 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 14,670–18,724 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 69
Measured (UTC)SubscribersChange
18 Nov 2026, 15:5815,138-57
15 Nov 2026, 16:4615,195-96
12 Nov 2026, 10:5815,291-54
10 Nov 2026, 11:5015,345-26
9 Nov 2026, 01:2815,371-38
7 Nov 2026, 19:0715,409-22
6 Nov 2026, 14:0615,431-18
5 Nov 2026, 17:3015,449-17
4 Nov 2026, 15:4515,466-9
3 Nov 2026, 18:4715,475-15
2 Nov 2026, 17:4015,490-23
1 Nov 2026, 17:0515,513-23
31 Oct 2026, 15:4615,536-18
30 Oct 2026, 16:3615,554-27
29 Oct 2026, 16:0915,581-21
28 Oct 2026, 13:3615,602-27
27 Oct 2026, 13:1415,629-21
26 Oct 2026, 10:4515,650-26
25 Oct 2026, 12:4415,676-36
24 Oct 2026, 13:4815,712first reading

Engagement

79 posts held, back to 8 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 90 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.42%
avg views ÷ 15,138 subscribers
Avg views / post
973
17 posts measured
Reaction rate
0.277%
reactions ÷ views · ER floor
Posts in window
17
of 79 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. It is computed over the 10 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held79 (8 July 2026 – 15 November 2026)
Views total16,533
Reactions total25
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Nov 2026, 09:06 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.

What this channel posts

Photos
300
Videos
11
Links
189

Lifetime counters from Telegram’s own channel header, read 20 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 02s
Average length
16s

Measured directly from 4 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.

Reaction mix

345 reactions across 65 posts, in 8 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍌12335.7%
❤6819.7%
🤣6819.7%
🔥298.41%
👍257.25%
❤‍🔥164.64%
🥰92.61%
🌭72.03%

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 67 of the 79 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 345 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 79 most recent posts we hold, published 8 July 2026 to 15 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 17 posts held from the last 30 days (17.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 08:52 UTC390 views0 reactionsread 20 November 2026

🇧🇭🇮🇷🇺🇸بحرین: بنا بر گزارش‌ها، ایران تلاش کرد تا به سامانه راداری هشدار اولیه در جبل الدخان حمله کند. سپاه پاسداران انقلاب اسلامی ایران اعلام کرد که شش پهپاد را به سمت رادار پدافند هوایی آمریکا در پایگاه بالگردی ریفا پرتاب کرده است. 💎 کانفیگ اختصاصی 💎 @MultiVpnSuport

14 Nov 2026, 22:01 UTC437 viewsread 20 November 2026

3️⃣ ادمین روی اکانتن.🥇 خلاصه پشتیبانی ۲۴ ساعتس چه ۴ صبح سرور بخواین که ۸ صبح ما هستیم✅ خلاصه نگران قطع شدن اینترنت نباشید همین که قطع هم شد پیام بدید آنلاینیم❤️ تهیه سرور پرسرعت و بدون قطعی: @MultiVpnSuport

14 Nov 2026, 15:58 UTC464 views2 reactionsread 20 November 2026

سرور ها بدون قطعی وصل هستند✅ یه سرور مخصوص نت ملی با پرچم هلند هم اضافه شده اپدیت کنید میاد💎 این سرور با هر شرایطی وصله ضریب هم نداره🥇 جهت خرید سرویس بدون قطعی: @MultiVpnSuport

❤2

11 Nov 2026, 19:00 UTC680 views0 reactionsread 20 November 2026

🔴 طبق گفته کاربران اینترنت تو بعضی از نقاط کشور، ضعیف شده امشب و اختلال زیادی داره! جهت تهیه سرور بدون قطعی: @MultiVpnSuport

10 Nov 2026, 16:06 UTC947 viewsread 20 November 2026

فووووووووری/توئیتر بریکس: ایران شرطِ آمریکا در مورد کاهش درصد اورانیوم غنی‌سازی شده رو برای توافق قبول کرد!

8 Nov 2026, 15:51 UTC949 views1 reactionsread 20 November 2026

سرور ها متصل هستند کافیه اپدیت کنید ساب سرورتون رو.

👍1

Showing the 12 most recent of 79 posts we hold for @multivpnsup. 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.

Posts edited after publishing

@multivpnsup 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
14 August 2026
Most recent edit
16 August 2026

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 9 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.

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 18 November 2026 — this entry's latest reading, not the date you are reading this.

“MuLtI VPN | PROXY مولتی وی پی ان | پروکسی” (@multivpnsup), 15,138 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/multivpnsup.

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.