Telegram RegisterThe public register of Telegram
Telegram profile photo for 折腾啥

Channel

折腾啥

@zhetengsha

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

47,753subscribers

+799 since we began measuring on 6 August 2026

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

Register entry

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

Growth

46,95447,75347,353.56 August 2026 — 46,954 subscribers6 August 2026 — 46,954 subscribers6 August 2026 — 46,970 subscribers7 August 2026 — 47,092 subscribers8 August 2026 — 47,149 subscribers9 August 2026 — 47,202 subscribers10 August 2026 — 47,247 subscribers11 August 2026 — 47,297 subscribers12 August 2026 — 47,353 subscribers13 August 2026 — 47,450 subscribers14 August 2026 — 47,484 subscribers15 August 2026 — 47,563 subscribers17 August 2026 — 47,679 subscribers18 August 2026 — 47,753 subscribers6 August 202618 August 2026
14 measurements spanning 12 days, net +799. 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 46,834–47,873 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 08:4847,753+74
17 Aug 2026, 10:0447,679+116
15 Aug 2026, 20:2747,563+79
14 Aug 2026, 08:4647,484+34
13 Aug 2026, 04:1347,450+97
12 Aug 2026, 04:5847,353+56
11 Aug 2026, 04:2647,297+50
10 Aug 2026, 04:1847,247+45
9 Aug 2026, 05:0147,202+53
8 Aug 2026, 06:0647,149+57
7 Aug 2026, 04:3647,092+122
6 Aug 2026, 07:3146,970+16
6 Aug 2026, 05:1546,954no change
6 Aug 2026, 05:0846,954first reading

Engagement

90 posts held, back to 3 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 36 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.67%
avg views ÷ 47,753 subscribers
Avg views / post
3,180
90 posts measured
Reaction rate
0.102%
reactions ÷ views · ER floor
Posts in window
90
of 90 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 64 of 90 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 17 August 2026
Posts held90 (3 August 202617 August 2026)
Views total286,496
Reactions total213
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 00:55 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
13m 28s
Average length
13m 28s

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

199 reactions across 51 posts, in 9 distinct kinds. The most used accounts for 57.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11557.8%
👍5728.6%
🥰73.52%
😁63.02%
👏52.51%
👌42.01%
🔥31.51%
🤣10.503%
🫡10.503%

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

Measured over the 90 most recent posts we hold, published 3 August 2026 to 17 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

17 Aug 2026, 13:02 UTC≈1,940 viewsread 18 August 2026
Photo

Octopus: 面向个人部署的 LLM API 聚合与统一管理服务 • 主要更新了协议转换, 增加了透传, 拦截上游报错不打断 agent 客户端任务, 可视化完整的请求链路 codex 接入 octopus 后进行对话 codex 显示 working 此时 octopus 日志端就会推送一条日志 点击日志后显示重试请求详情,此时 octopus 会拦截所有的错误,不会返回给 codex, codex 仍在等待 手动选择渠道后, 渠道正常响应, 透传或者协议转换后发送给 codex 整个请求链路都是可视化的,任何错误信息都会被 octopus 拦截, 并且不会传给 codex, codex 不会因为上游错误而中止,完全不需要发送 继续 https://github.com/bestruirui/octopus 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#LLM #AI #API #聚合 #模型管理 #协议

Signed 小一

17 Aug 2026, 13:02 UTC606 views1 reactionsread 18 August 2026
Photo

Crush Cloud 机场 🌟 还没抛弃 📈 Surge 🐶 因为机场主也用 📈 Surge 🌟 IPv6 为主, 也有 IPv4 🌟 部分套餐赠送 Emby 服 ✅ 高速节点 多地区高速线路接入,下载、刷视频、日常使用都更流畅。 ✅ 晚高峰稳定 高峰期也能保持稳定连接,减少卡顿、掉速。 ✅ 流媒体解锁 支持 Netflix、Disney+、YouTube、TikTok 等常用流媒体平台。 ✅ 赠送 Emby 影视服务 部分套餐赠送 Emby 观影服务,海量影视资源,打开即看。 ✅ 专属客户端 提供客户端使用,导入简单,新手也能快速上手。 ✅ 多地区节点 覆盖香港、日本、台湾、新加坡、韩国、美国等常用地区。 ✅ 售后响应快 节点异常、订阅问题、使用问题都有客服协助处理。 ✅ 价格实惠 高性价比套餐,适合长期日常使用。 👉 欢迎注册使用 crush91.cc 📢 Telegram频道:@CrushCloud

1

Signed 一个普通的人形

