Telegram RegisterThe public register of Telegram

Channel

ASANET |‌ VPN

@ASANET1

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

1,682subscribers

-9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002365310712
TypeChannel
Username@ASANET1
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/ASANET1

Topic

Technology — 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 86% 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.

Observations

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@JoomoongVPN/38310 Jun 2026, 19:38 UTC@ASANET1/260 · this entry10 Jun 2026, 19:38 UTC1.00under a minute
@JoomoongVPN/38616 Jun 2026, 15:18 UTC@ASANET1/263 · this entry16 Jun 2026, 15:18 UTC1.00under a minute
@JoomoongVPN/40723 Jul 2026, 09:58 UTC@ASANET1/284 · this entry23 Jul 2026, 09:58 UTC1.00under a minute
@ASANET1/285 · this entry2 Aug 2026, 21:35 UTC@JoomoongVPN/4082 Aug 2026, 21:35 UTC1.00under a minute
@JoomoongVPN/3981 Jul 2026, 15:51 UTC@ASANET1/270 · this entry1 Jul 2026, 16:01 UTC0.9810 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@JoomoongVPN5 (5/5 hand-verifiable sample passed)1.00under a minute@JoomoongVPN (41)

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 4 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 16 comparable posts for this entry, running 2 June 2026 to 2 August 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @ASANET1 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

Also posting the same content

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.

Growth

1,6821,6911,686.56 August 2026 — 1,691 subscribers6 August 2026 — 1,691 subscribers9 August 2026 — 1,685 subscribers12 August 2026 — 1,682 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -9. 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 1,681–1,692 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:241,682-3
9 Aug 2026, 20:311,685-6
6 Aug 2026, 07:161,691no change
6 Aug 2026, 04:021,691first reading

Engagement

20 posts held, back to 2 June 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
26.7%
avg views ÷ 1,682 subscribers
Avg views / post
449
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
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 2 August 2026
Posts held20 (2 June 20262 August 2026)
Views total1,797
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:43 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.

Recent posts

2 Aug 2026, 22:54 UTC253 viewsread 7 August 2026
Photo

✔️ وضعیت سرویس در حین شدیدترین اختلال اینترنت طی یک ماه اخیر:

2 Aug 2026, 21:35 UTC280 viewsread 7 August 2026

⚠️ اختلال گسترده در اپراتورهای اینترنت! 🔔 طبق گزارشات به دست رسیده، روتینگ زیرساخت برخی اپراتورها دچار تغییراتی شده؛ ترافیک ایران از مسیر آذربایجان و شرکت دلتا عبور می‌کرده که در حال حاضر به آلمان منتقل شده و حتی برخی اپراتورها مستقیما و بدون فیلتر آیپی آلمان دارن!

23 Jul 2026, 09:58 UTC568 viewsread 7 August 2026

🔄 لینک اشتراکتونو آپدیت کنید! ‏🇮🇷 لوکیشن ایران اضافه شد که علاوه بر دسترسی پرسرعت به سایت‌های داخلی، برای تلگرام، اینستاگرام، یوتیوب، گیم و سایر سرویس‌های فیلترشده نیز عملکردی سریع و پایدار ارائه می‌دهد. ➕ پهنای باند سرویس‌های ⅓ بها ارتقا داده شد و اکنون روی تمامی اپراتورها با سرعت بالا و تعرفه یک‌سوم ‌بها فعال هستند. ‏🇹🇷 ترکیه گیمینگ هم با پینگ و جیتر بی‌نظیر اضافه شد، همچنین بزودی روی هیستریا با udp نیز فعال

18 Jul 2026, 09:44 UTC696 viewsread 7 August 2026

👍 هر سوال، مشکل، پیشنهاد یا انتقادی دارید، خدمتتون هستیم: 💬 @AsanetAdmin

13 Jul 2026, 21:28 UTC926 viewsread 7 August 2026
Forwarded from @IRRadar

🔴 اختلال گسترده در اینترنت ثابت و همراه گزارش‌های کاربران نشان می‌دهد از ساعاتی پیش، اینترنت ثابت و همراه در نقاط مختلف کشور با اختلالات گسترده و افت محسوس کیفیت خدمات مواجه شده است. کاربران از کاهش شدید سرعت، قطعی و وصل‌های مکرر، ناپایداری اتصال، پرش آنتن در شبکه‌های تلفن همراه و اختلال در دسترسی به برخی سرویس‌ها و پلتفرم‌های اینترنتی خبر می‌دهند. 📡 @IRRadar

