Telegram RegisterThe public register of Telegram
Telegram profile photo for سرور کانفیگ کانفینگ رایگان

Channel

سرور کانفیگ کانفینگ رایگان

@FreakConfig

Not marked by Telegram, checked 30 August 2026

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Citations · Domains linked from posts · Cite this entry

1,769,927subscribers

+8,639 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1001836809801
TypeChannel
Username@FreakConfig
DescriptionFree servers and Free configs 🔗 @arthurmorgan ایران تسلیت🖤🕊️ فروش نداریم سرور رایگان | کانفیگ رایگان
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 August 2026
Measurements held24
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/FreakConfig

Topic

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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.

Views and reactions moved apart

On 4 of the 394 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0006 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/914815 Aug 2026, 07:31 UTC4.8 hours41,10066,800at least +25,6001819at most +2+14.9
/915115 Aug 2026, 07:40 UTC4.8 hours46,90066,500at least +19,5003536at most +2+11.4
/915215 Aug 2026, 07:40 UTC4.8 hours52,60069,900at least +17,2006768at most +2+10.0
/917616 Aug 2026, 11:32 UTC11 hours25,80043,400at least +17,5006768at most +2+10.2

Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).

What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.

Recorded under the key view_reaction_decoupling, last confirmed 30 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.

Growth

1,761,2881,775,6231,768,455.56 August 2026 — 1,761,288 subscribers6 August 2026 — 1,761,288 subscribers7 August 2026 — 1,763,140 subscribers8 August 2026 — 1,765,999 subscribers9 August 2026 — 1,767,654 subscribers9 August 2026 — 1,768,243 subscribers10 August 2026 — 1,771,412 subscribers11 August 2026 — 1,773,801 subscribers12 August 2026 — 1,775,623 subscribers14 August 2026 — 1,771,672 subscribers15 August 2026 — 1,772,106 subscribers16 August 2026 — 1,773,760 subscribers17 August 2026 — 1,775,432 subscribers19 August 2026 — 1,773,788 subscribers20 August 2026 — 1,774,897 subscribers20 August 2026 — 1,774,325 subscribers22 August 2026 — 1,772,923 subscribers23 August 2026 — 1,771,864 subscribers25 August 2026 — 1,771,124 subscribers26 August 2026 — 1,770,346 subscribers26 August 2026 — 1,769,458 subscribers27 August 2026 — 1,769,254 subscribers28 August 2026 — 1,770,020 subscribers29 August 2026 — 1,769,927 subscribers1,769,9276 August 202629 August 2026
24 measurements spanning 23 days, net +8,639. 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,759,138–1,777,773 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
29 Aug 2026, 21:271,769,927-93
28 Aug 2026, 21:051,770,020+766
27 Aug 2026, 19:251,769,254-204
26 Aug 2026, 21:141,769,458-888
26 Aug 2026, 00:421,770,346-778
25 Aug 2026, 03:131,771,124-740
23 Aug 2026, 16:261,771,864-1,059
22 Aug 2026, 03:151,772,923-1,402
20 Aug 2026, 23:051,774,325-572
20 Aug 2026, 02:021,774,897+1,109
19 Aug 2026, 02:561,773,788-1,644
17 Aug 2026, 23:421,775,432+1,672
16 Aug 2026, 22:271,773,760+1,654
15 Aug 2026, 14:051,772,106+434
14 Aug 2026, 03:181,771,672-3,951
12 Aug 2026, 20:131,775,623+1,822
11 Aug 2026, 18:051,773,801+2,389
10 Aug 2026, 21:141,771,412+3,169
9 Aug 2026, 21:511,768,243+589
9 Aug 2026, 00:551,767,654first reading

Engagement

375 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 74 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.11%
avg views ÷ 1,769,927 subscribers
Avg views / post
72,700
375 posts measured
Reaction rate
0.073%
reactions ÷ views · ER floor
Posts in window
375
of 375 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 30 August 2026
Posts held375 (5 August 202630 August 2026)
Views total27,276,080
Reactions total19,826
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 15:26 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
141
Videos
13
Links
4,260

