所有电商收货+寄货+退货地址 😉😉😉😉 包括淘宝 京东 抖音 拼多多 得物 已和内部美团对比过可找我拿对比结果 近一年的 一条免费 2条以上收费 手机号报单 凌晨2点发车 隔天回

Channel
冰冰【源头批发查档业务】
@zscd23
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,265subscribers
-5,763 since we began measuring on 15 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1004416402238 |
|---|---|
| Type | Channel |
| Username | @zscd23 |
| Created | 5 September 2026 — measured — dated from the channel’s first post |
| First recorded | 15 September 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/zscd23 |
Topic
Hacking & security — 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 4 October 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 03:11 | 4,265 | -736 |
| 8 Nov 2026, 13:46 | 5,001 | -542 |
| 4 Nov 2026, 23:51 | 5,543 | -212 |
| 1 Nov 2026, 21:36 | 5,755 | -702 |
| 29 Oct 2026, 12:56 | 6,457 | -555 |
| 26 Oct 2026, 19:16 | 7,012 | -560 |
| 24 Oct 2026, 01:38 | 7,572 | -786 |
| 21 Oct 2026, 02:25 | 8,358 | -889 |
| 18 Oct 2026, 02:18 | 9,247 | -496 |
| 15 Oct 2026, 12:58 | 9,743 | -298 |
| 14 Oct 2026, 12:11 | 10,041 | -337 |
| 13 Oct 2026, 00:09 | 10,378 | -23 |
| 8 Oct 2026, 13:35 | 10,401 | +16 |
| 4 Oct 2026, 00:58 | 10,385 | +35 |
| 25 Sept 2026, 07:21 | 10,350 | +118 |
| 18 Sept 2026, 23:36 | 10,232 | +200 |
| 16 Sept 2026, 14:18 | 10,032 | +4 |
| 15 Sept 2026, 11:22 | 10,028 | no change |
| 15 Sept 2026, 10:47 | 10,028 | first reading |
Engagement
23 posts held, back to 5 September 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.97%
- avg views ÷ 4,265 subscribers
- Avg views / post
- 169
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 23 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 28 October 2026 |
|---|---|
| Posts held | 23 (5 September 2026 – 28 October 2026) |
| Views total | 508 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 19:07 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 23 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 5 September 2026 to 28 October 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’s own ‘edited’ marker: 1 of 5 posts held from the last 30 days (20.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Channel name was changed to «冰冰【源头批发查档业务】»
境外人员涉案查询 😉😉😉 回执返回(大头照+护照原件+信息)命中名单后,在澜湄合作地出入境后会自动标记监控状态,包含出入境记录+开房入住登记 合作地(中国 柬埔寨 老挝 缅甸 泰国 越南)马来西亚 11 月会同步接入 下名单:10000U 起 私信看板 姓名身份证报单 当天隔天在线秒 空给图收50 @zscd001
Channel photo updated
税务局全业务 😉😉😉😉 以下任选其一 不需要有效期!不需要有效期! 不需要有效期!不需要有效期! 公司对公名下卡 遗漏小全出 公司发票 一年记录 无遗漏全出 公司财务报表 无遗漏全出 公司股东 无遗漏全出 公司员工 无遗漏全出 公司房产 无遗漏全出 公司车船 无遗漏全出 报单提供: 公司名 税号代码+法人大头+法人sfz号 空给图收费 报单联系 @zscd001
10月15号更新源头直收(最新地址类)🔜 公网水电地址 🥵🤮🫨 多地址+15u 公网宽带地址 😤🤮🫨 公网现居地址 🥵🤮🫨 京东最新多条🥵🤮🫨 七合一快递地址 🥵🤮🫨 圆通 中通 京东 邮政 韵达 申通 极兔 七合一 邮政地址单😓🫨多😢🥵🫨 当天隔天回单‼️翻车赔U 水电 宽带 认准范冰冰 比外卖划算 出单率还差不多 超级牛逼业务 代理同行来问价 @zscd001
10月15号更新源头直收(最新地址类)🔜 公网水电地址 🥵🤮🫨 多地址+15u 公网宽带地址 😤🤮🫨 公网现居地址 🥵🤮🫨 京东最新多条🥵🤮🫨 七合一快递地址 🥵🤮🫨 圆通 中通 京东 邮政 韵达 申通 极兔 七合一 邮政地址单😓🫨多😢🥵🫨 当天隔天回单‼️翻车赔U 水电 宽带 认准范冰冰 比外卖划算 出单率还差不多 超级牛逼业务 代理同行来问价 @zscd001
刑侦全头全户 😉😉😉 已测试 限量收单 文字全户空的速度上 实时户籍系统数据 之前空的/数据不实时的可上
抖音关联人 😉😉😉 抖音所有评论 😉😉😉 全网独家查小三系列 质量很高 外面出不来都可以来走独家老线 隐私/白号/私密/封禁/都可以出! 独家线 保真不保漏 当天隔天回 @zscd001
京东快递外卖一体 单地址😉😉😉 多地址 😉😉😉 半年所有😉😉😉 半年内最新记录 带购物详情带单号 基本上当天报当天回 提供:手机号报单
😀😀😀😀 秒线文字全户❤️❤️❤️ 秒线公网猎魔/补齐 ❤️❤️ 全天秒线文全 源头出单 保真不保漏!!! 😀😀😀😀😀😀 寻量大同行代理 盘口老板 催收老板 你有量我有价 欢迎拿屠龙刀来砍我 需要联系 永久nft用户名: @zscd001 业务频道 永久nft用户名: @zscd001 🔥🔥🔥🔥🔥🔥🔥🔥
特价 婚姻开秒 早8-晚8 一直秒😉😉 带登记 带字号 带历史 全网唯一周末出单渠道 全网唯一公认板子(白板) 日出500单+ 0客诉 0问题 全网公认白板婚姻 吊打一切垃圾婚姻 唯一秒线婚姻渠道 不秒不要钱
Showing the 12 most recent of 23 posts we hold for @zscd23. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“冰冰【源头批发查档业务】” (@zscd23), 4,265 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/zscd23.
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.