Messages in this channel will be automatically deleted after 1 day

Channel
百万的小窝
@kbYYDS666
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
7,097subscribers
-89 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001739538407 |
|---|---|
| Type | Channel |
| Username | @kbYYDS666 |
| Description | 频道主:@dagainb |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/kbYYDS666 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 00:01 | 7,097 | -86 |
| 7 Aug 2026, 18:58 | 7,183 | -3 |
| 7 Aug 2026, 11:30 | 7,186 | no change |
| 7 Aug 2026, 11:18 | 7,186 | first reading |
Engagement
18 posts held, back to 12 September 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 10 pagesof 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 18 posts for this entry, the most recent from 14 September 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈1,330
- Videos
- ≈24
- Links
- ≈1,040
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
晚晚手拔价格如下 无风险不封卡 一个小时1080元支持vx zfb结账 新人做单多➕28块钱 新人一起一单有1️⃣1️⃣0️⃣8️⃣元 分钟计时报一分钟都有钱 做单联系 @wanwan99000 双向联系 @wan789bot 频道—https://t.me/bgpd01
🚬XL和平加速器[适配新赛季] 🌟搭配直装/插件/文件可稳定上分 ⭐独家封包规则 封包自动处理 💎维护更新内容都会在频道内通知 ✅1.公益账号密码 XLDK888 ✅2.公益账号密码 XL123 反馈加时长→ @aiIang https://www.123912.com/s/Uzuovd-aO1NH 👉〔点ai智能处理或手动勾选〕 🔘官方频道 @XLDK888 🔘官方频道 @XLDK888 🔘官方频道 @XLDK888
⭐内部群禁止泛滥,速度进入 https://t.me/bgpd01 https://t.me/bgpd01 https://t.me/bgpd01 ⚠️只开放二小时⚠️ 准备更新全网最牛逼的文件和美化.以及开户教程
我操他妈的电报上骗子怎么这么多啊!!直到我遇到 @bgpd01 他我才知道一小时可以挣1475元 目前已经拿下苹果16了
晚晚手拔价格如下 无风险不封卡 一个小时1080元支持vx zfb结账 新人做单多➕28块钱 新人一起一单有1️⃣1️⃣0️⃣8️⃣元 分钟计时报一分钟都有钱 做单联系 @wanwan99000 双向联系 @wan789bot 频道—https://t.me/bgpd01
结账➕1️⃣1️⃣1️⃣持续稳定结账中 有需要私信就行主打分钟课结报多少结多少
想赚点零花钱的兄弟们可以来联系了⬆️⬆️ 没有任何风险 做完秒结账 稳定结账上面有反馈图. 这个项目不是只能做一次,而是每天都能做,收到很多人问能做几次,统一回复:无数次,天天都能做
投票:你们有没有亩 看见不投票死全家
想赚点零花钱的兄弟们可以来联系了⬆️⬆️ 没有任何风险 做完秒结账 稳定结账上面有反馈图. 这个项目不是只能做一次,而是每天都能做,收到很多人问能做几次,统一回复:无数次,天天都能做
晚晚手拔价格如下 无风险不封卡 一个小时1080元支持vx zfb结账 新人做单多➕28块钱 新人一起一单有1️⃣1️⃣0️⃣8️⃣元 分钟计时报一分钟都有钱 做单联系 @wanwan99000 双向联系 @wan789bot 频道—https://t.me/bgpd01
结账➕1️⃣1️⃣1️⃣持续稳定结账中 有需要私信就行主打分钟课结报多少结多少
Showing the 12 most recent of 18 posts we hold for @kbYYDS666. 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.
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
@kbYYDS666 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 2 posts, 8 August 2026 – 11 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“百万的小窝” (@kbYYDS666), 7,097 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/kbYYDS666.
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.