Telegram RegisterThe public register of Telegram
Telegram profile photo for madys_vpn

Channel

madys_vpn

@madys_vpn

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,154subscribers

+94 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001530954395
TypeChannel
Username@madys_vpn
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/madys_vpn

Topic

Other / unclassifiable — 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 15 August 2026 and assigned it the closest of 31 fixed categories, at 48% 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

2,0552,2012,1287 August 2026 — 2,060 subscribers7 August 2026 — 2,060 subscribers7 August 2026 — 2,062 subscribers10 August 2026 — 2,055 subscribers14 August 2026 — 2,201 subscribers17 August 2026 — 2,191 subscribers20 August 2026 — 2,186 subscribers24 August 2026 — 2,166 subscribers27 August 2026 — 2,154 subscribers2,1547 August 202627 August 2026
9 measurements spanning 20 days, net +94. 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 2,033–2,223 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 01:342,154-12
24 Aug 2026, 10:042,166-20
20 Aug 2026, 19:032,186-5
17 Aug 2026, 17:262,191-10
14 Aug 2026, 03:062,201+146
10 Aug 2026, 13:582,055-7
7 Aug 2026, 15:132,062+2
7 Aug 2026, 05:312,060no change
7 Aug 2026, 05:232,060first reading

Engagement

20 posts held, back to 13 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
34.6%
avg views ÷ 2,154 subscribers
Avg views / post
746
6 posts measured
Reaction rate
0.916%
reactions ÷ views · ER floor
Posts in window
6
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
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (13 July 20267 August 2026)
Views total4,476
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:01 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

88 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 85.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7585.2%
👍44.55%
🔥44.55%
👎33.41%
❤‍🔥11.14%
😍11.14%

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 20 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 88reactions 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 13 July 2026 to 7 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.

Recent posts

7 Aug 2026, 16:56 UTC20 views2 reactionsread 7 August 2026

📢 اطلاعیه مهم تمامی کاربرانی که از مجموعه ما سرویس دارند، لطفاً یک بار لینک اشتراک خود را به‌صورت کامل آپدیت (Update Subscription) بزنند و سپس به کانفیگ‌های جدید متصل شوند. ✅این کار باعث می‌شود آخرین تغییرات و کانفیگ‌های جدید برای شما دریافت شود و سرویس بدون مشکل و با بهترین کیفیت در اختیارتان قرار بگیرد. ممنون از همراهی شما ❤

2

5 Aug 2026, 20:48 UTC585 views7 reactionsread 7 August 2026
Photo

👊🏃‍♂️چه سرعتی چه پینگی 👽 #pasha

6❤‍🔥1

4 Aug 2026, 10:09 UTC772 views6 reactionsread 7 August 2026
Photo

👍👍یکی از امکانات جدیدی که به پنل اضافه کردم اینه که شما وقتی داخل بات خرید میزنید لینک هوشمندو بهتون داد روش بزنید کپی میشه داخل خود بات یا هر جایی که دوس داشتید پیست کنید بعد روش کلیک کنید چه با فیلتر شکن چه بدون فیلتر شکن وارد سایت پنل میشید اسکرول کنید بیاید پایین تا به قسمت افزودن سریع به اپلیکیشن برسید اینجا هر کدوم از اپا رو داشتید بزنید تا کل کانفیگاتون مستقیم خودکار برن داخل برنامه برید عشق کنید 😎❤️ 📱@madys

5🔥1

2 Aug 2026, 18:11 UTC919 views13 reactionsread 7 August 2026

لوکیشن(هلند🇳🇱) اضافه کنیم؟ ریکشناتون کم شده انرژی نمیگیریم 😭که بخوایم خدمات و لوکیشنایی بیشتری اضافه کنیم انرژی بدید ببینم چند چندیم🥰 #pasha

9🔥2👍1👎1

31 Jul 2026, 18:50 UTC≈1,130 views7 reactionsread 7 August 2026

نامحدود تا زمانی که فیلتر بشه🕤 ✔اکثر اپراتور ها 🛜🛜🛜🛜 vless://[email protected]:443?security=reality&encryption=none&pbk=M9_R2DX7bxoMJpkF4RcyJ0oJ8ZuGsxWrjuREKi6Ol0w&headerType=none&fp=firefox&type=tcp&flow=xtls-rprx-vision&sni=apple.com#%40Shh_Proxy-New%C2%B9 ss://Y2hhY2hhMjAtaWV0Zi1wb2x5MTMwNTpyWWZpNGNRM3o3enRzN0JPNC1ZOV9B@188.41.249.20:1080#%40Shh_Proxy-New%C2%B2 ss://Y2hhY2hhMjA

7

30 Jul 2026, 10:48 UTC≈1,050 views6 reactionsread 7 August 2026

