Telegram RegisterThe public register of Telegram
Telegram profile photo for Private VPN

Channel

Private VPN

@custom_config

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

14,263subscribers

-202 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001668212791
TypeChannel
Username@custom_config
Descriptionادمین تبلیغات و تبادل، مشاوره و پشتیبانی: @vip4vpn خرید: @custom_config_pro_bot
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live23 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/custom_config

Growth

14,26314,46514,3646 August 2026 — 14,465 subscribers6 August 2026 — 14,465 subscribers6 August 2026 — 14,458 subscribers7 August 2026 — 14,446 subscribers8 August 2026 — 14,432 subscribers9 August 2026 — 14,420 subscribers10 August 2026 — 14,403 subscribers11 August 2026 — 14,395 subscribers13 August 2026 — 14,387 subscribers14 August 2026 — 14,377 subscribers15 August 2026 — 14,351 subscribers17 August 2026 — 14,328 subscribers18 August 2026 — 14,316 subscribers19 August 2026 — 14,308 subscribers20 August 2026 — 14,296 subscribers21 August 2026 — 14,275 subscribers23 August 2026 — 14,263 subscribers6 August 202623 August 2026
17 measurements spanning 17 days, net -202. 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 14,233–14,495 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 01:3914,263-12
21 Aug 2026, 15:0714,275-21
20 Aug 2026, 10:3314,296-12
19 Aug 2026, 13:1614,308-8
18 Aug 2026, 12:3314,316-12
17 Aug 2026, 10:2614,328-23
15 Aug 2026, 19:5214,351-26
14 Aug 2026, 11:3514,377-10
13 Aug 2026, 00:5314,387-8
11 Aug 2026, 21:4914,395-8
10 Aug 2026, 18:3414,403-17
9 Aug 2026, 15:1214,420-12
8 Aug 2026, 11:0314,432-14
7 Aug 2026, 13:4414,446-12
6 Aug 2026, 15:2514,458-7
6 Aug 2026, 07:1514,465no change
6 Aug 2026, 07:0914,465first reading

Engagement

27 posts held, back to 17 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 32 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.8%
avg views ÷ 14,263 subscribers
Avg views / post
3,100
9 posts measured
Reaction rate
0.706%
reactions ÷ views · ER floor
Posts in window
9
of 27 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 21 August 2026
Posts held27 (17 June 202621 August 2026)
Views total27,922
Reactions total197
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Aug 2026, 01:59 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

Photos
263
Videos
10
Links
311

Lifetime counters from Telegram’s own channel header, read 23 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.

Reaction mix

902 reactions across 27 posts, in 8 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍39543.8%
👎27630.6%
🤣14315.9%
🔥272.99%
💔262.88%
🙏242.66%
🏆80.887%
😐30.333%

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

Measured over the 27 most recent posts we hold, published 17 June 2026 to 21 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

21 Aug 2026, 16:09 UTC942 views21 reactionsread 23 August 2026
Photo

وضعیت اسفناک اینترنت! تست سرعت بدون فیلترشکن گرفتم، نتیجه این بود.

💔17🤣4

16 Aug 2026, 19:49 UTC≈2,270 views33 reactionsread 23 August 2026

سلام وقت بخیر، پیش بینی من از علت اختلال‌های اینترنت در روزهای اخیر آمادگی برای قطعی احتمالی در پی افزایش ناگهانی قیمت بنزین هست!

👍27👎6

14 Aug 2026, 19:45 UTC≈2,710 views18 reactionsread 23 August 2026

عملیات با موفقیت به پایان رسید با احترام

👍9🔥6🙏2😐1

14 Aug 2026, 19:34 UTC≈2,540 views12 reactionsread 23 August 2026

سلام وقت بخیر به دلیل بروزرسانی دقایقی اختلال یا قطعی خواهیم داشت به محض اتمام عملیات مجددا اطلاع رسانی خواهد شد با عرض پوزش

👍9👎2🙏1

10 Aug 2026, 06:48 UTC≈3,620 views66 reactionsread 23 August 2026

تصمیم گرفتم دوباره درس خوندن را شروع کنم آماده یک جنگ تمام عیار باشید

🤣54🏆7👎2😐2👍1

7 Aug 2026, 20:44 UTC≈3,820 views11 reactionsread 23 August 2026

طبق بررسی انجام شده خود api تلگرام اختلال دارد و به زودی رفع خواهد شد (خارج از کنترل من هست و از سمت بنده قابل حل یا بررسی نیست)

🙏11

7 Aug 2026, 20:36 UTC≈3,460 views12 reactionsread 23 August 2026

سلام وقت بخیر، قطعی بات فروش و تمدید در حال پیگیری می‌باشد، (کانفیگ‌ها ولی اختلالی ندارند)

👍12

3 Aug 2026, 20:00 UTC≈4,420 views12 reactionsread 23 August 2026

بروزرسانی انجام شد با تشکر

👍10🙏2

3 Aug 2026, 19:36 UTC≈4,140 views12 reactionsread 23 August 2026

سلام وقت بخیر به دلیل بروزرسانی الزامی، دقایقی اختلال خواهیم داشت با عرض پوزش پیشاپیش

👍10🔥1🙏1

18 Jul 2026, 20:18 UTC≈5,890 views26 reactionsread 23 August 2026

تا وقتی نت ملی نشه کانفیگ جنگی فروش نداریم! دلیلش هم اینه معلوم نیست روشی که دفعه قبل جواب میداده الان جواب بده، بقیه هم با حدس و گمان دارن می فروشن.

👍26

16 Jul 2026, 21:02 UTC≈5,680 views26 reactionsread 23 August 2026

سلام وقت بخیر شاهد اختلال گسترده روی اینترنت کشور هستیم (کندی و کاهش پهنای باند)

👍21👎5

13 Jul 2026, 20:07 UTC≈6,240 views38 reactionsread 23 August 2026

گول کانفیگ نت ملی که بقیه با نرخ معمولی می فروشن را نخورید، اگر نت قطع شد بعدا به فکر خریدن از کسانی باشید که هنوز وصلن، کسانی که سری قبل وصل بودن لزوما سری بعد وصل نخواهند بود، خواهشا هم شروع نکنید تند تند از بات من کانفیگ بخرید، هیچ چی معلوم نیست، اصلا شاید هیچ چی قطع نشه

👍27👎9🙏2

Showing the 12 most recent of 27 posts we hold for @custom_config. 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 — 843,666 of 1,584,142entries 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.

Mentions

Named by 2 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.

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

“Private VPN” (@custom_config), 14,263 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/custom_config.

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.