Telegram RegisterThe public register of Telegram
Telegram profile photo for 上善若水python基地

Channel

上善若水python基地

@ShangShanRuoShui520

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

52subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003968335039
TypeChannel
Username@ShangShanRuoShui520
Created30 July 2026measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/ShangShanRuoShui520

Growth

525352.57 August 2026 — 53 subscribers10 August 2026 — 53 subscribers14 August 2026 — 52 subscribers7 August 202614 August 2026
3 measurements spanning 7 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 52–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:3752-1
10 Aug 2026, 09:3153no change
7 Aug 2026, 11:3353first reading

Engagement

14 posts held, back to 30 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
551.2%
avg views ÷ 52 subscribers
Avg views / post
287
13 posts measured
Reaction rate
0.702%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 9 of 13 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 9 August 2026
Posts held14 (30 July 20269 August 2026)
Views total3,726
Reactions total25
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 09:31 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

25 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 56.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 59923996433826547431456.0%
custom 59898599046664797601144.0%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 14 most recent posts we hold, published 30 July 2026 to 9 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

9 Aug 2026, 16:55 UTC13 viewsread 10 August 2026

互推将在本月8月20号正式结束 感谢大家的支持 我们有缘再见

6 Aug 2026, 23:31 UTC16 viewsread 10 August 2026
Forwarded from @HeSuXunZiPhoto

⭐️和粟薰子PUBG官方频道(原和泉纱雾) ✈️官方频道 @HeSuXunZi 😡流畅绘制 😡触摸自瞄 😡独家菜单 😡秒刷美化 😡独家过检 😡模型渲染 ✈️官方唯一频道 @HeSuXunZi

4 Aug 2026, 21:11 UTC62 viewsread 10 August 2026
File

📱软件:pydroid3 Pydroid 是一款在 Android 设备上运行 Python 代码的集成开发环境,无需电脑即可学习和编写 Python 程序 ✅主要特点 内置 Python 3 解释器,支持 pip 安装第三方库 可离线运行代码,无需网络连接 自带代码补全、语法高亮、错误提示 支持交互式终端(REPL)和脚本编辑两种模式 可安装 NumPy、Pandas、Matplotlib 等科学计算库 ✅适用人群 学习 Python 的初学者 想随时随地在手机上写代码练习的人 需要快速测试 Python 代码片段的开发者 Disclaimer & Notice 1 . Educational Purpose Only All Python scripts, codes, and technical information shared in this channel are provided strictly for

4 Aug 2026, 13:50 UTC72 viewsread 10 August 2026

反登录机器人 更新公告🫨🫨🫨 ⭐1. 支持多账号登录 现在可以同时登录多个 Telegram 账号,每个账号独立管理、独立监听。每个账号单独分配代理。极致的模拟真实设备环境。保护你的账号安全 ⭐2. 定时巡检 定期检查账号状态,冻结或失效会立即通知你。 ⭐3. 删除账号彻底清理 删除账号后,服务器上的相关文件会被彻底清理,同时自动释放配额。 ⭐4. 稳定性优化 修复了 session 文件丢失、代理认证失败等问题 如有问题请及时反馈

3 Aug 2026, 20:54 UTC63 views2 reactionsread 10 August 2026
Photo

♥定制/开发/搭建/克隆 各类机器人! ♥支持自定义机器人创造,部署,编写源码出售等各类机器人服务 ♥现市面上已有机器人均可模仿克隆、也可以按照需求定制 ♥所有机器人支持 租 /买断 部分机器人只收取每月服务器费用 💋爆款机器人 🤖私人记账机器人 🤖能量租赁机器人 🤖TRX闪兑机器人 🤖翻译机器人 🤖消息转发机器人 🤖评论区转发机器人 🤖消息监听机器人 🤖加密货币支付机器人 🤖双向机器人 🤖自动回复机器人 🤖地址监控机器人 🤖曝光地址查询机器人 🤖频道克隆机器人 ━━━━━━━━━━━━━━ ⚠️支持各种 机器人 开发定制 ━━━━━━━━━━━━━━ ⚡⚡⚡⚡⚡ @sad1881

