😧☹️😋收款码流水(任何收款码) 支付宝 微信 聚合码 都可以 公户私户通杀 无上限 无上限(除了空不收 其他都收) 回单时间:当天隔天

Channel
查档 开户 手机定位 银行流水 户籍 飞火
@laojingzhang001
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
34,595subscribers
+2,828 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002180164274 |
|---|---|
| Type | Channel |
| Username | @laojingzhang001 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/laojingzhang001 |
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 9 September 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 10:42 | 34,595 | +3,010 |
| 17 Sept 2026, 12:55 | 31,585 | -192 |
| 15 Sept 2026, 09:17 | 31,777 | -137 |
| 13 Sept 2026, 21:37 | 31,914 | -155 |
| 12 Sept 2026, 00:39 | 32,069 | -320 |
| 9 Sept 2026, 18:15 | 32,389 | -381 |
| 6 Sept 2026, 12:39 | 32,770 | -331 |
| 4 Sept 2026, 00:16 | 33,101 | -325 |
| 2 Sept 2026, 13:14 | 33,426 | -83 |
| 1 Sept 2026, 14:26 | 33,509 | -6 |
| 31 Aug 2026, 16:25 | 33,515 | -72 |
| 30 Aug 2026, 18:25 | 33,587 | -14 |
| 29 Aug 2026, 16:58 | 33,601 | -9 |
| 28 Aug 2026, 16:36 | 33,610 | -5 |
| 27 Aug 2026, 19:14 | 33,615 | -10 |
| 26 Aug 2026, 20:55 | 33,625 | +1,140 |
| 25 Aug 2026, 20:42 | 32,485 | +1,516 |
| 24 Aug 2026, 21:52 | 30,969 | -82 |
| 23 Aug 2026, 09:25 | 31,051 | -65 |
| 21 Aug 2026, 19:57 | 31,116 | first reading |
Engagement
38 posts held, back to 31 July 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 97 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.3%
- avg views ÷ 34,595 subscribers
- Avg views / post
- 3,560
- 7 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 7
- of 38 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 4 October 2026 |
|---|---|
| Posts held | 38 (31 July 2026 – 4 October 2026) |
| Views total | 24,930 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Oct 2026, 10:30 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.
What this channel posts
- Photos
- 48
- Videos
- 1
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 4 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 8s
- Average length
- 8s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
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 4 of the 38 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 38 most recent posts we hold, published 31 July 2026 to 4 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
国庆期间业务回单不稳定 在这里和各位老板说下抱歉 国庆期间下单都送大头照‼️‼️
国庆节假日业务通知 持续更新 柜台及无盲流水系列 建设银行、农业银行 27号最后一车 29日全部回完 农业柜台流水和卡反 10月8日开工,10.7日可报单 邮政柜台流水和卡反 10月8日开工,10.7日可报单 工商柜台流水和卡反 正常营业 ,10月1-4日放假 中国柜台流水和卡反 正常营业,9月28日开工 广发柜台卡反 正常营业,9月28日开工 公户无盲流水 10月8日发车,可预收单 微提好友提取 正常营业 9月28日 节前最后一批 支付宝微信流水 正常营业 9月28日 节前最后一批 手机轨迹 正常营业 警务通人脸 正常营业 立案详情 正常营业 9月28日出单 公网名下卡 正常营业 9月28日出单 卡反预留系列 正常营业 不放假 出入境记录 正常营业 不放假 名下常用号 正常营业 不放假 地址类业务私信询问
银行卡反实名和预留手机号 银行卡预留手机号 银行卡反身份证 有量就有价! 批量打骨折
支付宝全系列 支付宝收款码 反手机号 支付宝收款码 反手机号+姓名 身份证 支付宝邮箱反手机号 支付宝付款订单号 反收款人+付款人信息 有量就有价! 批量打骨折
近期有人冒充老警长骗人‼️ 报单认准号码+888 06173630 Id @laojingzhang007 老警长007 被骗概不负责
银行卡反预留手机号和实名信息稳定回单 来就秒
很多业务需要身份证报单‼️ 没有身份证可通过以下渠道查询 1:通过电话号码查询 2:通过微信号查询 3:通过车牌查询 4:通过银行卡号查询 5:通过人脸识别查询 6:通过姓名+大概年龄+大概户籍地区查询 7:通过支付宝收款码查询 8:通过微信收款码查询
抖音类业务 抖音号反手机号 手机号反抖音号 抖音关联人 模版 抖音评论 模版
美团饿了么一体 报单:姓名+身份证+手机号 回三个月内最新十条收货地址 超过三个月的记录全部回空 系统如果没有十条 一条也收费 不堵车当天隔天回 很稳定
高德地图轨迹强势来袭‼️‼️ 含盖所有打车记录、地址、酒店、机票等等 报单:提供 姓名身份证手机号 录屏回单:所有打车 历史所有去过地址 历史所有打车记录 高德机票记录 高德订酒店 能出酒店记录 历史旅游记录+时间 所有导航记录 没有遗漏 概率出车牌号 温馨提醒: 没有记录不收费 敏感提前说加钱出 不提前说收费不出单! 只要在高德上使用过的都能显示
支付宝28位订单号反查 提供支付宝交易订单号 出付款人信息和收款人信息 人在就秒
Showing the 12 most recent of 38 posts we hold for @laojingzhang001. 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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“查档 开户 手机定位 银行流水 户籍 飞火” (@laojingzhang001), 34,595 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/laojingzhang001.
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.