Telegram RegisterThe public register of Telegram
Telegram profile photo for LSPilot

Channel

LSPilot

@LSPilot

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,045subscribers

+258 since we began measuring on 31 October 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004399645853
TypeChannel
Username@LSPilot
Created28 June 2026 — measured — dated from the channel’s first post
First recorded31 October 2026
Last confirmed live3 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/LSPilot

Growth

1,7872,0451,91631 October 2026 — 1,787 subscribers1 November 2026 — 1,847 subscribers3 November 2026 — 2,045 subscribers31 October 20263 November 2026
3 measurements spanning 3 days, net +258. 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,748–2,084 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 22:092,045+198
1 Nov 2026, 06:481,847+60
31 Oct 2026, 22:221,787first reading

Engagement

13 posts held, back to 28 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
106.1%
avg views ÷ 2,045 subscribers
Avg views / post
2,170
4 posts measured
Reaction rate
0.346%
reactions ÷ views · ER floor
Posts in window
4
of 13 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 31 October 2026
Posts held13 (28 June 2026 – 31 October 2026)
Views total8,680
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Oct 2026, 22:22 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

Video runtime
1m 32s
Average length
1m 32s

Measured directly from 1 video 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.

Reaction mix

89 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 52.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4752.8%
❤2224.7%
🥰77.87%
🤔55.62%
🆒22.25%
🎉22.25%
🐳22.25%
😁11.12%
🫡11.12%

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

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

Recent posts

Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) 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).

31 Oct 2026, 13:44 UTC≈1,050 views2 reactionsread 31 October 2026

#互推 【系统模块】LuckyTool: ColorOS扩展优化 【聚合模块】HookVip: 上百款应用破解 【聚合模块】NukeApp: 微信抖音增强 【聚合模块】LSPilot: 逆向分析助手 【QQ模块】QWish: QQ扩展功能 【TIM模块】TimTool: TIM扩展功能 【WX模块】WABTest: WX灰度功能 【WX模块】Qaulity: 微信扩展功能 【WX模块】Wren: 微信增强功能 Tip: 欢迎各位开发者加入互推

🎉2

30 Oct 2026, 15:03 UTC≈1,290 views8 reactionsread 31 October 2026

插件解释器已从Bsh-Android换到Bsh-Rust,底层全部由Rust重写,无jvm介入时速度更快更节省内存,jvm(按需)介入时速度和内存占用也有所提升,还加了一些新特性

🤔5🐳2❤1

29 Oct 2026, 13:57 UTC≈1,480 views14 reactionsread 31 October 2026
Photo

Zygisk 注入和新的跨协议通讯;Zygisk模式下还有专有的注入顺序,包括常规注入和早期注入

👍14

25 Sept 2026, 14:51 UTC≈3,860 views3 reactionsread 31 October 2026

后续版本会把内置的逆向工具给删除掉,只留几个简单的工具以及部分相关的提示词 建议现在可以实现相关的 MCP,可以利用自带的 MCP 插件多配合 loadApk 和 loadDex 以及 hostContext,MCP 插件文档要等后续才会更新上去

❤3

21 Sept 2026, 11:49 UTC≈4,030 views32 reactionsread 31 October 2026

后续版本将重新定义lspilot,不再仅限于逆向分析调试 大白话就是想干嘛就干嘛;配合MCP 插件可玩性更高,做一款全能的AI助手,你们期待吗?

👍21🥰7🆒2❤1🫡1

19 Sept 2026, 15:35 UTC≈11,600 views19 reactionsread 31 October 2026
File

新增 MCP 插件(BeanShell) 新增 跟随系统切换语言 新增 支持中国台湾语言 新增 支持中国香港语言 增加 对话中的计划模式 增加 MCP 拓展小标签 增加 项目页进程小标签 增加 终端支持chroot 重构 重新设计输入框UI 更新 BeanShell 版本依赖 更新 google/smali 至 3.0.10 修复 file_edit,file_read 修复 终端字体颜色问题 修复 MCP Web 工具 删除 Lua 及 Js 引擎 删除旧版本再安装,否则会出现一些意想不到的事情

❤12👍6😁1

7 Sept 2026, 17:38 UTC≈3,710 viewsread 31 October 2026

软件用于动态调试类仅软件开发者人群学习交流,如果你是小白并且不懂这个软件是干什么的,那么立即卸载该软件。 如果用来破解并传播至国内互联网,根据《刑法》第285条及《网络安全法》第63条,用于破解并传播即属违法,一切后果由使用者自行承担。

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

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

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

“LSPilot” (@LSPilot), 2,045 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/LSPilot.

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.