Telegram RegisterThe public register of Telegram

Channel

🎉 Efficiency资源干货全收录

@quanshoulu

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

16,714subscribers

+1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001178591807
TypeChannel
Username@quanshoulu
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/quanshoulu

Growth

16,70916,72016,714.56 August 2026 — 16,713 subscribers7 August 2026 — 16,713 subscribers8 August 2026 — 16,720 subscribers9 August 2026 — 16,718 subscribers10 August 2026 — 16,716 subscribers12 August 2026 — 16,709 subscribers14 August 2026 — 16,711 subscribers15 August 2026 — 16,714 subscribers16,7146 August 202615 August 2026
8 measurements spanning 8 days, net +1. 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 16,707–16,722 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 04:5816,714+3
14 Aug 2026, 00:2516,711+2
12 Aug 2026, 21:5416,709-7
10 Aug 2026, 18:1516,716-2
9 Aug 2026, 20:1116,718-2
8 Aug 2026, 18:1016,720+7
7 Aug 2026, 17:3716,713no change
6 Aug 2026, 22:0116,713first reading

Engagement

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

ERR · 30 days
0.922%
avg views ÷ 16,714 subscribers
Avg views / post
154
104 posts measured
Reaction rate
0.658%
reactions ÷ views · ER floor
Posts in window
104
of 104 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. It is computed over the 3 of 104 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held104 (4 August 202614 August 2026)
Views total16,023
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 03:04 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

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.0%

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

Measured over the 104 most recent posts we hold, published 4 August 2026 to 14 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.

Recent posts

14 Aug 2026, 11:54 UTC157 viewsread 15 August 2026

📢导航站收录更新通知! #文档知识库 #知识库 站点名称: AI 电商基础从入门到掌握 描述: 面向电商从业者的免费AI课程,涵盖Prompt工程、智能体设计、成本优化,提供系统学习路径。 链接: https://sgxueai.com/slides/home 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:52 UTC155 viewsread 15 August 2026

📢导航站收录更新通知! #运营工具 #媒体运营 站点名称: 发推素材 - X增长工具 描述: X创作者工具集合,提供发推素材、热门话题监控、流量分析等功能,帮助用户发现内容创作灵感。 链接: https://xgrowth.tools/tweet-ideas 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:51 UTC140 viewsread 15 August 2026

📢导航站收录更新通知! #电商·AI #电商外贸 站点名称: 箱包AI商品图工作台 描述: 面向箱包电商团队的AI商品图处理工具,支持智能调色、生图、透明抠图及唯品会/京东套图整理。 链接: https://github.com/mengqixi/Sino_gpt 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:50 UTC114 viewsread 15 August 2026

📢导航站收录更新通知! #AI·知识库·产品 #AI新时代 站点名称: DevNest 描述: DevNest 是一款面向开发人员的本地个人工作台,整合任务管理、代码片段、知识库和 AI 助手,数据存于本地 SQLite,支持离线使用,可打包为 Windows 应用。 链接: https://github.com/ylxylxylx/DevNest 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:48 UTC105 viewsread 15 August 2026

📢导航站收录更新通知! #电商·AI #电商外贸 站点名称: 跨境电商商品图AI工作台 描述: 面向 Amazon 与 TikTok Shop 的跨境电商商品图 AI 工具,支持图片生成、A+ 策划、拆图反推、VOC 评论分析,提供 Windows 桌面端。 链接: https://github.com/china-luo/ImageStudioRemasteredVersion 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:47 UTC96 viewsread 15 August 2026

📢导航站收录更新通知! #效率生产力 #App精选 站点名称: 言落 — 本地优先的 macOS 语音桌面应用 描述: 一个开源的 macOS 语音桌面应用,支持语音输入和本地处理,实现开口出稿和派活。 链接: https://github.com/Sherlockouo/yanluo 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:46 UTC83 viewsread 15 August 2026

📢导航站收录更新通知! #RSS阅读 #极客订阅 站点名称: 拾阅 - Windows 桌面 RSS 阅读器 描述: 拾阅是一款专注阅读体验的 Windows 桌面 RSS 阅读器,提供三栏式界面、正文清洗、图片懒加载、摘录收藏与网页快照保存等功能。 链接: https://github.com/idkwhatimdoing62/shiyue-rss 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:46 UTC73 viewsread 15 August 2026

📢导航站收录更新通知! #AI·写作 #AI新时代 站点名称: 落笔 描述: 落笔(Loby)是一款本地优先、以 Markdown 为核心、面向 AI 协作的专业写作桌面应用,支持跨平台(桌面端)使用。 链接: https://github.com/GeekMai90/Loby 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:45 UTC71 viewsread 15 August 2026

📢导航站收录更新通知! #摄影聚焦 #媒体创作 站点名称: Pocket4自动Rec709 转换工具 描述: Windows 图形工具,通过 SMB 自动接收 DJI Osmo Pocket 4 视频,传输完成后自动应用 D-Log 到 Rec.709 LUT 并使用 FFmpeg 和 NVENC/QSV/ProRes 输出高质量视频。 链接: https://github.com/0makinoruki0/Pocket4-Auto-Rec709 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:44 UTC74 viewsread 15 August 2026

📢导航站收录更新通知! #AI·API·商店 #AI新时代 站点名称: 模眼 - AI供应商与大模型API中转站监测平台 描述: 模眼是一个持续监测AI供应商的模型覆盖、价格、分组倍率与充值规则的平台,支持供应商广场、模型筛选、价格对比、模型验真及收藏订阅等功能。 链接: https://okmoyan.com/ 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:43 UTC71 viewsread 15 August 2026

📢导航站收录更新通知! #剪辑能手 #媒体创作 站点名称: AgentPlay — AI时代本地智能媒体工作台 描述: AgentPlay是一款本地智能媒体工作台,支持可靠播放、实时字幕翻译、视频分析与原创重构,并开放模型接入,适合媒体创作者使用。 链接: https://github.com/wg5759/AgentPlay 前往导航: www.noisedh.cn 或 www.noisedh.link

14 Aug 2026, 11:42 UTC70 viewsread 15 August 2026

📢导航站收录更新通知! #剪辑能手 #媒体创作 站点名称: VideoTrace 视频溯源解析工具 描述: VideoTrace是一款支持本地文件或B站、YouTube、抖音等链接上传的视频溯源、智能解析与深度理解工具,提供专业版功能。 链接: https://videotrace.online/ 前往导航: www.noisedh.cn 或 www.noisedh.link

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

Citation-graph rank

Citation-graph rank — 885,897 of 1,350,102entries 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.

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.

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

“🎉 Efficiency资源干货全收录” (@quanshoulu), 16,714 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/quanshoulu.

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.