Telegram RegisterThe public register of Telegram
Telegram profile photo for Patt's Channel

Channel

Patt's Channel

@patt_channel_x

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

35,715subscribers

+7,121 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003992539403
TypeChannel
Username@patt_channel_x
CreatedBetween 1 April 2026 and 6 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 October 2026
Measurements held36
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/patt_channel_x

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 per post sit far above this size band

35,100 average views per post against 35,715 subscribers — an engagement rate of 98.2%. Across the 3,493 registered channels in the same cohort — 31,624–99,943 subscribers, posting mainly in Persian — the middle half sit between 2.07% and 10.9%, with a median of 5.04%.

What this was computed from
Window30 days (6 September 2026 – 6 October 2026)
Posts measured27 of 27 published in the window (0 exact, 27 rounded by Telegram)
Views totalled947,120
Mature posts only108.9% over 22 posts read at least 24h after publication
Subscribers35,715 measured 4 October 2026
Cohortb31623:fas · 3,493 channels · p10 0.714% · p25 2.07% · p50 5.04% · p75 10.9% · p90 20.6%
Position in cohort99.599th percentile · 19.5× the cohort median
Uncertainty±0.016% of the figure, from Telegram’s rounding
Post languagePersian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 6 October 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

28,59435,71532,154.56 August 2026 — 28,594 subscribers6 August 2026 — 28,594 subscribers6 August 2026 — 28,654 subscribers7 August 2026 — 28,742 subscribers8 August 2026 — 28,778 subscribers9 August 2026 — 28,831 subscribers10 August 2026 — 28,956 subscribers11 August 2026 — 29,009 subscribers12 August 2026 — 29,070 subscribers14 August 2026 — 29,119 subscribers15 August 2026 — 29,506 subscribers17 August 2026 — 31,013 subscribers18 August 2026 — 31,346 subscribers19 August 2026 — 31,474 subscribers20 August 2026 — 31,572 subscribers22 August 2026 — 31,829 subscribers23 August 2026 — 32,037 subscribers25 August 2026 — 32,220 subscribers26 August 2026 — 32,300 subscribers27 August 2026 — 32,373 subscribers28 August 2026 — 32,433 subscribers29 August 2026 — 32,546 subscribers30 August 2026 — 32,613 subscribers31 August 2026 — 32,667 subscribers1 September 2026 — 32,712 subscribers2 September 2026 — 32,743 subscribers3 September 2026 — 32,811 subscribers5 September 2026 — 32,843 subscribers8 September 2026 — 33,001 subscribers11 September 2026 — 33,090 subscribers13 September 2026 — 33,097 subscribers15 September 2026 — 33,281 subscribers17 September 2026 — 33,327 subscribers19 September 2026 — 33,355 subscribers26 September 2026 — 33,450 subscribers4 October 2026 — 35,715 subscribers6 August 20264 October 2026
36 measurements spanning 60 days, net +7,121. 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 27,526–36,783 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)SubscribersChange
4 Oct 2026, 16:2035,715+2,265
26 Sept 2026, 14:3933,450+95
19 Sept 2026, 14:5933,355+28
17 Sept 2026, 01:0033,327+46
15 Sept 2026, 02:3933,281+184
13 Sept 2026, 13:1833,097+7
11 Sept 2026, 14:5833,090+89
8 Sept 2026, 23:3833,001+158
5 Sept 2026, 13:1732,843+32
3 Sept 2026, 16:1632,811+68
2 Sept 2026, 10:0332,743+31
1 Sept 2026, 06:3832,712+45
31 Aug 2026, 03:5532,667+54
30 Aug 2026, 02:1632,613+67
29 Aug 2026, 04:5532,546+113
28 Aug 2026, 01:5432,433+60
27 Aug 2026, 00:2432,373+73
26 Aug 2026, 01:3632,300+80
25 Aug 2026, 00:3732,220+183
23 Aug 2026, 15:0432,037first reading

Engagement

67 posts held, back to 6 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 108 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
100.8%
avg views ÷ 35,715 subscribers
Avg views / post
36,000
27 posts measured
Reaction rate
2.65%
reactions ÷ views · ER floor
Posts in window
27
of 67 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 6 October 2026
Posts held67 (6 June 2026 – 6 October 2026)
Views total971,600
Reactions total25,731
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 20:27 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
8
Links
31

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

64,030 reactions across 67 posts, in 61 distinct kinds. The most used accounts for 74.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤47,93674.9%
👍3,6515.70%
🔥2,8684.48%
😭1,7642.75%
🤣1,3982.18%
👏1,0871.70%
💔7231.13%
❤‍🔥6471.01%
😱5400.843%
🤬4760.743%
🍾4220.659%
🤔3810.595%
🙏3560.556%
👎2940.459%
🫡1610.251%
😁1330.208%
😢1190.186%
💋1040.162%
🥰860.134%
💩840.131%
41 further kinds8001.25%

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

Measured over the 67 most recent posts we hold, published 6 June 2026 to 6 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.

Telegram Stars

Stars received
1,136
across the posts below
Posts paid on
63
of 67 we hold a reading for · 94%
Most on one post
121
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @patt_channel_x. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 67 most recent posts we hold for this entry, published 6 June 2026 to 6 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Oct 2026, 04:39 UTC≈14,600 views630 reactions17 Starsread 6 October 2026

برای کانفیگ‌های رایگان هم تغییرات مناسب انجام شد. PattNG PattN Free-Configs Serverless-for-Iran Mitm-DomainFronting

❤576🔥24👍14💘6❤‍🔥3👌2👎2🍌1

