Telegram必备全能搜索机器人。 一秒记住用户名 @soso 👇点击下方按钮尝试搜搜你喜欢的频道或者群组吧~

Channel
电报导航•中文索引更方便
@dbcndh
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,065subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002314064628 |
|---|---|
| Type | Channel |
| Username | @dbcndh |
| Created | Between 1 September 2024 and 5 January 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 12 October 2026 |
| On Telegram | t.me/dbcndh |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 05:38 | 1,065 | -4 |
| 27 Sept 2026, 00:21 | 1,069 | -1 |
| 8 Sept 2026, 00:02 | 1,070 | -1 |
| 2 Sept 2026, 19:52 | 1,071 | -1 |
| 30 Aug 2026, 15:44 | 1,072 | +1 |
| 27 Aug 2026, 05:19 | 1,071 | -1 |
| 24 Aug 2026, 03:25 | 1,072 | -6 |
| 8 Aug 2026, 06:11 | 1,078 | -1 |
| 8 Aug 2026, 00:06 | 1,079 | no change |
| 7 Aug 2026, 14:22 | 1,079 | first reading |
Engagement
20 posts held, back to 5 January 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 9 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 17s
- Average length
- 13s
Measured directly from 6 videos 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
6 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 33.3% | |
| 👍 | 2 | 33.3% | |
| ❤🔥 | 1 | 16.7% | |
| 💯 | 1 | 16.7% |
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 6 of the 20 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 January 2025 to 9 February 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
𝟐𝟎𝟐𝟔已 来,我们 准备好了——用更好的自己,陪您走更远的路。 元旦快乐,新的一年,继续并肩作战,共赢更多可能!
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 Telegram必备全能搜索机器人。 一秒记住用户名 @soso 👇点击下方按钮尝试搜搜你喜欢的频道或者群组吧~
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 今日小年,炊烟袅袅,糖瓜 甜甜 。 在这温馨时分, 尘旧 拂去, 愿新 萌生,愿往后日子皆如 般糖 甜蜜, 活生 满是悠然诗意。
❤🔥1
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 岁末大寒,是结束也是开始。告别旧年的遗憾,我们带着满满的诚意和优质的产品,与您携手迈向新的春天。愿您在新的一年里,诸事顺遂,幸福安康!
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 《下个路口见》-李宇春 #音乐分享
💯1
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 Telegram必备全能搜索 一秒记住用户名 @cnyisou 👇点击下方按钮尝试搜搜你喜欢的频道或者群组吧~
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 QR 码扫描仪。应用内相机默认识别二维码,无需切换应用程序即可在您喜欢的浏览器中打开链接。 要快速打开应用内相机,请在 iOS 上从聊天列表向右滑动,或点击📷 Android 上的相机图标。 #QR码 #二维码
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 Telegram必备全能搜索 一秒记住用户名 @cnyisou 👇点击下方按钮尝试搜搜你喜欢的频道或者群组吧~
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 ⭐️文件夹中的自定义表情符号。每个 Telegram 用户都可以创建自定义聊天文件夹来组织他们的对话。 聊天文件夹支持在标题中使用表情符号- 高级用户可以添加任何自定义表情符号,使其文件夹更具表现力或更简约。
👍1
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 新年,Telegram 新功能! 2025 年才刚刚开始,Telegram 就已推出新一轮更新!现在,您可以将 20 多种热门礼物转变为收藏品,每种礼物都有独特的外观、次要特征和不同的稀有度。这些礼物可以直接在聊天中交易或发送给他人,甚至可以作为 NFT 对外共享。铸造一份独特的礼物只需要 25 颗星,涵盖 TON 区块链费用。 但这还不是全部!Telegram 还添加了: ▪️当有人加入群组或发送礼物时,快速响应服务消息 ▪️消息搜索过滤器 ▪️应用内二维码扫描 ▪️第三方验证,减少诈骗和错误信息 高级用户可以享受文件夹名称中的表情符号的更多自定义功能,同时每个人都可以受益于 Telegram 改进的隐私和安全功能。 我们很高兴与您一起开启 2025 年。敬请期待更多更新!
🔤搜索丨音乐丨翻墙丨会员代开🔤 📤点击上方对应字幕进入📤 💡TG使用小技巧 谨防盗号 限制私聊 注册和登录 两步验证 隐私设置 使用标签筛选当前频道所有相关内容 注册/登录收不到验证码 点击链接无反应 手机操作解除18+内容限制 Telegram 官方客户端下载地址 Telegram分组/文件夹 Telegram收藏夹 Telegram客服 Telegram归档 Telegram主题 Telegram限制 Telegram会员 Telegram 如何建群? Telegram 创建频道 Telegram 频道开启"评论"功能 Telegram注销 Telegram开启邮箱登录 Telegram慢速消息 Telegram消息翻译 Telegram账号限制 Telegram添加联系人 Telegram屏蔽私聊 Telegram频道身份发言 Telegram 自动删除消息 Telegram 缓存和自动下载 Telegra…
👍1
Showing the 12 most recent of 20 posts we hold for @dbcndh. 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.
Mentions
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.
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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“电报导航•中文索引更方便” (@dbcndh), 1,065 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/dbcndh.
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.