THwRUxy6XmYL33CujgJXCCYP6czKmZnadk

Channel
叮当猫售后
@all666666all
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
134subscribers
-3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001931743276 |
|---|---|
| Type | Channel |
| Username | @all666666all |
| Created | 13 April 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/all666666all |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 14:46 | 134 | -3 |
| 8 Aug 2026, 23:16 | 137 | no change |
| 8 Aug 2026, 03:17 | 137 | first reading |
Engagement
13 posts held, back to 13 April 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 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 13 posts for this entry, the most recent from 1 November 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
充值地址⬆️ 充值后提供充值成功截图及自己的永久id给人工客服 @DingDangKF 即可
🎉庆祝万圣节 🎉充值季卡优惠促销 🎉季卡原价 160u/季 现130u/季 🎉年卡原价 600u/年 现500u/年 🎉参与联系客服
❗️❗️最后一次通知 近日客户反应原bot充值不到账 因为原充值系统维护人员失联 近日充值未到账的可以补缴升级为季卡 年卡等 持转账截图联系人工客服 @DingDangKF
这种傻子以后离远点儿 刚开始骂我 后来又求我 叮当猫不差你这一个客户 自己想想为什么不给你开通!
现开放叮当猫API使用权 800u/月 2200u/季 8000u/年 也可帮忙对接维护bot 价格另议 以上业务联系
需要查档请联系人工客服 @DingDangKF
关于客户问为什么 为什么不把新机器人公开 1.公开后会涌入很多竟对的群体社工库 捣乱 2.现已改为付费社工库 白嫖的人勿入
充值地址⬆️ 充值后提供充值成功截图及自己的永久id给人工客服 即可
THwRUxy6XmYL33CujgJXCCYP6czKmZnadk
原叮当猫 @DingDangCats_Bot bot管理者账号被强制消除 已不再运行 由于白嫖的用户太多 导致服务器经常拥堵 现推出新的叮当猫付费🤖️ 新版机器人回应更快 只为付费人群使用 充值vip后可享受无限制查询! 月卡 60u 季卡 160u 年卡 550u
💖 实时更新 #信息加密 #隐私保护 #防御泄露 #安全上网 #现有数据 😄 腾讯密保 😢 微博绑定 ❤️ 搜云数据 ❤️ 机主数据 😀 学习通库 ❤️ 游戏绑定 📦 快递数据 ❤️ 微信数据 😫 支付宝库 😵 麦当劳库 ❤️ 志愿数据 ❤️ 四要素库 ❤️ 二要素库 ❤️ 邮箱数据 🗂 三要素库 🖥 论坛数据 ❤️ 学籍数据 🐱 G站数据 😪 肯德基库 ❤️ 购物订单 ❤️ 抖音数据 🐦 推特中国 😵 快手数据 😫 病人数据 😵 工商个体 🚙 车主数据 ❤️ 脸书中国 ❤️ 企业数据 💳 银联数据 🥰 上海公安 ❤️ 亚马逊库 📲 多邻国库 ❤️ 金山数据 ❤️ 贝宝数据 😢 贴吧数据 😜 知乎数据 😢 B站数据 ❤️ 编程猫库 🤮 CSDN 库 🤢 饿了么库 😂 美团数据 🤕 九一数据 ❤️ IMEI数据 📲 可画数据
Showing the 12 most recent of 13 posts we hold for @all666666all. 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 — 898,867 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.
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.
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
@all666666all 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 3 posts, 9 August 2026 – 9 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“叮当猫售后” (@all666666all), 134 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/all666666all.
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.