17 Aug 2026, 11:00 UTC≈1,900 viewsread 18 August 2026

#互推 【音声&涩涩】永不消逝的音声 【资源分享】小声逼逼 【书籍分享】电子书资源分享 📚 【安卓黄游】安卓黄油の领域(转世重生ver)❤️ 【苹果限免】 App Store 限免应用 & ... 【小红书分享】小红薯抽象观察 【心声树洞】赛博忏悔室 【网络分享】Appinn Feed|小众软件 【科技分享】折腾啥 Powered by @Summer_Clear_Sky_Bot

Signed 冬の素雪

17 Aug 2026, 10:03 UTC≈2,060 viewsread 18 August 2026
Photo

TimeCapsuleSMB: 让老款 Apple AirPort Time Capsule 具备现代 SMB3 共享与 Time Machine 备份能力 我以为已经没人用了 • 在设备本机运行 Samba 4.24.3,支持 SMB3 认证访问,macOS 27 可直接通过 Finder 挂载共享 • 集成 Bonjour 广播与网络发现,设备会自动出现在 macOS 的“网络”与 Time Machine 备份列表中 • 提供 macOS 图形界面和 Python CLI,覆盖 SSH 启用、部署更新、健康检查与老机型开机启动补丁 https://github.com/jamesyc/TimeCapsuleSMB 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#Apple #TimeCapsule #Samba #SMB3 #TimeMachine #macOS #网络存储 #旧设备改造 #家庭实验室

Signed 小一

17 Aug 2026, 08:08 UTC≈2,240 viewsread 18 August 2026

🔗 Sub-Store 落地相关的检测脚本更新 ▎完整支持 🐿️ Egern 换成了 Egern 的节点格式 现在能用 Egern 测 VLESS 节点之类的了 🐶 🤭 Sub-Store 合集 🧐 频道资源合集 😄 恰饭推荐 💬 群组 🥰联系推广 🥰 #Sub-Store #SubStore #脚本 #节点 #订阅 #检测 #check #HTTP-META #HTTPMETA #Meta #Clash #脚本 #Node #服务器 #VPS

Signed 小一

17 Aug 2026, 02:04 UTC≈2,810 views2 reactionsread 18 August 2026
Photo

Kumone: 基于 SwiftUI 打造的原生 macOS 网易云音乐客户端 群友 @missuo 开发 • 原生 Swift 实现 weapi / eapi 加密,直连网易云接口,提供扫码登录、Cookie 持久化与稳定的账号体验 • 内置 AVPlayer 播放引擎,覆盖 Hi-Res 音质选择、同步歌词、私人漫游、媒体键与 Now Playing 集成 • 集成灰色歌曲自动匹配音源、歌单与音乐库管理,以及 Sparkle 自动更新,整体体验完整且贴近 macOS 设计语言 https://github.com/missuo/kumone 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#macOS #SwiftUI #网易云音乐 #音乐播放器 #开源项目 #GitHub #AppleSilicon

1👍1

Signed 小一

16 Aug 2026, 13:01 UTC≈3,060 views2 reactionsread 18 August 2026
Photo

Kaset: 面向 macOS 的原生 YouTube Music 与 YouTube 客户端 • 基于 Swift 和 SwiftUI 打造,提供接近 Apple Music 风格的原生界面,并支持 YouTube Music 与 YouTube 模式切换 • 覆盖播放队列、同步歌词、6 段参数均衡器、Smart Shuffle,以及播放列表、播客、历史记录等核心音乐功能 • 深度集成 macOS 媒体键、控制中心、画中画、Keyboard Shortcuts 和 AppleScript,也支持加载 uBlock Origin Lite 与 SponsorBlock 等扩展 https://github.com/sozercan/kaset 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#macOS #原生应用 #音乐播放器 #YouTubeMusic #YouTube #SwiftUI #AppleScript #

🥰2

Signed 小一

16 Aug 2026, 10:03 UTC≈2,830 views6 reactionsread 18 August 2026
Photo

cloudflare-light-blog: 基于 Cloudflare 全家桶的轻量级博客系统 • 基于 Cloudflare Workers + D1 + R2 构建,集成前台博客、后台管理和 GitHub 自动部署流程 • 内置 Markdown 编辑器、主题切换、标签云、RSS、Sitemap 和 WordPress XML 导入,适合快速搭建个人内容站 • 安全与性能配置完整,包含 HMAC 认证、速率限制、HTTP 安全头、接口缓存和 R2 图片缓存 https://github.com/SRSGMOE/cloudflare-light-blog 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#Cloudflare #CloudflareWorkers #D1 #R2 #博客系统 #个人站点 #开源项目 #GitHub