custom 59898599046664797601custom 59923996433826547431

31 Jul 2026, 17:04 UTC164 views4 reactionsread 10 August 2026

诈骗犯 @s5678 我们并不是诈骗犯,我们只是根据每个人的智商来分配财产

custom 59898599046664797602custom 59923996433826547432

31 Jul 2026, 16:28 UTC226 views5 reactionsread 10 August 2026

上善若水的机器人 反登录 @ShangShanRuoShuiFanDenLuBot 反入机=反登录 智能检测 价格低廉 互推机器人 @ShangShanRuoShuiHuTui_Bot 上善若水网络平台自助互推机器人 记账机器人 @ShangShanRuoShuiJiZhangBot 记账机器人支持自定义货币 快删机器人 @CC_KuaiShanBot 快删机器人 监听关键词自动删除 支持正则模式与ORC 百度智能体图片识别 五子棋机器人 @ShangShanRuoShuiWuZiQiBot 群聊内的开放五子棋机器人 支持七种AI模式 动态AI大模型训练 攻防兼备 是活跃群聊的必备神器

custom 59898599046664797603custom 59923996433826547432

31 Jul 2026, 16:08 UTC170 views4 reactionsread 10 August 2026
File

开源频道消息自动加内联按钮 半成品 有点问题 自行修复 开源频道 @t123t123tt

custom 59898599046664797602custom 59923996433826547432

31 Jul 2026, 13:10 UTC202 views2 reactionsread 10 August 2026

嫌你穷 怕你富 现在这社会 他就是这样 底层逻辑就是看不了你好 你混的比我好 我真难受 就现在挣钱吧 把肉埋饭里 少把菜往出端 别让他看见 你吃8个菜 吃6个菜你别让他看见 你要凡要是转过头去 他就得一口吐你 吐你菜里 你就直接一碗大米饭端上来 兑点榨菜 哎看着没那逼样的 看没看着 那逼样的 大米饭就榨菜呢 哎他这会 他就不生气了

custom 59898599046664797601custom 59923996433826547431

31 Jul 2026, 12:12 UTC193 views1 reactionsread 10 August 2026
Photo

🔥 大量高价收购 Telegram +687 地区账号 长期稳定收购,诚信交易,秒回复。 😀 只收优质账号 • 靓号 • 情侣号 • 生日号 • 豹子号 • 连号 • 注册 3 年以上老号 💰 根据账号质量、注册时长、号码号段综合评估价格,优质账号价格可直接拉满。 ❌ 协议号 / API 号勿扰 ❌ 骗子、天价报价勿扰 ❌ 交易前需验号,不接受验号请勿联系 ✔️ 官方频道:@t123t123tt ✔️ 官方客服:@sad1881 长期收购,欢迎老板来聊,价格合适可长期合作。

custom 59923996433826547431

31 Jul 2026, 10:28 UTC142 views1 reactionsread 10 August 2026

😀😀😀😀😀😀😀 ❤️❤️❤️❤️❤️⚡️⚡️⚡️⚡️⚡️ 官方代开飞机会员 单月【5u】 😄高级会员【3个月14U】 😄高级会员【6个月22U 】 😄高级会员【12个月35U 】 😄【付款成功用户名私信发我】 😄各种礼物代购 😄用户名上链与代实名 😄python脚本定制 网站制作 😄僵尸粉 30/60/90/365不掉 😄频道专业互推引流业务 一切 😄 @sad1881 查询会员时间 点击拉到最底下 🧐🧐🧐🧐🧐🧐🧐🧐

custom 59923996433826547431

30 Jul 2026, 23:46 UTC233 views2 reactionsread 10 August 2026
File

开源TG BOT自定义接入Emoji 通过tg-html实现自定义接入图标 支持所有会员图标 转发请带频道 @t123t123tt 密码 @t123t123tt 定制脚本联系 @sad1881

custom 59898599046664797601custom 59923996433826547431

Showing the 12 most recent of 14 posts we hold for @ShangShanRuoShui520. 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 — 879,989 of 1,480,975entries 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

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.

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

“上善若水python基地” (@ShangShanRuoShui520), 52 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ShangShanRuoShui520.

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.