Channel
@cloudvpnn
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
2,340subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001835292583 |
|---|---|
| Type | Channel |
| Username | @cloudvpnn |
| Created | Between 1 October 2022 and 31 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/cloudvpnn |
Ecommerce storefront — 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 47% 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 |
|---|---|---|---|
| @cloudvpnn/928 · this entry1 Jun 2026, 16:59 UTC | @mimvpnn/44971 Jun 2026, 17:01 UTC | 1.00 | 2 minutes |
| @cloudvpnn/929 · this entry1 Jun 2026, 17:31 UTC | @mimvpnn/44981 Jun 2026, 17:31 UTC | 0.97 | under a minute |
| @mimvpnn/450326 Jul 2026, 05:14 UTC | @cloudvpnn/934 · this entry26 Jul 2026, 05:15 UTC | 0.96 | under a minute |
| @cloudvpnn/932 · this entry7 Jun 2026, 19:35 UTC | @mimvpnn/45017 Jun 2026, 19:35 UTC | 0.92 | under a minute |
| @mimvpnn/44928 May 2026, 06:40 UTC | @cloudvpnn/923 · this entry8 May 2026, 06:41 UTC | 0.91 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @mimvpnn | 5 (5/5 hand-verifiable sample passed) | 0.95 | under a minute | this entry (3–2) |
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 2 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 8 comparable posts for this entry, running 8 May 2026 to 26 July 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 @mimvpnn. 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 |
|---|---|---|
| 11 Aug 2026, 10:43 | 2,340 | -8 |
| 8 Aug 2026, 03:13 | 2,348 | -1 |
| 7 Aug 2026, 10:31 | 2,349 | no change |
| 7 Aug 2026, 10:29 | 2,349 | first reading |
20 posts held, back to 8 April 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 2 pagesof 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 26 July 2026 |
|---|---|
| Posts held | 20 (8 April 2026 – 26 July 2026) |
| Views total | 102 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:38 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.
🔥 کاهش قیمت های اکانت های حجمی 🔥 🔵 1 ماهه 1 کاربره حجمی ✅ 40 گیگ 110 هزار تومان ✅ 70 گیگ 170 هزار تومان ✅ 90 گیگ 220 هزار تومان ✅ 100 گیگ 270 هزار تومان 🔵 1 ماهه 2 کاربره حجمی ✅ 40 گیگ 130 هزار تومان ✅ 70 گیگ 190 هزار تومان ✅ 90 گیگ 240 هزار تومان ✅ 100 گیگ 290 هزار تومان 🔥 قیمت کانفیگ v2ray نامحدود 🔥 1⃣ یک ماه 1کاربر ✅⬅️ 340 هت 2⃣ یک ماه 2کاربر ✅⬅️ 490 هت 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 ❤️ برای استعلام قیمت پلن های بلند م…
🟡 میدونستید اکانت های ما برای هیچ اپراتوری محدودیت نداره🫶🏻 ✅ سرورهای ما با تمامى اپراتورها و واى فاى ها سرعت فضايى دارن حتی فرقی نمیکنه از چه گوشی یا سیستمی استفاده کنید😜 ايدى جهت خريد 👇🏻 @admiinvpn22 @admiinvpn22
❤️ شاهد کاهش پهنای باند اینترنت کشور هستیم!! ✅ با این وجود سرویس های ما با پایداری و سرعت عالی متصل هستن. ➕ حتما سرویس ویژه نت ملی ما رو تهیه کنید که اگر اختلال و محدودیت بیشتر شد درگیر خرید و پیدا کردن فیلترشکن مناسب نت ملی نباشید!! همراه شما هستیم❤️❤️ @admiinvpn22 @admiinvpn22
❤️ سلام وقت بخیر عزیزان ❤️ ✅ ۲۰ گیگ ... ۳۶۰ هزار تومن ✅ ۴۰ گیگ ... ۶۰۰ هزار تومن ✅ ۶۰ گیگ ... ۸۹۰ هزار تومن 🔅نامحدود تک کاربر یکماهه ... ۲ میلیون و ۴۰۰ 🔅نامحدود دو کاربر یکماهه ... ۳ میلیون و ۸۰۰
🟡 میدونستید اکانت های ما برای هیچ اپراتوری محدودیت نداره🫶🏻 ✅ سرورهای ما با تمامى اپراتورها و واى فاى ها سرعت فضايى دارن حتی فرقی نمیکنه از چه گوشی یا سیستمی استفاده کنید😜 ايدى جهت خريد 👇🏻 @admiinvpn22 @admiinvpn22
دیگه وقتش شده تمام VPNهای بیکیفیت و یکبار مصرف رو بندازین دور .. ✅ اکانتهای ما علاوه بر سرویسدهی روی قویترین و پرسرعت ترین سرورها تا آخرین روز هم گارانتی دارند. حتی الان که همه اختلال شدید دارند... تیم پشتیبانی هم ۲۴ ساعته و هفت روز هفته آنلاین و اماده برطرف کردن مشکلات و سوالات شما هستند😍 📛 خرید اکانت : @admiinvpn22
❤️ سلام وقت بخیر عزیزان ❤️ ✅ ۲۰ گیگ ... ۳۶۰ هزار تومن ✅ ۴۰ گیگ ... ۶۰۰ هزار تومن ✅ ۶۰ گیگ ... ۸۹۰ هزار تومن 🔅نامحدود تک کاربر یکماهه ... ۲ میلیون و ۴۰۰ 🔅نامحدود دو کاربر یکماهه ... ۳ میلیون و ۸۰۰
تخفیفات رو از دست ندید👌
دوستان به من پیام میدن که تخفیف لحاظ شه دوباره... تا ۱۲ امشب برای کانفیگ های v2ray تخفیف براتون اعمال میشه عزیزان🙏🌹 @admiinvpn22
دو عدد نامحدود امروز شارژ شد دوستان ، افرادی که درخواست داشتن پیام بدن بهم✅ حجمی هم موجوده عزیزان❤️
۲ عدد نامحدود دو کاربره هم موجود شد✅
۳ عدد نامحدود موجود شد دوباره عزیزان✅ الویت با واریزی @admiinvpn22
Showing the 12 most recent of 20 posts we hold for @cloudvpnn. 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 — 1,131,093 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Cloud vpn | کلود وی پی ان” (@cloudvpnn), 2,340 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/cloudvpnn.
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.