软考vip付费课程资料合集 网盘链接 https://pan.quark.cn/s/54d32f443d1e
👍2

Channel
@shuidigx
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
41,069subscribers
-705 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001172604953 |
|---|---|
| Type | Channel |
| Usernames | @fufeikc @shuidigx |
| Description | Telegram免费代理分享 Telegram机器人开发搭建 编程教程分享,网赚教程分享 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/shuidigx |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 01:44 | 41,069 | -24 |
| 30 Aug 2026, 03:23 | 41,093 | -19 |
| 29 Aug 2026, 06:24 | 41,112 | -12 |
| 28 Aug 2026, 07:38 | 41,124 | -19 |
| 27 Aug 2026, 05:27 | 41,143 | -28 |
| 26 Aug 2026, 05:34 | 41,171 | -35 |
| 25 Aug 2026, 03:34 | 41,206 | -36 |
| 23 Aug 2026, 18:30 | 41,242 | -45 |
| 22 Aug 2026, 07:08 | 41,287 | -41 |
| 20 Aug 2026, 19:01 | 41,328 | -17 |
| 19 Aug 2026, 18:52 | 41,345 | -35 |
| 18 Aug 2026, 16:43 | 41,380 | -52 |
| 17 Aug 2026, 14:58 | 41,432 | -35 |
| 16 Aug 2026, 08:57 | 41,467 | -47 |
| 14 Aug 2026, 20:16 | 41,514 | -37 |
| 13 Aug 2026, 08:16 | 41,551 | -30 |
| 12 Aug 2026, 11:45 | 41,581 | -26 |
| 11 Aug 2026, 13:16 | 41,607 | -30 |
| 10 Aug 2026, 16:11 | 41,637 | -36 |
| 9 Aug 2026, 17:02 | 41,673 | first reading |
27 posts held, back to 2 January 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 52 pagesof Telegram’s post history, 20 posts per page.
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 4 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 27 (2 January 2026 – 15 August 2026) |
| Views total | 12,950 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 05:12 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.
Lifetime counters from Telegram’s own channel header, read 31 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
62 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 62.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 62.9% | |
| 👍 | 20 | 32.3% | |
| 😈 | 2 | 3.23% | |
| 🔥 | 1 | 1.61% |
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 18 of the 27 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 62reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 2 January 2026 to 15 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.
软考vip付费课程资料合集 网盘链接 https://pan.quark.cn/s/54d32f443d1e
👍2
【CSDN-38895】uniapp陪诊小程序 网盘链接 https://pan.quark.cn/s/fc306b9f1ea9
👍1
古风美少女《小狸》角色动画制作教学 网盘链接 https://pan.quark.cn/s/51fda5908f48
👍1
《前线部署工程师:人工智能时代的客户价值交付秘籍》 百度网盘链接: https://pan.baidu.com/s/1YeBiqSSs1iX22zQc8WmpUA?pwd=sjsn 提取码: sjsn
👍1
《骗术大观-百种诈骗术揭秘》学习借鉴,避免被骗 百度链接: https://pan.baidu.com/s/1zljetNDF7-dhckt6li38lA?pwd=ceuk 提取码: ceuk
2026年最新AI全栈开发实战营(完结) 链接: https://pan.baidu.com/s/1Fu_K1l-EYhoCRETREHp2bw?pwd=cdb3 提取码: cdb3
《穷查理宝典》巴菲特推荐 他和芒格的投资与智慧 百度网盘:https://pan.baidu.com/s/1STDRjbZm7W7e5pHjUMksTQ?pwd=gs6q 提取码: gs6q 夸克网盘:https://pan.quark.cn/s/08d1d3d31e4e
@v5099 代理节点已全部更新
@kkktgbot 自助开会员机器人上线 市面最低价
👍3
https://t.me/aifaguang 今日汇总已更新 请各位老哥查看 太多了 直接去汇总频道一次看完
❤4
📢 TG书库 1.260505观海100元付费文:5月骨市行情推演,上证起于3794点的上涨行情何时见鼎?.pdf 2.洪灏260507:站在光里看半导体超级周期_3980_5682【花费时间整理‖免费分享_cunlove_cn】.pdf 3.幻幻话你知:打工人很可伶,但不值得同情.pdf 4.赢在8小时之外:匮乏感是摧毁男性能量的元凶_3980_3895【精心整理‖更多资源关注_CunWorkNotess】.pdf 5.西风的罗盘260507:财富大洗牌,我该选择,还是努力?.pdf 6.南半球聊财经260507_3980_8942【花费时间整理‖免费分享_cunlove_cn】.pdf 7.鉴茶财经院260507:光的第N波_3980_5428【耗时整理‖免费分享_cunlove_cn】.pdf 8.鉴茶财经院260506问答:关于英伟达_3980_9454【免费分享‖获取更多关注公众号_CunWorkNotess】.pd…
❤9🔥1😈1
物联网ESP8266视频教程,实操调试视频和文档资料 百度:https://pan.baidu.com/s/1-OrmpYTnFKQ3SmDPDQaYTQ?pwd=34np 夸克:https://pan.quark.cn/s/d29da5c94bcf
❤3
Showing the 12 most recent of 27 posts we hold for @shuidigx. 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 — 1,552,446 of 1,628,927entries 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.
Named by 1 registered channel — 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“教程|TG代理|机器人定制开发” (@shuidigx), 41,069 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/shuidigx.
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.