Telegram RegisterThe public register of Telegram
Telegram profile photo for VPN ‎جومونگ | 보요아이피

Channel

VPN ‎جومونگ | 보요아이피

@JoomoongVPN

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

6,196subscribers

+674 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001611047292
TypeChannel
Username@JoomoongVPN
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/JoomoongVPN

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

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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/383 · this entry10 Jun 2026, 19:38 UTC@ASANET1/26010 Jun 2026, 19:38 UTC1.00under a minute
@JoomoongVPN/386 · this entry16 Jun 2026, 15:18 UTC@ASANET1/26316 Jun 2026, 15:18 UTC1.00under a minute
@JoomoongVPN/407 · this entry23 Jul 2026, 09:58 UTC@ASANET1/28423 Jul 2026, 09:58 UTC1.00under a minute
@ASANET1/2852 Aug 2026, 21:35 UTC@JoomoongVPN/408 · this entry2 Aug 2026, 21:35 UTC1.00under a minute
@JoomoongVPN/398 · this entry1 Jul 2026, 15:51 UTC@ASANET1/2701 Jul 2026, 16:01 UTC0.9810 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@ASANET15 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (4–1)

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 1 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 25 comparable posts for this entry, running 5 June 2026 to 26 October 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @ASANET1. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

5,5227,1066,3147 August 2026 — 5,522 subscribers7 August 2026 — 5,522 subscribers7 August 2026 — 7,035 subscribers11 August 2026 — 7,034 subscribers14 August 2026 — 7,037 subscribers17 August 2026 — 7,056 subscribers20 August 2026 — 7,083 subscribers24 August 2026 — 7,106 subscribers27 August 2026 — 6,537 subscribers29 August 2026 — 6,533 subscribers1 September 2026 — 6,539 subscribers5 September 2026 — 6,559 subscribers10 September 2026 — 6,589 subscribers13 September 2026 — 6,525 subscribers17 September 2026 — 6,435 subscribers26 September 2026 — 6,253 subscribers5 October 2026 — 6,124 subscribers11 October 2026 — 6,102 subscribers14 October 2026 — 6,100 subscribers17 October 2026 — 6,067 subscribers21 October 2026 — 6,068 subscribers24 October 2026 — 6,098 subscribers26 October 2026 — 6,119 subscribers29 October 2026 — 6,142 subscribers2 November 2026 — 6,138 subscribers5 November 2026 — 6,160 subscribers9 November 2026 — 6,196 subscribers6,1967 August 20269 November 2026
27 measurements spanning 93 days, net +674. 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 5,284–7,344 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
9 Nov 2026, 00:106,196+36
5 Nov 2026, 12:116,160+22
2 Nov 2026, 09:556,138-4
29 Oct 2026, 23:296,142+23
26 Oct 2026, 16:056,119+21
24 Oct 2026, 00:366,098+30
21 Oct 2026, 00:206,068+1
17 Oct 2026, 17:156,067-33
14 Oct 2026, 11:406,100-2
11 Oct 2026, 00:006,102-22
5 Oct 2026, 01:216,124-129
26 Sept 2026, 04:216,253-182
17 Sept 2026, 15:576,435-90
13 Sept 2026, 20:366,525-64
10 Sept 2026, 10:206,589+30
5 Sept 2026, 03:226,559+20
1 Sept 2026, 19:346,539+6
29 Aug 2026, 21:146,533-4
27 Aug 2026, 02:096,537-569
24 Aug 2026, 10:537,106first reading

Engagement

32 posts held, back to 5 June 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 18 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
41.0%
avg views ÷ 6,196 subscribers
Avg views / post
2,540
3 posts measured
Reaction rate
0.866%
reactions ÷ views · ER floor
Posts in window
3
of 32 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 26 October 2026
Posts held32 (5 June 2026 – 26 October 2026)
Views total7,620
Reactions total66
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 16:49 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

Video runtime
1m 37s
Average length
1m 37s

Measured directly from 1 video 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

