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 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 5 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (6 of the pairs behind the counts below)
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
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. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 1,020 comparable posts for this entry, running 5 August 2026 to 10 November 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 5 channels, the one whose matching posts we hold earliest is @FreakConfig — which is this entry. That is a statement about our reading window, not a claim of authorship.
Views and reactions moved apart
On 23 of the 497 posts we watched over 30 days, 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.0020 reactions per view.
Each interval, as we read it — views and reactions before and after
Expected is 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 keys clone_mutual · clone_source · view_reaction_decoupling, 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 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
65 measurements spanning 96 days, net +602,117. 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,632,317–2,750,070 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
10 Nov 2026, 15:58
2,363,405
-36,603
9 Nov 2026, 04:17
2,400,008
+1,645
7 Nov 2026, 17:49
2,398,363
-2,873
6 Nov 2026, 15:16
2,401,236
-28,473
5 Nov 2026, 12:15
2,429,709
-49,183
4 Nov 2026, 09:17
2,478,892
-10,104
3 Nov 2026, 11:01
2,488,996
+1,408
2 Nov 2026, 08:27
2,487,588
-58,262
1 Nov 2026, 08:45
2,545,850
-8,571
31 Oct 2026, 11:36
2,554,421
-8,689
30 Oct 2026, 15:01
2,563,110
-10,865
29 Oct 2026, 17:58
2,573,975
-11,594
28 Oct 2026, 18:41
2,585,569
-6,702
27 Oct 2026, 18:00
2,592,271
-16,764
26 Oct 2026, 15:11
2,609,035
-12,063
25 Oct 2026, 16:28
2,621,098
+55,349
24 Oct 2026, 15:29
2,565,749
+67,381
23 Oct 2026, 15:17
2,498,368
+141,543
22 Oct 2026, 15:19
2,356,825
+20,845
21 Oct 2026, 10:05
2,335,980
first reading
Engagement
1,345 posts held, back to 5 August 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 280 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.52%
avg views ÷ 2,363,405 subscribers
Avg views / post
59,500
486 posts measured
Reaction rate
0.38%
reactions ÷ views · ER floor
Posts in window
486
of 1,345 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
Window
Rolling 30 days · latest post in window 11 November 2026
Posts held
1,345 (5 August 2026 – 11 November 2026)
Views total
28,932,310
Reactions total
110,005
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 07:25 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
≈281
Videos
≈56
Links
≈4,820
Lifetime counters from Telegram’s own channel header, read 11 November 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
15m 54s
Average length
20s
Measured directly from 48 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 503 of this channel’s own posts over the last 30 days: across 471 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 5.1 hours of being posted; a typical post has already reached 19.6% of its 24-hour view count within the first hour, and 69.4% within the first six; the median 24-hour reach across those posts is 40,050 views — 1.69% of this channel’s own subscriber count (90th percentile 75,790).
8 most recently posted, with a view-velocity reading
60 minutes: 8,762 interp. → 3.0 hours: 19,300 → 6.0 hours: 32,200 → 12 hours: 37,100still climbing at last reading
not yet at 24h
3.3 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 views is 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
142,510 reactions across 990 posts, in 14 distinct kinds. The most used accounts for 50.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤣
71,243
50.0%
❤
30,594
21.5%
👍
14,552
10.2%
👎
10,633
7.46%
💔
10,000
7.02%
🔥
1,569
1.10%
🗿
1,409
0.989%
🥰
630
0.442%
🤯
595
0.418%
🍓
507
0.356%
⚡
326
0.229%
🌚
239
0.168%
🕊
114
0.08%
🐳
99
0.069%
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 993 of the 1,000 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 142,510 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 28 August 2026 to 11 November 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: 17 of 486 posts held from the last 30 days (3.50%) 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).
🔑کانفیگ عمومی v2ray
📍لوکیشن : 🇺🇸🇨🇦
I با ضربه کپی کنید
vless://[email protected]:443?path=%2Ffp&security=tls&encryption=none&insecure=0&host=fs.qicai99.com&type=ws&allowInsecure=0&sni=fs.qicai99.com#%F0%9F%87%AF%F0%9F%87%B5%40FreakConfig
vless://[email protected]:8008?mode=auto&path=%2F&security=&encryption=none&type=xhttp#%F0%9F%8F%B4%E2%80%8D%E2%98%…
🔑کانفیگ عمومی v2ray
📍لوکیشن : 🇳🇱🇩🇪🇷🇺
I با ضربه کپی کنید
vless://[email protected]:443?mode=gun&security=tls&encryption=none&insecure=0&fp=firefox&type=grpc&serviceName=stats.v2.StreamService&allowInsecure=0&sni=cdn.mediacorphub.org#%F0%9F%87%B3%F0%9F%87%B1%40FreakConfig
vless://[email protected]:2058?security=reality&encryption=none&pbk=lJBs…
🔑کانفیگ عمومی v2ray
📍لوکیشن : 🇳🇱🇺🇸
I با ضربه کپی کنید
vless://[email protected]:443?mode=gun&security=tls&encryption=none&insecure=0&fp=firefox&type=grpc&serviceName=hub.v1.ObjectService&allowInsecure=0&sni=edge.mediacorphub.org#%F0%9F%87%B3%F0%9F%87%B1%40FreakConfig
vless://[email protected]:48312?security=reality&encryption=no…
🔑کانفیگ عمومی v2ray
📍لوکیشن : 🇪🇸🇨🇳
I با ضربه کپی کنید
vless://[email protected]:2058?security=reality&encryption=none&pbk=lJBsn9ndieTIUBzXkJUhf6O0OE8pm29_z1fUtARwL0s&headerType=none&fp=firefox&type=tcp&flow=xtls-rprx-vision&sni=www.cloudflare.com&sid=937255313d6ce673#%F0%9F%87%A8%F0%9F%87%B3%40FreakConfig
vless://[email protected]:2058?security=rea…
🔑کانفیگ عمومی v2ray
📍لوکیشن : 🇳🇱🇹🇷
I با ضربه کپی کنید
vless://[email protected]:443?path=%2Ffp&security=tls&encryption=none&insecure=0&host=fs.qicai99.com&type=ws&allowInsecure=0&sni=fs.qicai99.com#%F0%9F%87%AF%F0%9F%87%B5%40FreakConfig
vless://[email protected]:443?security=reality&encryption=none&pbk=nf9eFC0yVVO-peA-wmZ1EEIwAaSstK2JN3tJV0WNJQE&he…
❤44👍2👎2🕊2
Showing the 12 most recent of 1,345 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 9 posts 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
5 November 2026
Posts recorded as deleted after publishing
We recorded 211 posts on @FreakConfig 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
7 August 2026
Most recent seen missing
10 November 2026
Median time before seen missing
24 hours
Seen missing in the last 30 days
17
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 14 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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
کانفیگ رایگان V2Ray و پروکسی ⚡ @proxy_Shadowsocks · 48,562 Telegram ranks this channel #1 of 43 here — alongside 42 others — read 2 October 2026
کانفیگ v2ray | پروکسی تلگرام @VPNv2ray_Fre · 26,407 Telegram ranks this channel #2 of 42 here — alongside 41 others — read 2 October 2026
Parsashonam | V2Ray | VPN @Parsashonam · 131,918 Telegram ranks this channel #3 of 58 here — alongside 57 others — read 2 October 2026
Fain | سرور کانفیگ v2ray رایگان @v2fre · 59,523 Telegram ranks this channel #3 of 38 here — alongside 37 others — read 2 October 2026
v2rayNG /رفع فیلتر @v2rayargon · 19,124 Telegram ranks this channel #4 of 71 here — alongside 70 others — read 2 October 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
3 domains this 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.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“سرور کانفیگ کانفینگ رایگان” (@FreakConfig), 2,363,405 subscribers as measured 10 November 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.
