Channel
@sheding
On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry
315subscribers
+11 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001792126029 |
|---|---|
| Type | Channel |
| Usernames | @kenian @leichui @liehai @muqun @sheding @tianzao |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/sheding |
@sheding was previously reachable at these 2 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 14:08 | 315 | no change |
| 31 Aug 2026, 11:44 | 315 | no change |
| 31 Aug 2026, 07:56 | 315 | -1 |
| 30 Aug 2026, 22:15 | 316 | no change |
| 30 Aug 2026, 17:05 | 316 | -1 |
| 29 Aug 2026, 04:49 | 317 | +1 |
| 25 Aug 2026, 04:26 | 316 | +5 |
| 24 Aug 2026, 19:54 | 311 | -1 |
| 24 Aug 2026, 00:37 | 312 | no change |
| 23 Aug 2026, 18:27 | 312 | +1 |
| 23 Aug 2026, 16:33 | 311 | -1 |
| 23 Aug 2026, 12:54 | 312 | -1 |
| 22 Aug 2026, 23:14 | 313 | no change |
| 22 Aug 2026, 04:27 | 313 | +6 |
| 17 Aug 2026, 12:16 | 307 | no change |
| 17 Aug 2026, 11:25 | 307 | no change |
| 16 Aug 2026, 20:03 | 307 | no change |
| 16 Aug 2026, 16:17 | 307 | +1 |
| 16 Aug 2026, 08:16 | 306 | no change |
| 15 Aug 2026, 15:54 | 306 | first reading |
20 posts held, back to 7 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 April 2026. An engagement rate over an empty window would be a number about nothing.
😎PG电子游戏机器人 客户1:1定制 （正版PG接口开户） （配送日志群/后台群） 游戏部分特色功能： 1.对接okpay fllqb adqb dlqb官方商户，提现审核 2.地址归集 3.机器人内联红包发放及推广邀请 4.自定义转化USDT转RMB汇率 5.自定义设置返佣邀请比例 6.自定义设置反水比例 7.展示用户详细信息，投注，下级，充值，提现 8.广播信息 演示机器人bot联系 @haook
👋 您好，我是爱看逼机器人 🔍 使用机器人可以搜索任何您想要的视频资源，万部以上 👇 点击下方按钮立即体验
📚 记账机器人操作说明,支持功能定制 1️⃣ 基础功能 开始记账▫️开始 停止记账▫️停止 打开发言▫️上课(机器人为管理员时有效) 停止发言▫️下课(机器人为管理员时有效) 2️⃣ 群内操作人设定 增加记员▫️设置操作人 @aaa @bbb 增加记员▫️回复指定人：设置操作人 删除记员▫️删除操作人 @aaa @bbb 查看记员▫️显示操作人 全部记员▫️设置所有人 全部记员▫️取消所有人 3️⃣ 账单显示设定 账单条数▫️账单条数5 置顶开启▫️开启记账置顶 置顶关闭▫️关闭记账置顶 跟回复人▫️显示回复人 跟操作人▫️显示入账人 纯净模式▫️纯净模式（不显示回复人和入账人） 分类显示▫️开启分类 分类关闭▫️关闭分类 单个币种▫️设置汇率0 币种显示▫️设置币种AUD 4️⃣ 群内账单设定 定时日切▫️设置日切时间 入款费率▫️设置费率2 入款汇率▫️设置汇率6.8 实时汇率▫️设置实时汇率 档位调整▫️设置实时…
多语言USDT贷款授权盗U源码 支持BNB ERC TRC多链授权 这个源码查询余额的接口有问题了 自己可以修复一下 #盗U #贷款 #授权 #USDT #多链
telegram 改地址源码 变U地址 懂得下载看看吧 要升级更新 #telegram #盗U #变地址 #幽灵剪贴板
基于NodeJS开发的海外电子游戏 多款游戏 有需要的老板可以下载搭建测试 UI也完美 #BC #菠菜 #菠菜源码 #电子 #nodejs
Tabby是一个基于Electron的终端仿真器，适用于所有主要操作系统，旨在为您提供强大、现代且可定制的运行命令环境。 #工具 #软件 #Tabby #终端工具
TRC20区块链多签盗U源码 多签盗U需要鱼地址有100T才可以 直接锁死 有兴趣的可以下载研究一下 宝塔完美搭建运营 #TRC20 #区块链 #盗U #波场 #PHP
一个不错的 简约导航站源码 搭建很简单 无需复杂环境 需要的可以搞一个 html的 自己可以修改UI #导航站 #网站源码 #源码 #html
TG盗号源码 可以研究一下 自己搭建测试一下 后门自己扫一下吧 我没扫过 附带搭建教程 #telegram #盗TG #盗号 #nodejs #python
易语言程序卡密破解工具 可以破解易语言写的程序 #易语言 #破解 #卡密 #工具 #软件
一个Github上开源的 telegram投稿机器人 这个直接是一键搭建教程 有需要可以下载搞一下 别人通过机器人投稿可以发送到指定群组审核 就这一个简单的功能 #telegram #机器人 #机器人源码 #投稿机器人 #python
Showing the 12 most recent of 20 posts we hold for @sheding. 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.
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.
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.
“搞点小科技” (@sheding), 315 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/sheding.
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.