Lifetime counters from Telegram’s own channel header, read 30 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 05s
Average length
31s

Measured directly from 4 videos 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 400 of this channel’s own posts over the last 30 days (6 of the 24-hour readings behind this are interpolated, not measured directly): across 241of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 12 hours of being posted; a typical post has already reached 9.57% of its 24-hour view count within the first hour, and 37.7% within the first six; the median 24-hour reach across those posts is 68,400 views3.86% of this channel’s own subscriber count (90th percentile 77,560).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/939730 Aug 2026, 13:28 UTC414 minutes2.0 hours old10,000 views ~37 reactions60 minutes: 6,416 interp.still climbing at last readingnot yet at 24h42 minutesprovisional — final view count still climbing
/939630 Aug 2026, 13:28 UTC414 minutes2.0 hours old9,700 views ~17 reactions60 minutes: 6,223 interp.still climbing at last readingnot yet at 24h42 minutesprovisional — final view count still climbing
/939530 Aug 2026, 13:28 UTC414 minutes2.0 hours old8,880 views ~5 reactions60 minutes: 5,732 interp.still climbing at last readingnot yet at 24h42 minutesprovisional — final view count still climbing
/939430 Aug 2026, 07:30 UTC1526 minutes7.9 hours old26,600 views ~82 reactions60 minutes: 6,548 interp.3.0 hours: 14,726 interp.6.0 hours: 24,200still climbing at last readingnot yet at 24h2.6 hoursprovisional — final view count still climbing
/939330 Aug 2026, 07:30 UTC1526 minutes7.9 hours old25,000 views ~37 reactions60 minutes: 6,376 interp.3.0 hours: 14,240 interp.6.0 hours: 23,000still climbing at last readingnot yet at 24h2.5 hoursprovisional — final view count still climbing
/939230 Aug 2026, 07:30 UTC1526 minutes7.9 hours old22,300 views ~12 reactions60 minutes: 5,652 interp.3.0 hours: 12,408 interp.6.0 hours: 20,000still climbing at last readingnot yet at 24h2.6 hoursprovisional — final view count still climbing
/939130 Aug 2026, 05:34 UTC192 minutes9.9 hours old34,600 views ~46 reactions60 minutes: 4,365 interp.3.0 hours: 12,9006.0 hours: 23,500still climbing at last readingnot yet at 24h3.4 hoursprovisional — final view count still climbing
/939029 Aug 2026, 21:29 UTC346 minutes18 hours old75,600 views ~78 reactions60 minutes: 6,879 interp.3.0 hours: 11,5006.0 hours: 13,90012 hours: 54,400still climbing at last readingnot yet at 24h10.0 hoursprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

19,826 reactions across 375 posts, in 11 distinct kinds. The most used accounts for 62.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12,33362.2%
👎4,00320.2%
👍1,5287.71%
🤣8364.22%
💔2951.49%
🔥2051.03%
🗿1970.994%
🍓1370.691%
🥰1200.605%
1120.565%
🕊600.303%

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

Measured over the 375 most recent posts we hold, published 5 August 2026 to 30 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

30 Aug 2026, 13:28 UTC≈10,000 views37 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇫🇷🇺🇸🇯🇵 🔌 وضعیت : متصل تا زمان فیلتر trojan://[email protected]:443?path=%2Fassignment&security=tls&insecure=0&host=www.ignitelimit.com&ech=ip.gs%2Budp%3A%2F%2F8.8.8.8&type=ws&allowInsecure=0&sni=www.ignitelimit.com#%F0%9F%87%AB%F0%9F%87%B7%40FreakConfig vmess://eyJhZGQiOiJndWFud2FuZy5hd3Nuby5jb20iLCJhaWQiOiIwIiwiYWxwbiI6IiIsImZwIjoiIiwiaG9zdCI6IiIsImlkIjoiNmE4OWEyMTUtMjJiZi00Y

22👎9👍4🥰2