161 reactions across 10 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤161100.0%

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

Measured over the 32 most recent posts we hold, published 5 June 2026 to 26 October 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 3 posts held from the last 30 days (100.0%) 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).

26 Oct 2026, 19:31 UTC≈3,250 views24 reactionsread 6 November 2026

⚠️ کلاهِ گشادی به اسم «فیلترشکن نامحدود!» ‌❓ بذارید یه نکته فنی رو خیلی شفاف بهتون بگم: زیرساخت سرویس‌هایی که به اسم «حجم نامحدود» بهتون می‌فروشن، دقیقاً همون کانفیگ‌های رایگانیه که توی سطح اینترنت ریخته! 🚨 وقتی شما بابت یه سرویس هزینه می‌کنید، منطقاً باید کیفیت و زیرساختش با یه سرویس رایگان فرق داشته باشه. اما تفاوت اصلی کجاست؟ ✔️سرویس‌های تانل (حجمی): توی این سرویس، دیتاسنترها هزینه زیرساخت سرورها رو بر اساس گیگ…

❤24

24 Oct 2026, 16:32 UTC≈1,700 views18 reactionsread 6 November 2026
Photo

‏⁧ 🆕 26 کشور جدید اضافه شد! 📍 190 لوکیشن فعال در 120 کشور دنیا ‌‏ ⁧🆓 تست رایگان از ربات: 🛡 @JoomoongBot پُز نیست، سَبکِ کارِمونِه.

❤18

19 Oct 2026, 20:44 UTC≈2,670 views24 reactionsread 6 November 2026

⁉️ وضعیت کانفیگ‌های نیم‌بها به کجا رسید؟ 💬 با توجه به تغییرات و سیاست‌های اخیر اعمال‌شده از سوی اپراتورهای اینترنت (موبایل و ثابت)، ساختار محاسبه ترافیک دگرگون شده و امکان ارائه ترافیک نیم‌بهای سراسری و پایدار از دسترس خارج شده؛ در حال حاضر ترافیک نیم‌بها صرفا برای پلتفرم‌های داخلی (نظیر آپارات، فیلیمو و...) فعال است. ⁉️ پس چطور برخی فروشگاه‌ها همچنان کانفیگ نیم‌بها ارائه می‌دهند؟ 💬 محاسبه نیم‌بهای ترافیک در حال ح…

❤24

11 Oct 2026, 14:40 UTC≈3,750 views28 reactionsread 6 November 2026

‼️ طبق شواهد موجود، اگر طی جنگ احتمالی، اینترنت بخواد قطع بشه، اتصالتون به مراتب سخت تر خواهد بود، اگر اطلاعات مهمی دارید حتما بکاپ آفلاین ازش تهیه کنید. امیدوارم روایت چیز دیگه‌ای باشه...

❤28

11 Oct 2026, 14:26 UTC≈3,420 views8 reactionsread 6 November 2026

🚨 از ساعت 17:30 کل دیتاسنتر آسیاتک، از دسترس خارج شده! 🔔 در حال انتقال هستیم صبوری کنید... ✔️ اتصال مجدد برقرار شد

❤8

5 Oct 2026, 21:10 UTC≈4,460 viewsread 6 November 2026

🔴 اختلال گسترده در اینترنت بین‌الملل ‌ ‌

3 Oct 2026, 11:23 UTC≈4,140 views41 reactionsread 6 November 2026
Photo

🔔 از روز اول تمام تلاش‌مون این بوده که با وجود هزینه‌های سرسام‌آور ارزی که صرف زیرساخت سرویسمون می‌شه، تا جایی که در توان داریم تعرفه سرویس رو ثابت نگه داریم که فشاری به شما عزیزان نیاد. 🔍 آخرین بار قیمت‌ها رو زمانی فیکس کرده بودیم که دلار روی کانال 150 هزار تومان بود؛ اما حالا در آستانه دوبرابر شدن هست و تعرفه سرویس ما همچنان ثابت مونده. ➕ با این حال، خواستیم پیشاپیش و قبل از اعمال تغییرات بهتون اطلاع بدیم که غافل…