12 Jul 2026, 14:23 UTC877 viewsread 7 August 2026
Forwarded from @IRRadar

🔴 اختلال و افت محسوس سرعت اینترنت؛ گزارش‌های کاربران از افزایش مشکلات ارتباطی گزارش‌های کاربران حاکی از آن است که از ساعاتی گذشته، اینترنت در برخی نقاط کشور با اختلال و کاهش سرعت همراه شده و دسترسی به برخی سرویس‌های آنلاین با مشکل مواجه است. هم‌زمان، بسیاری از کاربران از اختلال در دسترسی به برخی پلتفرم‌ها از جمله ChatGPT خبر می‌دهند؛ به‌طوری که ورود به سرویس، ارسال درخواست و دریافت پاسخ با کندی یا خطا همراه شده است

5 Jul 2026, 07:47 UTC911 viewsread 7 August 2026

✔️ امکان ارائه پنل همکاری اختصاصی با کیفیت و تعرفه استثنایی مهیا شد! 💬 جهت اطلاعات بیشتر با پشتیبانی در ارتباط باشید: 🔗 @AsanetAdmin

1 Jul 2026, 16:01 UTC≈5,960 viewsread 7 August 2026
Photo

📣 تعرفه خدمات کاهش یافت و بسته‌‌های چند ماهه هم اضافه شد! ✔️ دسترسی آسوده به سایت‌ها و پلتفرم‌های خاص و حساس از جمله جمینای 💎 کانفیگ‌های یک سوم‌بها جهت صرفه‌جویی در مصرف و هزینه‌های اینترنت شما 🚫 دور زدن تبلیغات یوتیوب، ساوندکلاد، اسپاتیفای و ... 🏓 پینگ و جیتر فوق‌العاده برای گیم، شامل چندین کانفیگ از کشورهای ترکیه، ارمنستان و امارات 📍 آیپی ثابت بیش از 30 کشور دنیا مناسب ترید 🥶 بدون محدویت در تعداد کاربر و بدو

25 Jun 2026, 13:23 UTC≈1,020 viewsread 7 August 2026

🔥🔥🔥 لینک اشتراک رایگان، مهلت استفاده تا شنبه 04/06 : https://link.gridpointgo.com/asanet/fa5e7de2d56085f6068eea0334e366ab 🛍 دریافت VPN اختصاصی با آیپی ثابت بیشتر از 20 کشور مناسب گیم و ترید از ربات: 🔗 @AsanettBot با دوستان و آشنایان به اشتراک بزارید👍 ‼️ ------- اتمام مهلت استفاده ------- ‼️

24 Jun 2026, 21:00 UTC≈1,010 viewsread 7 August 2026

✔️ دیدیم تعرفه‌ها رو که آوردیم پایین، بهتره کاری کنیم هزینه‌ی اینترنت خودتون هم کمتر بشه ! 📌 تعدادی کانفیگ جدید با ترافیک ۱/۳ بها به لینک اشتراک همه اضافه شد. 🔥 یعنی چی؟ یعنی از این به بعد وقتی با این کانفیگ‌ها 3 گیگابایت دانلود یا وبگردی می‌کنید، اپراتور (همراه اول، ایرانسل، مخابرات و ...) فقط 1 گیگابایت از بسته اینترنتتون کم میکنه! 👍 عملا هزینه‌ای که بابت خرید اینترنت به همراه اول و ایرانسل و ... می‌دید با این

24 Jun 2026, 20:09 UTC818 viewsread 7 August 2026
Photo

🔔 اطلاعیه کاهش تعرفه خدمات: 🟢 15 گیگ 135 تومان 🔴 30 گیگ 255 تومان 🔵 50 گیگ 400 تومان و ... 🛍 خرید از @AsanettBot

19 Jun 2026, 10:09 UTC941 viewsread 7 August 2026
Photo

❤️ پایِدار تا پایِ‌دار 💬 @AsanetAdmin

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

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

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

“ASANET |‌ VPN” (@ASANET1), 1,682 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ASANET1.

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.