有缴纳过代理费但是自身销号或未保存联系方式等原因无法联系我的 代理一次缴纳终身有效,请任何时间联系我,即使退出这个行业也会负责到底 @LoveAdBot1
Channel
@chadang1 Loveadbot1 唯一ID 谨防冒充
@chadang1
On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
21subscribers
+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 | -1001427084261 |
|---|---|
| Type | Channel |
| Username | @chadang1 |
| Created | 2 July 2021 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/chadang1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 04:27 | 21 | +1 |
| 16 Aug 2026, 02:58 | 20 | +1 |
| 11 Aug 2026, 17:01 | 19 | no change |
| 7 Aug 2026, 01:06 | 19 | first reading |
Engagement
7 posts held, back to 2 July 2021 — 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 7 posts for this entry, the most recent from 19 October 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
【超级搜索】 ⭐️置顶大额付费广告认证⭐️ 🥇{社工}、{数据}、{中文}等关键词,排行第一🥇 🔥两年信誉保障,全Telegram行业第一!(频道运营时间为准,事实可靠,非空口无凭) 👍主频道内,大量靠谱案例信誉证明👍 @LoveAdBot1 别问在不在,直接说问题! 被拉黑联系 @Loveadbot 老频道均因行业问题被官方冻结
查档认准群置顶官方押金担保推荐信誉商家,有问题直接私聊10人,在群里问的结果就是100%被骗子盯上。 有问题别在群里问❗️❗️❗️问商家 有问题别在群里问❗️❗️❗️问商家 有问题别在群里问❗️❗️❗️问商家 注意 群推荐查档在任何情况下 不会 不会 不会 主动私聊任何人 商家都不会主动找你 主动私聊你的都是骗子 私聊你的,100%是冒充狗 认准 看清楚❗️❗️❗️❗️❗️
Sticker, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
Channel created
Showing the 7 most recent of 7 posts we hold for @chadang1. 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.
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
@chadang1 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 1 post, 12 August 2026 – 12 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“@chadang1 Loveadbot1 唯一ID 谨防冒充” (@chadang1), 21 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/chadang1.
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.