Telegram RegisterThe public register of Telegram
Telegram profile photo for NPatch

Channel

NPatch

@NPatch

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

18,554subscribers

+354 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002141231601
TypeChannel
Username@NPatch
DescriptionNPatch is a root‑less Xposed framework supporting Android 9 to 17. Website: npatch.nkbe.top Canary: @ONPatch
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/NPatch

Growth

18,20018,55418,3777 August 2026 — 18,200 subscribers8 August 2026 — 18,219 subscribers9 August 2026 — 18,241 subscribers10 August 2026 — 18,258 subscribers11 August 2026 — 18,290 subscribers12 August 2026 — 18,304 subscribers13 August 2026 — 18,350 subscribers14 August 2026 — 18,379 subscribers16 August 2026 — 18,416 subscribers17 August 2026 — 18,454 subscribers18 August 2026 — 18,472 subscribers19 August 2026 — 18,491 subscribers20 August 2026 — 18,518 subscribers21 August 2026 — 18,554 subscribers7 August 202621 August 2026
14 measurements spanning 14 days, net +354. 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,147–18,607 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 12:4918,554+36
20 Aug 2026, 12:4218,518+27
19 Aug 2026, 12:0318,491+19
18 Aug 2026, 14:3618,472+18
17 Aug 2026, 17:2518,454+38
16 Aug 2026, 14:5718,416+37
14 Aug 2026, 20:4518,379+29
13 Aug 2026, 12:3818,350+46
12 Aug 2026, 15:2418,304+14
11 Aug 2026, 14:0518,290+32
10 Aug 2026, 11:1018,258+17
9 Aug 2026, 09:5318,241+22
8 Aug 2026, 11:0318,219+19
7 Aug 2026, 12:1518,200first reading

Engagement

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

ERR · 30 days
36.5%
avg views ÷ 18,554 subscribers
Avg views / post
6,770
14 posts measured
Reaction rate
0.388%
reactions ÷ views · ER floor
Posts in window
15
of 24 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 18 August 2026
Posts held24 (1 July 202618 August 2026)
Views total94,770
Reactions total368
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 22:05 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
232
Videos
3
Links
125

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

704 reactions across 22 posts, in 16 distinct kinds. The most used accounts for 34.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍24334.5%
19928.3%
🤯8712.4%
🔥486.82%
💅476.68%
😁334.69%
👾192.70%
🍌50.71%
🤔50.71%
😍40.568%
😭40.568%
30.426%
🥰30.426%
👏20.284%
🎉10.142%
💯10.142%

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

Measured over the 24 most recent posts we hold, published 1 July 2026 to 18 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.

Telegram Stars

Stars received
22
across the posts below
Posts paid on
3
of 22 we hold a reading for · 14%
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 24 most recent posts we hold for this entry, published 1 July 2026 to 18 August 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

18 Aug 2026, 09:20 UTC≈3,530 views39 reactionsread 22 August 2026

宣传避雷,不通知用户的情况下就将硬盘拿给其他用户

👍353😍1

17 Aug 2026, 16:46 UTCviews —

NPatch pinned «Come try out the latest NPatch! I'm really looking for more feedback, but that's been so hard to come by. Go to @ONPatch»

17 Aug 2026, 16:45 UTC≈3,940 views20 reactionsread 22 August 2026

Come try out the latest NPatch! I'm really looking for more feedback, but that's been so hard to come by. Go to @ONPatch

👍146

17 Aug 2026, 07:57 UTC≈3,930 views32 reactionsread 22 August 2026

重磅功能:自适应二次修补(智能提取原包) 平时修补应用时,如果选到了之前打过补丁的 APK(比如换模块、升级框架),多层嵌套打包往往会导致应用闪退或签名冲突。新版本带来了完整的自适应修补链路! ✨ 更新亮点: 🔹 全方位框架识别 - 智能识别由 NPatch、LSPatch 或 FunPatchApp (FPA) 修补过的应用。 - 无论是在已安装应用列表、存储空间选包,还是通过分享/外部 Intent 调起,均可精准识别。 🔹 一键提取内置原包 - 选中已修补应用时,自动弹窗提示,支持一键解压并校验内置的纯净原版 APK 重新修补,告别套娃修补! - 内建 包名一致性与完整性校验,防止异常包导致修补错误。 🔹 灵活的修补策略 - 🥇 提取原包修补:推荐方案,基于干净原包重新打包。 - 🥈 直接修补外壳:保留对外壳进行二次修补的能力。 - 🛡 优雅降级:若原包使用 Level 0 无内置原包模式,自动提示并支持一键降级为外

23👍9

14 Aug 2026, 05:27 UTC≈5,490 views27 reactionsread 22 August 2026

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

22🔥4👍1

12 Aug 2026, 15:53 UTC≈6,060 views36 reactionsread 22 August 2026
Photo

DeepSeek v4 Pro 正式版 0813发布了

30👾6

11 Aug 2026, 10:35 UTC≈6,450 views61 reactionsread 22 August 2026

Posted without readable text

👍4215👏2🔥2

6 Aug 2026, 17:43 UTC≈7,710 views39 reactionsread 22 August 2026
Photo

GitHub Actions is down.~

😁33👾42

31 Jul 2026, 11:01 UTC≈9,570 views20 reactions11 Starsread 22 August 2026

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.

16👍3🤯1

31 Jul 2026, 08:53 UTC≈7,730 views15 reactions10 Starsread 22 August 2026

outputLog 功能升級: 大幅擴充日誌記錄範圍,全面涵蓋 Legacy XposedBridge.log、Modern API 的 XposedInterface.log/context.log、框架事件及未捕獲的 Java/Kotlin 崩潰;無論是主程序或 package:* 次程序,輸出的日誌均包含時間、程序 (PID)、執行緒 (TID)、級別、TAG 與完整堆疊。 同時,為確保文件與實際實作一致,本功能明確排除模組直接呼叫 android.util.Log 的 Logcat 訊息,以及 Native fatal signal 與系統級 Tombstone 日誌。 期望能為用戶與開發者帶來更清晰、更高效的使用體驗。

👍114

28 Jul 2026, 01:18 UTC≈8,570 views25 reactions1 Starread 22 August 2026
Forwarded from @NeoZygiskPhoto

Rewrite the manager in Compose Screenshots from the current branch, on a Pixel 6 running Android 17. You can download it through Github Actions.

25

Showing the 12 most recent of 24 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

Citation-graph rank

Citation-graph rank — 90,490 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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.

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.

Magisk alpha
@magiskalpha · 65,367
Telegram ranks this channel #12 of 40 here — alongside 39 others — read 21 August 2026
LSPosed
@LSPosed · 189,402
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 17 August 2026
Clash Verge Rev Channel
@clash_verge_re · 77,927
Telegram ranks this channel #54 of 64 here — alongside 63 others — read 19 August 2026

This channel appears in 3 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 21 August 2026 — this entry's latest reading, not the date you are reading this.

“NPatch” (@NPatch), 18,554 subscribers as measured 21 August 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.