Channel
@m00nvpn
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
543subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001729423507 |
|---|---|
| Type | Channel |
| Username | @m00nvpn |
| Description | فیلترشکن اختصاصی اکانت تست رایگان Moon VPN لطفاً صبور باشید به نوبت به پیام همه دوستان پاسخ داده میشود @MoonVpn14 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/m00nvpn |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @moonvpn2/2611 Nov 2024, 11:11 UTC | @m00nvpn/326 · this entry1 Nov 2024, 11:11 UTC | 1.00 | under a minute |
| @moonvpn2/26311 Nov 2024, 15:14 UTC | @m00nvpn/328 · this entry11 Nov 2024, 15:14 UTC | 1.00 | under a minute |
| @moonvpn2/2694 Dec 2024, 19:21 UTC | @m00nvpn/336 · this entry4 Dec 2024, 19:21 UTC | 1.00 | under a minute |
| @moonvpn2/27219 Jun 2025, 17:47 UTC | @m00nvpn/340 · this entry19 Jun 2025, 17:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @moonvpn2 | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–3) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 1 November 2024 to 19 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @m00nvpn — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 18:18 | 543 | no change |
| 6 Aug 2026, 05:04 | 543 | first reading |
20 posts held, back to 1 November 2024 — 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 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 19 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 August 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.
🚀ما مثل همیشه پر سرعت متصلیم برای خرید به ایدی زیر مراجعه کنید 🟢 ⭐️ اگه برات مهمه ارتباطت با دنیای آنلاین قطع نشه، الان وقتشه یه اتصال مطمئن برای خودت داشته👌 همراه با پشتیبانی ۲۴ ساعته👩💻 👤 خرید و تحویل آنی: @tigersupp0rt در خدمتتون هستم❤️
Signed Moon VPN
♻️💖سرورها در حالت پایدار قرار گرفتن فروش باز شد 🎁😍
لطفاً برای خرید اشتراک به این کانال پیام بدین
📢 اطلاعیه خوشبختانه سرورها مجدداً در دسترس قرار گرفتهاند و سرویس به حالت پایدار بازگشته است. ابتدا بابت قطعیها و زمانی که در این مدت از دست رفت، صمیمانه از شما عذرخواهی میکنیم. 🙏 دلیل طولانی شدن فرایند این بود که اینبار بهجای اجاره سرور، تصمیم گرفتیم زیرساخت اختصاصی خودمان را تهیه و راهاندازی کنیم. بخش هماهنگی و مذاکره با دیتاسنترها زمانبر شد، اما نتیجه این انتقال، پایداری بسیار بیشتر و جلوگیری از مشکلات مشابه…
#اطلاعیه 🏆کلیه سرورا روی تمامی نت ها جوابگو هست. 🚀سرور اختصاصی برای هر کاربر حجم ترافیک منصفانه ✅قابل استفاده در : ویندوز ،اندروید ، ios سازگار با تمامی سرویس دهنده های اینترنت دارای IP ثابت و بدون کندی 🏆🚀مناسب انواع بازی ها ، وب گردی ، دانلود و اپلود و غیره .. تهیه سرویس : @moonvpn14
خرید باز شد کانفیگ کیفیت خوب و سرعت عالی بدون قطعی برای تمامی نت ها🏆 مثل همیشه در خدمت شما هستیم پیوی ها به نوبت از پایین پاسخ خواهیم داد🥇🥇 ممنونیم از همراهی شما @moonvpn14
سلام وقت بخیر با عرض پوزش خدمت کاربران گرامی برای اختلال به وجود آمده مشکل کانفیگ ها رفع شده در صورت تمایل به خرید در خدمت همراهان همیشگی هستیم
ارتباط اینترنت کل کشور و کل دیتاسنترهای ایرانی به طور کامل قطع شده و تنها 3 درصد از کل کشور به اینترنت دسترسی داشت. • مشکل به طور کامل برطرف نشده و در حال بررسی هستیم، لطفا تا حل شدن مشکل به پشتیبانی پیام ندید تا مشکل به طور کامل برطرف شه. • جواب دیتاسنتر ایرانی: به دلیل اختلالات موجود، ارتباط بینالمللی دیتاسنترها را از دست دادهایم. در حال پیگیری این موضوع از پروایدرهای بالادستی هستیم.
رضایت مشتری عزیزما ♥️
❤️
رضایت مشتری عزیزما ♥️
⭕️⭕️ فروش فیلتر شکن پرسرعت V2ray 🛡🔑 🔹 تــســت رایــگــان ✅ 🔻سرعت در حد موشک 🚀(سرورهای اختصاصی) 🔻ایپی ثابت برای اینستا/ترید/گیم 🔻بدون محدودیت کاربر 🔷 🔻پشتیبانی تا اخرین روز اشتراک🟢 🔻قابل اجرا روی تمامی سیستم عامل ها 🔄 بازگشت وجه در صورت قطعی و نارضایتی ✅
Showing the 12 most recent of 20 posts we hold for @m00nvpn. 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 — 878,770 of 1,151,006entries 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.
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 4 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.
@m00nvpn named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“Moon VPN” (@m00nvpn), 543 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/m00nvpn.
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.