🏙🏙سرویس نامحدود (مصرف منصفانه که 150گیگه) با تعداد کاربر نامحدود به بات اضافه شد میتونید خرید بزنید ❤️ 🛒🤖خرید از ربات: 🔤 @Madys_vpnbot

5👎1

26 Jul 2026, 19:58 UTC≈1,210 views5 reactionsread 7 August 2026

دوستانی که قبلا خرید کردن و مشکل چک کردن حجمو دارن و وقتی روی سرویس خودشون میزنن با خطا مواجه میشن دلیلش تغییر پنله بات رفته روی پنل جدید و در خرید های بعدیتون میتونید حجمو از داخل بات چک کنید برای کسانی هنوز حجم در پنل قبلی دارند اگه لینک هوشمند یا همون لینک سابو در هر برنامه ای (ویتوری، ویتوباکس happ و... ) بزنید حجمو داخل همون برنامه نشون میده رو خود لینک هم بزنید وارد یه سایت میشد و میتونید حجم مانده و روز رو مش

4👎1

26 Jul 2026, 15:47 UTC≈1,280 views7 reactionsread 7 August 2026

🏙پاشا یه سریا دارن ارزون تر میدن دلیلش چیه؟ منم میتونم گیگی 1000تومنی براتون موجود کنم 100گیگ 100هزار تومن با سرعت بالا ولی هیچ امنیتی ندارن cpu گوشیتون درگیر میشه باتری گوشیتونو زود خالی میکنه و گوشیتون داغ میکنه و اطلاعات از گوشیتون میکشه بیرون یه سری دیتاسنتر هستن کارشون همینه ارزون میدن و در ازای اون اطلاعات میکشن بیرون و برای گوشی و حتی سیستم مضر هستن برای من امنیت مهمترین عامل و اولیته هزینه بیشتر میکنم تا امن

7

25 Jul 2026, 10:22 UTC≈25,500 views5 reactionsread 7 August 2026
Photo

👑به نام خداوند ایران زمین 🏙🏙لیست جدید قیمت ها از راه رسید ⚡️⚡️مولتی لوکیشن 🇫🇮🇹🇷🇺🇸🇩🇪 ☑️ اتصال پایدار و پرسرعت ☑️ مناسب گیم، استریم و استفاده روزمره ☑️ بدون قطعی آزاردهنده ☑️ پشتیبانی سریع و پاسخگو 🧪🧪هیچوقت قبل تست خرید نکن اول تست کن بعد با خیال راحت خرید بزن 🔹 20گیــگ 120,000 💰 🔹 30گیــگ 180,000 💰 🔹 40گیــگ 240,000 💰 🔹 50گیــگ 300,000 💰 🔹 60گیــگ 360,000 💰 🔹 80گیــگ 450,000 💰 🔹 100گیگ

4👍1

24 Jul 2026, 09:19 UTC≈1,360 views3 reactionsread 7 August 2026

🔹سلام و عرض ادب خدمت همراهان عزیز madys vpn 🌹 ➕به اطلاع شما عزیزان می‌رسانیم، سرویس‌های قدیمی مولتی پس از اتمام اعتبار، قابلیت تمدید نخواهند داشت. به همین منظور، پنل جدید، پایدار و بدون باگ به ربات متصل شده و آماده ارائه خدمات است. ✅ پنل جدید با حداکثر کیفیت و پایداری در دسترس بوده و از طریق ربات قابل خرید و فعال‌سازی می‌باشد. ⌛ کاربرانی که قصد تمدید سرویس خود را دارند، می‌توانند پیش از پایان اعتبار سرویس فعلی، آن

1👍1😍1

22 Jul 2026, 00:54 UTC≈1,270 views1 reactionsread 7 August 2026

https://t.me/proxy?server=nab.goooalir.co.uk&port=8443&secret=dd104462821249bd7ac519130220c25d09 https://t.me/proxy?server=PAyDaR.goooalir.co.uk&port=8443&secret=dd104462821249bd7ac519130220c25d09 https://t.me/proxy?server=FOR-IRAN.goooalir.co.uk&port=8443&secret=dd104462821249bd7ac519130220c25d09 https://t.me/proxy?server=soheil.goooalir.co.uk&port=8443&secret=dd104462821249bd7ac519130220c25d09 @madys_vpn

👍1

19 Jul 2026, 10:29 UTC≈7,660 views5 reactionsread 7 August 2026
Photo

🔋🔋وضعیت پینگ سرویس هامون ادعا نمیکنیم عمل میکنیم 💀 ✈️دریافت اطلاعات بیشتر

5

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

Citation-graph rank

Citation-graph rank — 968,023 of 1,622,561entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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

“madys_vpn” (@madys_vpn), 2,154 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/madys_vpn.

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.