30 Aug 2026, 13:28 UTC≈9,700 views17 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇩🇪🇹🇷🇫🇷 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:443?mode=auto&path=%2F&security=reality&encryption=none&pbk=BvR2i3CJEL9QwNAWKqkkHY3rnqJdOFLyKw5DZ9sA2C8&host=panel.freesavesafe.com&fp=firefox&type=xhttp&sni=panel.freesavesafe.com&sid=812609fa663c57fb#%F0%9F%87%AB%F0%9F%87%B7%40FreakConfig vless://2f35965a-9a9b-45fd-ba32-987296dfb6be@150.

8👎6👍3

30 Aug 2026, 13:28 UTC≈8,880 views5 reactionsread 30 August 2026
Photo

🎁 مجموع جوایز نقدی رولت زنده 🔘 🔥 با ثبت پیش‌بینی در بازی‌های رولت زنده جایگاهتان را در تورنمنت ارتقا دهید و سهم بیشتری را از مجموع جوایز ۱۰ میلیارد ریالی بت‌فوروارد دریافت کنید. اطلاعات بیش‌تر و قوانین بونوس: 🔗 bfrd.link/ROU 👍 ورود به سایت با فیلترشکن کلیک کنید BetForward.com کلیک کنید BetForward.com 🟢 دریافت سرورفیلترشکن رایگان 🅰g8 💻 @BetForward

5

30 Aug 2026, 07:30 UTC≈26,600 views82 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇹🇷🇷🇺 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:443?mode=stream-one&path=%2F&security=tls&alpn=h2&encryption=none&extra=%7B%22xPaddingBytes%22%3A%22100-1000%22%7D&insecure=0&host=lw-5.injaadvie.ir&fp=firefox&type=xhttp&allowInsecure=0&sni=lw-5.injaadvie.ir#%F0%9F%87%B9%F0%9F%87%B7%40FreakConfig vless://2f35965a-9a9b-45fd-ba32-987296dfb6be@b

56👎21🥰41

30 Aug 2026, 07:30 UTC≈25,000 views37 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇺🇸🇳🇱🇹🇷 🔌 وضعیت : متصل تا زمان فیلتر vless://65e294c6-9733-40cd-ade4-9bcf4017a1bd@dda685345af09097dda685345af09097.drwrdoh.org:2025?mode=auto&path=%2Fb4920d9c064cfe38c0021723&security=reality&encryption=none&extra=%7B%22scMaxEachPostBytes%22%3A%2B1000000%2C%2B%22scMaxConcurrentPosts%22%3A%2B100%2C%2B%22scMinPostsIntervalMs%22%3A%2B30%2C%2B%22xPaddingBytes%22%3A%2B%22100-1000%22%2C%2B

27👎10

30 Aug 2026, 07:30 UTC≈22,300 views12 reactionsread 30 August 2026
Photo

🎲 هوشمندانه شرط ببند... و برنده شو! 🚀 اگر به دنبال یک تجربه حرفه‌ای، امن و پرهیجان هستید، کازینو رامسر (Casino Ramsar) بهترین انتخاب برای شماست. با خیال راحت پیش‌بینی کنید و از لحظه لذت ببرید! چرا کازینو رامسر؟ * 🔥 ضرایب رقابتی: بالاترین و بهترین ضرایب بازار برای سود بیشتر * ✅ امن و معتبر: بالاترین سطح امنیت برای آرامش خاطر شما * ⚡️ پرداخت سریع: واریز و برداشت آنی و بدون معطلی * 🎁 بونوس‌های شگفت‌انگیز: بونوس‌های م

👎63👍21

30 Aug 2026, 05:34 UTC≈34,600 views46 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇺🇸🇨🇦 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:443?mode=gun&security=reality&encryption=none&pbk=TZVMqglhHzteJ6t34mtku75LKzXNq0CB6glKYMAH6zg&fp=firefox&type=grpc&serviceName=hub.v1.ApiService&sni=md4.univesalsrv.com&sid=8e07337954f9823f#%F0%9F%8F%B4%E2%80%8D%E2%98%A0%EF%B8%8F%40FreakConfig vless://38a2a2dc-f9e5-4fed-a732-a0c6a08023d

22👎15🤣7👍2