5 Oct 2026, 17:43 UTC≈11,500 views801 reactionsread 5 October 2026

نشر حداکثری

❤682🫡41👍34🤣17❤‍🔥6🤩5🤨4🔥3

5 Oct 2026, 17:38 UTC≈51,200 views1,286 reactions12 Starsread 6 October 2026

جمع بندی راه‌های کنونی اتصال به کلودفلر بر روی فایروال همراه اول: 1. CDN/WORKER with ECH برای اتصال به یک کانفیگ cdn/worker از طریق ECH باید ابتدا از یک آدرس مناسب به طور مثال 188.114.97.6 استفاده کنید، finalMask و cipherSuites را پاک کنید، فینگرپرینت را روی chrome قرار دهید و در قسمت echConfigList به طور مثال مقدار: cloudflare-ech.com+udp://1.1.1.1 را وارد کنید. 2. CDN/WORKER with IPv6 ابتدا echConfigList و ciph…

❤1,170🙏42👍25👏9😢9❤‍🔥8🤯8🔥7

4 Oct 2026, 14:56 UTC≈13,400 views410 reactionsread 5 October 2026

اتر هم رو IPv6 وصله (wireguard/warp-in-warp)

❤354😭31💩5🖕5👍4🙏4👏3🕊2

4 Oct 2026, 14:11 UTC≈21,300 views586 reactionsread 6 October 2026

سرورلس هم به ورژن 52 آپدیت شد، فعلا فقط در صورتی که IPv6 دارید میتونید ازش برای دسترسی به یوتویوب و ... استفاده کنید.

❤493😭63👍14🤡6🙏5🔥3🍌1💊1

4 Oct 2026, 10:27 UTC≈17,700 views598 reactions2 Starsread 5 October 2026

محدودیت ۶ پکت روی وبسوکت (alpn/1.1) به طور کلی بر روی تمام دامنه‌های غیر وایت کلودفلر اعمال شده.(فعلا فقط برای IPv4) مواردی که الان روی کلودفلر کار میکنند: 1. IPv6 2. ECH 3. XHTTP (alpn h2)

❤442🤬97😭26👍8🤡5💩4🔥4🕊4

4 Oct 2026, 05:23 UTC≈23,100 views731 reactions2 Starsread 6 October 2026

ببینید اگه اتصالتون مستقیمه (غیر CDN) مطالبی که گفتم شامل حال شما نمیشه. مطالب بنده در مورد روش‌های اتصال به کلودفلر هست.

❤647👍44🕊11❤‍🔥8😭8🖕5🌭3🤡3

4 Oct 2026, 04:53 UTC≈29,300 views1,058 reactions14 Starsread 5 October 2026

پروتوکل UDP هم به طور کامل روی ip های کلودفلر بسته شد (فعلا فقط روی فایروال همراه اول و فقط هم‌ IPv4) در نتیجه امکان اتصال به warp از طریق پروتوکل wireguard و یا masque-h3 دیگر امکان پذیر نمیباشد.(روی IPv4) برای پروتوکل masque-h2 نیز، امکان استفاده از ECH از سمت خود کلودفلر بسته است، بنابراین در حال حاضر فقط با استفاده از IPv6 میتوان از این پروتوکل استفاده کرد. روشهای جدیدی که بزودی منتشر خواهد شد امکان اتصال کانک…

💔612❤367🙏32🤬12👍11❤‍🔥8🖕5😨5

4 Oct 2026, 04:44 UTC≈18,500 views698 reactions1 Starread 5 October 2026

Aether IPv4 🪦

😱519😭90❤53👀14🤡6🕊5😁5🥴2

4 Oct 2026, 04:26 UTC≈19,600 views1,114 reactions9 Starsread 5 October 2026

فرگمنت روی فایروال همراه اول (شامل همراه اول، مخابرات، شاتل و ...) به طور کامل از کار افتاده. روی فایروال ایرانسل (شامل ایرانسل، پیشگامان، مبین‌نت و حتی خود همراه اول در برخی مناطق) هنوز کار میکنه. /// روشهایی که هنوز روی فایروال همراه اول کار میکنند: 1. IPv6 (with F&F method) 2. ECH 3. XHTTP برای استفاده از ECH کافیه اول finalMask و cipherSuites رو پاک کنید، فینگرپرینت رو روی chrome بزارید و در قسمت echConfigLis…

❤1,030👍30🔥22😁13🙏8❤‍🔥3🕊3🖕2

4 Oct 2026, 04:12 UTC≈23,500 views593 reactions3 Starsread 5 October 2026

Fragment (on MCI IPv4)🪦

😭525❤34🤔20🕊7👍3🤬3🎉1

4 Oct 2026, 00:29 UTC≈31,000 views1,195 reactions6 Starsread 6 October 2026

PattNG v2.3.10-P60 منتشر شد. (+Android 10) امکانات اضافه شده: ۱. مقادیر متد فرگمنت+فینگرپرینت اکنون به صورت آپشن تو خود اپ اضافه شده، بنابراین برای اجرای متد فرگمنت+فینگرپرینت کافیست: address: 188.114.97.6 (or any clean ip) finalMask: tlshello-0-len fingerprint: unsafe cipherSuites: semi-python را انتخاب کنید، و دیگر نیاز به کپی پیست ندارید. برای اجرای این متد روی کانفیگ‌های اتر نیز کافیست: finalMask: tlshello…

❤1,090👍41🔥29👏9💋6❤‍🔥5🍓5👎3

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@patt_channel_x edited 6 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
16 August 2026
Most recent edit
5 October 2026

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 27 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Patt's Channel” (@patt_channel_x), 35,715 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/patt_channel_x.

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.