Telegram RegisterThe public register of Telegram

Channel

后备隐藏能源

@houbei108

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

4subscribers

+0 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-1001347123127
TypeChannel
Username@houbei108
Created1 June 2021measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/houbei108

Growth

47 August 2026 — 4 subscribers13 August 2026 — 4 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:174no change
7 Aug 2026, 08:364first reading

Engagement

17 posts held, back to 1 June 2021the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 9 July 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
3
Links
6

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
39m 28s
Average length
39m 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.

Recent posts

16 Jun 2021, 06:43 UTC349 viewsread 13 August 2026

Surge/Clash/QuantumultX规则 * 神机规则: https://github.com/DivineEngine/Profiles/tree/master * lhie1洞主的规则: https://github.com/lhie1/Rules/tree/master * GeQ1an的规则: https://github.com/GeQ1an/Rules/tree/master * blackmatrix7的规则: https://github.com/blackmatrix7/ios_rule_script/tree/master/rule * NobyDa的规则: https://github.com/NobyDa/ND-AD 群组 @yxbjx 频道 @YinxiangBiji_News

16 Jun 2021, 06:43 UTC309 viewsread 13 August 2026

Surge/Clash/QuantumultX/...转换 API: * https://github.com/0KABE/ConfConvertor * https://github.com/KOP-XIAO/QuantumultX-Surge-API * https://github.com/Fndroid/jsbox_script/wiki/开放接口使用及说明 * https://github.com/tindy2013/subconverter/blob/master/README-cn.md * https://subcon.py6.pw * https://sub.dler.io * https://bianyuan.xyz * https://sub-web.wcc.best * https://api.nameless13.com * https://ytoo.now.sh * https://agwa.page

16 Jun 2021, 06:43 UTC288 viewsread 13 August 2026

发几个机器人 点击"→"后面的 ID 即可进入. 自动删除'推广/广告'消息 → @keyworddel_bot Vultr 助手 Bot → @vultr_helper_bot Telegram 权限管理 Bot → @autopm_bot 自动回复Bot → @keyword_reply_bot 接收和回复 Gmail → @GmailBot 搜索引擎搜索 → @letmebot Telegraph 文章管理 → @telegraph InstantView 生成姬 → @ChnInstantViewBot 抽奖助手 → @cnLottery_bot 智能合租机器人 → @daixiahu_bot 删除加群退群消息 → @AntiServiceMessage_Bot 删除命令 → @AntiCommandBot 解除频道消息在群组的置顶 → @areply_bot 用机器人控制机器人 → @Manybot @Contro

16 Jun 2021, 06:43 UTC237 viewsread 13 August 2026

发几个频道 点击"→"后面的 ID 即可进入. Telegram 中文 NEWS → @YinxiangBiji_News Vultr News → @vultr_news Telegram 创始人频道 → @durov Telegram 抽奖活动导航 → @Lottery_home Surge 开发者的频道 → @yachme Surge 新闻 → @surgenews Shadowrocket 新闻 → @ShadowrocketNews Quantumult X 新闻 → @QuanXNews Quantumult X 教程 → @QuanX_API 毒药测速 → @DuyaoSS V1测速 → @V1_BLOG BGP测速 → @BGP2019 Newlearnerの自留地 → @NewlearnerChannel APPDO 数字生活指南 → @AppDoDo 不求甚解 → @fakeye  Apple Nuts

16 Jun 2021, 06:43 UTC197 viewsread 13 August 2026

发几个群组 点击"→"后面的 ID 即可进入. Telegram 中文社群 → @yxbjx Telegram 中文圈 → @tgzhcn Vultr 中文社群 → @vultr_group 机场群 → @rixCloud_User Surge 交流 → @loveapps Surge Pro → @SurgePro Quantumult X → @QuanXApp Shadowrocket → @ShadowrocketApp NewlearnerのIT社群 → @NewlearnerGroup 不求甚解 → @fakeye_clinic 大学联盟 → @UniversityAlliance 输入法讨论群 → @IME_zhCN 小众软件 → @appinn 少数派 → @sspai_group Price Tag Friends → @pricetagapp 科技花 → @zaihuachat App 种草群 → @ap

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

Forward network

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

“后备隐藏能源” (@houbei108), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/houbei108.

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.