机器人业务范围: 01. 【👥免费群管 】 02. 【🏠免费开车】 03. 【👥电报群管|定制】 04. 【👥开车机器人 |定制】 05. 【🏠电报商城 |定制】 06. 【👩⚕️双向客服|定制】 07. 【💴TRX兑换|定制】 08. 【💰电报钱包|定制】 09. 【🔎查询USDT|定制】 10. 【💹出入款通知|定制】 11. 【📝记账助手|定制】 12. 【⭐️供需机器人|定制】 13. 【🔊广告机器人|定制】 14. 【🌻香港六🈴彩|定制】

Channel
【电报机器人】
@DBXD666888
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
-2 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 | -1001152115567 |
|---|---|
| Type | Channel |
| Username | @DBXD666888 |
| Created | Between 1 October 2018 and 30 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 8 October 2026 |
| On Telegram | t.me/DBXD666888 |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 27 Sept 2026, 16:02 | 3 | -1 |
| 11 Sept 2026, 16:38 | 4 | -1 |
| 13 Aug 2026, 01:18 | 5 | no change |
| 7 Aug 2026, 08:20 | 5 | first reading |
Engagement
20 posts held, back to 19 February 2023 — 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 10 April 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
机器人业务范围: 01. 【👥电报群管 |免费】 02. 【👥电报群管 |定制】 03. 【🏠电报商城|免费】 04. 【🏠电报商城 |定制】 05. 【👩⚕️双向客服|免费】 06. 【👩双向客服|定制】 07. 【💴TRX兑换|定制】 08. 【💰电报钱包|定制】 09. 【🔎查询USDT|定制】 10. 【📝记账助手|定制】 11. 【💹出入款通知|定制】 12. 【👽智能回复Bot|定制】 13. 【⭐️供需机器人|定制】 14. 【🔥广告机器人|定制】 15. 【🔥👻开车机器人|定制】 16. 【香港六🈴彩|定制】
Channel photo updated
Channel name was changed to «【电报机器人】»
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
🇨🇳【机器人商城】可以做什么? 是商店,可以卖货赚钱 是群管,可以屏蔽垃圾 是辅助,可以管理100+群 是广播员,可以定时推送广告 是智能客服,可以24H接待用户 是引流平台,可以投放广告进行引流 🇨🇳1分钟开个商城,稳稳收入把钱赚
Showing the 12 most recent of 20 posts we hold for @DBXD666888. 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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@DBXD666888 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 5 posts, 13 August 2026 – 13 August 2026
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“【电报机器人】” (@DBXD666888), 3 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/DBXD666888.
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.