👍6

Signed 小一

16 Aug 2026, 02:00 UTC≈3,110 views1 reactionsread 18 August 2026
Photo

Glass Player: 基于 Metal 3 与 libmpv 的原生 macOS 高性能视频播放器 有点简陋啊 不如 CinePlayer • 采用 Swift 原生界面封装 libmpv,结合 Metal 3 渲染与 VideoToolbox 硬件解码,针对 Apple Silicon 做了深度优化 • 内置 39 个 Anime4K shader 和 12 组预设,适合番剧、低分辨率片源和放大场景下的实时画质增强 • 支持 HDR10、Dolby Vision、HLG 内容识别与播放,同时提供 rclone 远程媒体浏览、URL 播放和大缓存流媒体能力 https://github.com/khr898/Glass-player-macOS 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#macOS #视频播放器 #AppleSilicon #Metal3 #libmpv #Anime4K #HDR #D

1

Signed 小一

15 Aug 2026, 13:02 UTC≈3,270 views0 reactionsread 18 August 2026
Photo

airport-utility: 面向 macOS 27+ 的 AirPort Utility 重构版 • 通过 Swift 前端与 Python 协议后端重现 AirPort Utility,覆盖设备发现、网络拓扑展示和基础配置能力 • 已完成多代 AirPort Express、 AirPort Extreme 与 Time Capsule 实机测试,适合继续管理经典 Apple 路由设备 • 构建环境清晰,依赖 macOS 自带的 AppKit、 SwiftUI、 Bonjour 等组件,便于开发者编译、调试和参与贡献 https://github.com/jackhumphries/airport-utility 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#macOS #Apple #AirPort #Swift #Python #网络工具 #开源项目

Signed 小一

15 Aug 2026, 10:03 UTC≈3,000 views1 reactionsread 18 August 2026
Photo

Rapid-MLX: 面向 Apple Silicon 的高性能本地 AI 引擎 • 基于 MLX 原生优化,支持连续批处理、提示缓存和量化 KV Cache,本地推理速度表现很强 • 提供兼容 OpenAI 与 Anthropic 的 API 接口,可直接接入 Claude Code、Aider、Codex CLI 等开发工具链 • 覆盖文本、音频、视频、嵌入与工具调用场景,适合在 Mac 上快速搭建统一的本地 AI 服务层 https://github.com/raullenchai/Rapid-MLX GUI: https://rapidmlx.com/desktop 🧐 合集 💬 群组 😄 恰饭 🥰联系推广 🥰#本地推理 #模型服务 #工具调用 #AppleSilicon #MLX #OpenAI #ClaudeCode

1

Signed 小一

Showing the 12 most recent of 90 posts we hold for @zhetengsha. 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 — 31,295 of 1,548,671entries 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

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 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Voyla 搜书 | 推书| 求书
@voyla · 88,017
Telegram ranks this channel #4 of 56 here — alongside 55 others — read 17 August 2026
Legado|开源阅读|频道
@Legado_Channels · 92,879
Telegram ranks this channel #5 of 61 here — alongside 60 others — read 17 August 2026
Widget🏂软件工具资源分享
@WidgetChannel · 96,225
Telegram ranks this channel #6 of 44 here — alongside 43 others — read 17 August 2026
油油の科技软件资源分享
@youyousharechannel · 88,411
Telegram ranks this channel #10 of 43 here — alongside 42 others — read 17 August 2026
ahhhhfs|A姐分享
@abskoop · 306,835
Telegram ranks this channel #14 of 50 here — alongside 49 others — read 17 August 2026
科技圈🎗在花频道📮
@zaihuapd · 276,656
Telegram ranks this channel #14 of 40 here — alongside 39 others — read 12 August 2026
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 100,093
Telegram ranks this channel #23 of 56 here — alongside 55 others — read 15 August 2026
科学上网观察与机场测速
@jichangtj · 133,422
Telegram ranks this channel #30 of 54 here — alongside 53 others — read 15 August 2026
树洞🌳群友问❓有点意思🗳
@qunyouwen · 89,547
Telegram ranks this channel #31 of 67 here — alongside 66 others — read 17 August 2026
风向旗参考快讯
@xhqcankao · 158,946
Telegram ranks this channel #45 of 45 here — alongside 44 others — read 12 August 2026
秘密小频道(树洞)
@chxpd · 151,813
Telegram ranks this channel #50 of 51 here — alongside 50 others — read 17 August 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“折腾啥” (@zhetengsha), 47,753 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/zhetengsha.

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.