谁能p真实度比较高的手持 滴滴我一下。

Channel
过客出货通知
@weixin1002
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,865subscribers
-182 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001852762146 |
|---|---|
| Type | Channel |
| Username | @weixin1002 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/weixin1002 |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 12 Oct 2026, 16:50 | 1,865 | -19 |
| 5 Oct 2026, 15:59 | 1,884 | -8 |
| 28 Sept 2026, 02:21 | 1,892 | -36 |
| 18 Sept 2026, 16:20 | 1,928 | -7 |
| 14 Sept 2026, 11:01 | 1,935 | -1 |
| 11 Sept 2026, 06:01 | 1,936 | -10 |
| 6 Sept 2026, 01:57 | 1,946 | +8 |
| 2 Sept 2026, 00:08 | 1,938 | -10 |
| 29 Aug 2026, 17:34 | 1,948 | -10 |
| 26 Aug 2026, 09:08 | 1,958 | -8 |
| 23 Aug 2026, 16:45 | 1,966 | -4 |
| 19 Aug 2026, 23:17 | 1,970 | -18 |
| 16 Aug 2026, 17:56 | 1,988 | -48 |
| 13 Aug 2026, 07:26 | 2,036 | -23 |
| 10 Aug 2026, 08:10 | 2,059 | +12 |
| 7 Aug 2026, 11:01 | 2,047 | no change |
| 7 Aug 2026, 10:56 | 2,047 | first reading |
Engagement
20 posts held, back to 22 April 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.
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 2 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 6 of the 20 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 April 2026 to 2 August 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
帮朋友出一些 限制号支付功能正常 62数据 带资料30u 不带资料18u 最低5起拿 包小额收付测试! 先到先得 @guoke666
已卖完 有货会另行通知
出一些 限制号支付功能正常 带资料30u 不带资料15u 最低5起拿 包小额收付测试!
❤1
过客出货通知 pinned a photo
穿山甲vx协议功能列表 账密不读数据过滤密错 封号数据强开临时登录 查限制号 哪些功能被限制 查视频号是否开通/可用 批量修改密码 循环检测未修改成功密码持续修改 过滤封号数据非好友状态(搭配nu) 过滤封号数据是否短信可解(免费) 封号提链接(提解封网页) 查已登录账号最早朋友圈时间 查已登录账号最早收藏(同步收藏18位信息) 查已登录账号好友数量 一键清空已登录账号好友(好友转非好友技术) 查已登录账号注册地 查十名状态(实名名字) 查询绑定yhk开户行 Wxid替换手机格式 手机格式替换wxid 查头像(区分白头) 年卡用户新增查支付状态功能 @guoke666
不带资料 支付正常限制号有一些 现在上的来 62数据 15u出
全天24小时代过限制号支付状态 0.5每条👍👍 时速500+ 看清楚 只过限制号 @guoke666
❤1
哪个老板在做创业粉 能带滴滴 割韭菜别来。 看到效果可以付学费,可上押
过客出货通知 pinned «出可以绑定公众号的微信限制号 62登录 量大。 出以下👇👇12-19封号数据(非好友)👍 国内手机/id死密 库存4000+ 国内手机/id未sm 库存6000+ 香港护照/未 库存800+ 百起出售 一手62数据 @guoke666»
出可以绑定公众号的微信限制号 62登录 量大。 出以下👇👇12-19封号数据(非好友)👍 国内手机/id死密 库存4000+ 国内手机/id未sm 库存6000+ 香港护照/未 库存800+ 百起出售 一手62数据 @guoke666
过客出货通知 pinned «由于近期腾讯频繁修改加密方式,强开功能受到影响,烦请再次更新到穿山甲V18.1版本,本次更新从根源上彻底解决ccd加密算法问题!! 蓝奏地址:https://wwbii.lanzn.com/iVjBP3r4liva 密码:d5bp»
Showing the 12 most recent of 20 posts we hold for @weixin1002. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“过客出货通知” (@weixin1002), 1,865 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/weixin1002.
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.