抖音类业务 抖音号反手机号🤪🤔🙂 手机号反抖音号😴😄🤔🙂 抖音关联人😴😁🤔🙂 模版 抖音评论🤪🤔🤔🙂 模版 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音

Channel
老警长|机主|法人|银行卡流水|
@laojingzhang
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
13,691subscribers
+366 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002054035732 |
|---|---|
| Type | Channel |
| Username | @laojingzhang |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/laojingzhang |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 18 Sept 2026, 00:18 | 13,691 | -83 |
| 15 Sept 2026, 20:01 | 13,774 | -121 |
| 14 Sept 2026, 05:55 | 13,895 | -133 |
| 12 Sept 2026, 13:17 | 14,028 | -122 |
| 10 Sept 2026, 08:00 | 14,150 | +935 |
| 7 Sept 2026, 03:40 | 13,215 | -164 |
| 4 Sept 2026, 12:20 | 13,379 | -58 |
| 2 Sept 2026, 21:35 | 13,437 | -83 |
| 1 Sept 2026, 21:45 | 13,520 | -28 |
| 1 Sept 2026, 00:17 | 13,548 | -11 |
| 31 Aug 2026, 02:35 | 13,559 | -39 |
| 30 Aug 2026, 05:48 | 13,598 | -101 |
| 29 Aug 2026, 05:24 | 13,699 | -139 |
| 28 Aug 2026, 04:34 | 13,838 | -79 |
| 27 Aug 2026, 02:55 | 13,917 | -67 |
| 26 Aug 2026, 02:56 | 13,984 | +1,470 |
| 25 Aug 2026, 04:56 | 12,514 | -155 |
| 23 Aug 2026, 23:17 | 12,669 | -143 |
| 22 Aug 2026, 05:28 | 12,812 | -220 |
| 20 Aug 2026, 23:16 | 13,032 | first reading |
Engagement
36 posts held, back to 1 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 47 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 22.6%
- avg views ÷ 13,691 subscribers
- Avg views / post
- 3,090
- 9 posts measured
- Reaction rate
- 0.093%
- reactions ÷ views · ER floor
- Posts in window
- 9
- of 36 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. It is computed over the 2 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 36 (1 July 2026 – 2 September 2026) |
| Views total | 27,799 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 20:08 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
13 reactions across 9 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 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 13 of the 36 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 1 July 2026 to 2 September 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
满血版带所有最新微信号微提 出单:😴😱🤔🤔🤔🙂 提取微信好友带备注,满血版无需再次转换 所有行业都支持,带行业报单 直接出满血版无需转换,吊打残血版 提供微信号或者手机号都可以报单,带所有微信转换,提取人和列表里的人不可以有铭感,一律发现收费不出单,,取失败可以试试配合版,一周内回单! 微提配合版本:😴🤫🤔🤔🤔🙂 只需要提供微信号码 我这边安排人加好友,加成功了就能直接提取,或者 报单的人 有这个人的微信,报单人不可以铭感,提取列表里有铭感删掉可以给单 微提不带备注:😴🤫🤔🤔🤔🙂 报单:提供微信号/手机号,报单告知产业 老规矩 依旧保真不保漏 本人以及好友列表敏感收费不给单 境外号不行 出不来 报境外扣🤫🤪🤔🤔🙂 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道
❤2
美团饿了么一体 😴😄🤔🤔🙂 报单 姓名+身份证+手机号 回三个月内最新十条收货地址 超过三个月的记录全部回空 系统如果没有十条 一条也收费 不堵车当天隔天回 很稳定 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
高德地图轨迹强势来袭‼️‼️ 含盖所有打车记录、地址、酒店、机票等等 价格 :☺️🤔🤔🙂 报单:提供 姓名身份证手机号 录屏回单:所有打车 历史所有去过地址 历史所有打车记录 高德机票记录 高德订酒店 能出酒店记录 历史旅游记录+时间 所有导航记录 没有遗漏 概率出车牌号 温馨提醒: 没有记录不收费 敏感提前说加钱出 不提前说收费不出单! 只要在高德上使用过的都能显示 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
❤1
银行卡反带余额 只有 工商银行 邮政银行 农业银行 中国银行 平安银行 广发银行 其他银行📚📚 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
支付宝28位订单号反查🤪🤔🤔🙂 提供支付宝交易订单号 出付款人信息和收款人信息 人在就秒 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
单独大头☺️🤔🙂 带户籍地的个护😁🤔🙂 身份证正反面😴🤔🤔🙂 律所/公安盖章😴🤔🤔🙂 以上所有内容均要提供身份证报单。 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
医疗记录🤫🤔🤔🙂文档回单 全网正规的医院基本都能出 想看女朋友,前女友 相亲对象有没有打胎吃药的可以来出这个了。 ‼️5年内医疗记录 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
查档模版点这里 🦠🦠🦠 😊🙂↔️🙂☠️🙂 📚📚📚📚👋📚📞 点击蓝色文字,一键直达查询模板 或点击置顶消息回到界面 🧐🧐🧐模板仅供参考,每个时间段都会有微小区别。下单前联系客服 👀点我了解简要查档说明:查档小提示 个人信息类目 个人户籍 历史全家户籍 婚姻记录 带头全家户籍 小关联 社保工作单位 征信报告 三网手机号 医疗记录 人脸识别 名下资产 全国名下房 学籍学历 名下支付宝 名下银行卡 出入境记录 模糊找人 文字猎魔 社交账号反查 微信反查绑定手机号和实名 抖音反查 微信公众号提取 抖音关联人 名下社交账号 公网小红书反 社交账号评论 微信提取好友 微信聊天记录 支付宝订单号…
三合一名下卡 🤫🤪🤔🙂 包括名下银行卡 名下车 名下企业 背调首选 性价比高 姓名 身份证报单 当天隔天回 😀保真不保漏 遗漏很少 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
老警长常规查档业务及价格 个人户籍☺️🤔🙂起 全家户籍😴🤪🤔🙂起 名下常用手机号😁🤔🙂根据银行卡预留手机号出单 名下三网手机号😴🤔🤔🙂 手机定位😴😴🤔🤔🙂起 模糊找人😴☺️🤔🙂 邮政快递地址😄🤔🙂起 七合一快递地址🤫😄🤔🙂 名下所有银行卡🤪🤔🤔🙂 手机号反机主😴🤔🤔🙂起 名下社交账号😴😄🤔🙂 微信提取好友😴🤫🤔🤔🤔🙂 社保工作单位😴🤫🤔🙂起 个人征信😱🤔🤔🙂 抖音反绑定手机号😱🤔🙂 微信聊天记录📚📚 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
🫤🤢🤔开房及同住人涨价‼️单开房和飞火停收 飞火可以咬咬牙上人物轨迹‼️ 5年开房同住😴😴☺️🤔🤔🙂 5年人物轨迹😄☺️🤔🤔🙂 5年单开房记录☺️🤔🤔🤔🙂📚📚 5年飞火记录🤪🤔🤔🤔🙂📚📚 😀😀😀铭感收费不出单!!! 🤭所有业务支持👩⚕️5️⃣🩺🛒✈️🧘♂️8️⃣6️⃣💼 😊🙂↔️🙂☠️🙂 ➕点击联系 @laojingzhang007 ➕双向联系 @laojingzhang_bot ➕永久频道 @laojingzhang 老警长拼音
Showing the 12 most recent of 36 posts we hold for @laojingzhang. 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.
Posts edited after publishing
@laojingzhang edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 15 August 2026
- Most recent edit
- 15 August 2026
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“老警长|机主|法人|银行卡流水|” (@laojingzhang), 13,691 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/laojingzhang.
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.