Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Growth
32 measurements spanning 42 days, net +880. 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 18,068–19,212 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)
Subscribers
Change
18 Sept 2026, 02:20
19,080
+44
15 Sept 2026, 22:20
19,036
+27
14 Sept 2026, 03:39
19,009
+29
12 Sept 2026, 12:57
18,980
+32
10 Sept 2026, 08:02
18,948
+47
7 Sept 2026, 03:00
18,901
+60
4 Sept 2026, 08:20
18,841
+15
2 Sept 2026, 17:35
18,826
+19
1 Sept 2026, 19:23
18,807
+22
31 Aug 2026, 20:48
18,785
+10
30 Aug 2026, 19:26
18,775
+29
29 Aug 2026, 19:27
18,746
+27
28 Aug 2026, 17:15
18,719
+17
27 Aug 2026, 17:05
18,702
+31
26 Aug 2026, 18:26
18,671
+27
25 Aug 2026, 19:36
18,644
+23
24 Aug 2026, 16:02
18,621
+33
23 Aug 2026, 03:09
18,588
+34
21 Aug 2026, 12:49
18,554
+36
20 Aug 2026, 12:42
18,518
first reading
Engagement
25 posts held, back to 1 July 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 54 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
7.76%
avg views ÷ 19,080 subscribers
Avg views / post
1,480
1 post measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
1
of 25 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 2 September 2026
Posts held
25 (1 July 2026 – 2 September 2026)
Views total
1,480
Reactions total
17
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 02:11 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.
Reaction mix
744 reactions across 23 posts, in 16 distinct kinds. The most used accounts for 34.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
255
34.3%
❤
214
28.8%
🤯
87
11.7%
🔥
48
6.45%
💅
47
6.32%
😁
33
4.44%
👾
19
2.55%
🥰
16
2.15%
🍌
5
0.672%
🤔
5
0.672%
😍
4
0.538%
😭
4
0.538%
⚡
3
0.403%
👏
2
0.269%
🎉
1
0.134%
💯
1
0.134%
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 23 of the 25 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 744 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 1 July 2026 to 2 September 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
22
across the posts below
Posts paid on
3
of 23 we hold a reading for · 13%
Most on one post
11
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NPatch. 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 25 most recent posts we hold for this entry, published 1 July 2026 to 2 September 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.
The Update that Changed the World (改變世界的更新) has been officially released.
⚠️ 【重要升級提醒 / Important Notice】
由於本次版本對底層架構(API 102 規範對齊)、資料庫模型及 IPC 通訊鏈路進行了全面重構,
從舊版本(v1.0.6 及更早版本)升級的使用者,強烈建議先卸載舊版 Manager 後再安裝 v1.0.7,以避免快取殘留或舊資料結構衝突導致的異常。
Due to comprehensive architectural refactoring (
API 102 alignment, database model updates, and IPC lifecycle changes), users upgrading from older versions (v1.0.6 or earlier) are strongl…
NPatch Remote API 是给 Xposed 模块 App 使用的轻量 Android SDK。它让模块设置界面在本地修补模式下安全连接 NPatch Manager,共享 Remote Preferences 与 Remote Files。
NPatch Remote API is a small Android SDK for Xposed module companion apps. It lets a module settings UI securely connect to NPatch Manager in Local mode and share Remote Preferences and Remote Files.
Showing the 12 most recent of 25 posts we hold for @NPatch. 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
@NPatch 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
13 August 2026
Most recent edit
13 August 2026
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 3 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.
Nagram Tips @NagramTips · 46,239 Telegram ranks this channel #2 of 49 here — alongside 48 others — read 30 August 2026
FunProject @QToolCI · 49,485 Telegram ranks this channel #3 of 51 here — alongside 50 others — read 12 September 2026
哔哩漫游 @biliroaming · 56,222 Telegram ranks this channel #5 of 50 here — alongside 49 others — read 12 September 2026
QAuxiliary @QAuxiliary · 44,820 Telegram ranks this channel #6 of 58 here — alongside 57 others — read 12 September 2026
Magisk alpha @magiskalpha · 65,706 Telegram ranks this channel #12 of 40 here — alongside 39 others — read 21 August 2026
FlClash Channel @FlClash · 47,123 Telegram ranks this channel #13 of 53 here — alongside 52 others — read 28 August 2026
Hide My Applist @HideMyApplist · 40,938 Telegram ranks this channel #19 of 24 here — alongside 23 others — read 30 August 2026
LSPosed @LSPosed · 194,124 Telegram ranks this channel #19 of 57 here — alongside 56 others — read 17 August 2026
LSPosedArchives @LSPosedArchives · 25,244 Telegram ranks this channel #21 of 36 here — alongside 35 others — read 14 September 2026
LuckyTool @LuckyTool · 28,572 Telegram ranks this channel #21 of 56 here — alongside 55 others — read 12 September 2026
5ec1cff @real5ec1cff · 37,318 Telegram ranks this channel #22 of 51 here — alongside 50 others — read 2 September 2026
不靠谱的喵(>^ω^<) #CatGPT @MlgmXyysd_bibilailai · 21,690 Telegram ranks this channel #30 of 54 here — alongside 53 others — read 23 September 2026
Real Nullptr @nullptr_dev · 20,269 Telegram ranks this channel #35 of 54 here — alongside 53 others — read 28 September 2026
HyperCeiler | Release & Notice @cemiuiler_release · 26,729 Telegram ranks this channel #37 of 51 here — alongside 50 others — read 12 September 2026
Clash Verge Rev Channel @clash_verge_re · 81,375 Telegram ranks this channel #54 of 64 here — alongside 63 others — read 19 August 2026
This channel appears in 15 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“NPatch” (@NPatch), 19,080 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/NPatch.
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.