29 Aug 2026, 21:29 UTC≈75,600 views78 reactionsread 30 August 2026

👑کانفیگ فیلترشکن 📍 موقعیت سرور :🇩🇪🇫🇷 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:443?mode=auto&path=%2F&security=reality&encryption=none&pbk=BvR2i3CJEL9QwNAWKqkkHY3rnqJdOFLyKw5DZ9sA2C8&host=panel.freesavesafe.com&fp=firefox&type=xhttp&sni=panel.freesavesafe.com&sid=812609fa663c57fb#%F0%9F%87%AB%F0%9F%87%B7%40FreakConfig vless://[email protected]

56👎17🔥3💔1🥰1

29 Aug 2026, 21:29 UTC≈66,600 views8 reactionsread 30 August 2026
Video

۱۰٪ برد بیشتر از فرم انتخابی شما در بتگو 🤩🙄🤗 🎁۲۰۰٪ بونوس خوش آمدگویی🤑 -✔️تا ۸۰۰ میلیون تومان پاداش وفاداری ✔️-تا ۳۰٪ بونوس شارژ اضافی برای هر بار شارژ با روش حساب به حساب بانکی ✔️-اپلیکیشن اندروئید -✔️شارژ حساب بانکی و درگاه اتوماتیک بتگو پی و اتوپی 👽بات راهنمای بتگو و آدرس بدون فیلتر: @betgoir1_bot 📌لینک دائمی سایت بتگو 🔝 :🅰7 🪩 betgoir.com @betgoir Let's Go To Betgo 🚶‍♂️🚶‍♂️🚶‍♂️

7💔1

29 Aug 2026, 18:34 UTC≈78,300 views88 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇳🇱🇬🇧 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:22224?security=none&encryption=none&headerType=none&type=tcp#%F0%9F%8F%B4%E2%80%8D%E2%98%A0%EF%B8%8F%40FreakConfig vless://[email protected]:22223?security=none&encryption=none&headerType=none&type=tcp#%F0%9F%8F%B4%E2%80%8D%E2%98%A0%EF%B8%8F%40FreakConfig vles

👎4037👍8🗿3

29 Aug 2026, 14:04 UTC≈81,800 views87 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇫🇷🇳🇱 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:443?mode=auto&path=%2F&security=reality&encryption=none&pbk=BvR2i3CJEL9QwNAWKqkkHY3rnqJdOFLyKw5DZ9sA2C8&host=panel.freesavesafe.com&fp=firefox&type=xhttp&sni=panel.freesavesafe.com&sid=812609fa663c57fb#%F0%9F%87%AB%F0%9F%87%B7%40FreakConfig vless://[email protected]

58👎23👍6

29 Aug 2026, 14:04 UTC≈82,500 views45 reactionsread 30 August 2026

👑 کانفیگ فیلترشکن 📍 موقعیت سرور :🇩🇪🇳🇱🇺🇸 🔌 وضعیت : متصل تا زمان فیلتر vless://[email protected]:8080?security=none&encryption=none&headerType=none&type=tcp#%F0%9F%87%A9%F0%9F%87%AA%40FreakConfig vless://[email protected]:443?mode=gun&security=reality&encryption=none&authority=TELEGRAM%40MARAMBASHI_MARAMBASHI&pbk=JXFsWHYjhAcR-7yz9tuCTMdcfuiyC9a-C9ewA55Z63

30👎11👍21💔1

Showing the 12 most recent of 375 posts we hold for @FreakConfig. 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 edited after publishing

@FreakConfig edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 August 2026
Most recent edit
15 August 2026

Citation-graph rank

Citation-graph rank — 83,587 of 1,626,935entries 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.

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 13 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.

Domains linked from posts

3 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

derbybet.com4 posts · 6 August 2026 – 7 August 2026 · example post
cfbdiuhebmr.shop2 posts · 6 August 2026 – 7 August 2026 · example post
betinja.bet1 post · 6 August 2026 – 6 August 2026 · example post

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

“سرور کانفیگ کانفینگ رایگان” (@FreakConfig), 1,769,927 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/FreakConfig.

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.