❤41

12 Sept 2026, 13:49 UTC≈8,280 views15 reactionsread 6 November 2026

🔥🔥🔥 با 69 لوکیشن فعال؛ در هر پوزیشنی که می‌خوای به اینترنت وصل شو! 🌍 اروپا (Europe): ‌‎🇩🇪 آلمان (Frankfurt / Düsseldorf / Berlin) ‎🇸🇪 سوئد (Sweden)‎ ‎🇮🇹 ایتالیا (Italy) ‎🇳🇱 هلند (Netherlands) ‎🇬🇧 بریتانیا (United Kingdom) ‎🇹🇷 ترکیه (Turkey) ‎🇵🇱 لهستان (Poland) ‎🇺🇦 اوکراین (Ukraine) ‎🇫🇮 فنلاند (Finland) ‎🇧🇪 بلژیک (Belgium) ‎🇨🇿 جمهوری چک (Czech Republic) ‎🇱🇺 لوکزامبورگ (Luxembourg) ‎🇫🇷 فرانسه (France) ‎🇷🇴 رومانی (Rom…

❤15

10 Sept 2026, 21:04 UTC≈4,060 views0 reactionsread 6 November 2026
Video

💡 آموزش رفع مشکل گوگل فلو و برخی سرویس‌های گوگل مطالعه جزئیات از کانال زومیت👇 🔗 t.me/thezoomit/101168 منبع ویدیو👇 🔗 instagram.com/reel/DdB_ShdMlQE

10 Sept 2026, 10:34 UTC≈7,030 views1 reactionsread 6 November 2026
Photo

⚠️ هشدار امنیتی جدی: اطلاعات بانکی کاربران Jump Jump لو رفت! 📣 دیتابیس کاربران فیلترشکن JumpJump در یکی از فروم‌های دارک‌وب منتشر شد؛ منتشرکننده با شناسه leakhunter گفته این مجموعه شامل اطلاعات شخصی و حساسی مثل اطلاعات پرداخت، اطلاعات کارت‌های بانکی، تراکنش‌ها، موجودی، لاگ فعالیت کاربران و اطلاعات دستگاه‌ها از جمله مخاطبین هست. ‼️ نگهداری زیرساخت هر فیلترشکنی، ماهیانه هزینه دلاری سنگینی داره از جمله هزینه سرورها، ت…

❤1

30 Aug 2026, 14:15 UTC≈4,760 views1 reactionsread 6 November 2026

‼️ #اطلاعیه_مهم ✔️ لینک اشتراکتون رو بروزرسانی کنید، مشکل برنامه Happ در بخش کامنت‌های اینستاگرام رفع شد. 🔔 جهت بهره‌مندی از آپدیت اخیر، حتما باید از نسخه آخر برنامه Happ یا incy استفاده کنید؛ سایر برنامه‌ها مورد تایید ما نیست!

❤1

10 Aug 2026, 17:16 UTC≈9,510 viewsread 6 November 2026
Photo

📣 طبق گزارش تعداد کمی از کاربران، برنامه Happ با برخی گوشی‌ها سازگار نیست، اگر مشکل کندی روی Happ دارید‌، می‌تونید از برنامه جدید incy استفاده کنید: ⬇️ لینک دانلود نسخه اندروید: 📱 https://play.google.com/store/apps/details?id=llc.itdev.incy ‎ ⬇️ لینک دانلود نسخه آیفون: 🍏 https://apps.apple.com/us/app/incy/id6756943388

Showing the 12 most recent of 32 posts we hold for @JoomoongVPN. 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 recorded as deleted after publishing

We recorded 1 post on @JoomoongVPN as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
4 November 2026
Most recent seen missing
4 November 2026
Median time before seen missing
3 months
Seen missing in the last 30 days
1

Forward network

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

“VPN ‎جومونگ | 보요아이피” (@JoomoongVPN), 6,196 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/JoomoongVPN.

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.