公网:天眼地址(半年内记录) 报单:提供身份证 优点介绍:出现居住地址 户籍地址 个人关联名下常用支付账号 关联名下公司 婚姻记录 人员社会人群分类等详情信息 当天回 价格不高
❤2

Channel
@zkgfpd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,187subscribers
+925 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001531636109 |
|---|---|
| Type | Channel |
| Username | @zkgfpd |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/zkgfpd |
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 12 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 01:20 | 7,187 | -13 |
| 11 Nov 2026, 16:00 | 7,200 | +2,190 |
| 7 Nov 2026, 13:14 | 5,010 | +4,595 |
| 31 Oct 2026, 12:40 | 415 | -10 |
| 25 Oct 2026, 05:01 | 425 | -16 |
| 18 Oct 2026, 14:06 | 441 | -320 |
| 12 Oct 2026, 08:37 | 761 | -1,177 |
| 5 Oct 2026, 18:57 | 1,938 | -11 |
| 28 Sept 2026, 04:56 | 1,949 | -4,154 |
| 18 Sept 2026, 08:20 | 6,103 | -19 |
| 13 Sept 2026, 23:00 | 6,122 | -14 |
| 10 Sept 2026, 01:58 | 6,136 | -41 |
| 4 Sept 2026, 15:16 | 6,177 | -13 |
| 1 Sept 2026, 06:14 | 6,190 | -32 |
| 29 Aug 2026, 04:13 | 6,222 | -12 |
| 26 Aug 2026, 12:38 | 6,234 | -6 |
| 23 Aug 2026, 08:38 | 6,240 | -9 |
| 20 Aug 2026, 04:52 | 6,249 | -3 |
| 17 Aug 2026, 14:29 | 6,252 | -2 |
| 14 Aug 2026, 14:38 | 6,254 | first reading |
40 posts held, back to 10 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 18 pages of Telegram’s post history, 20 posts per page.
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 11 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 40 (10 July 2026 – 15 November 2026) |
| Views total | 19,922 |
| Reactions total | 188 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04:45 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.
Lifetime counters from Telegram’s own channel header, read 17 November 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.
188 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 25.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 48 | 25.5% | |
| 👍 | 47 | 25.0% | |
| 👏 | 34 | 18.1% | |
| 🎉 | 31 | 16.5% | |
| 🔥 | 28 | 14.9% |
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 11 of the 40 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 188 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 10 July 2026 to 15 November 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.
Telegram’s own ‘edited’ marker: 0 of 19 posts held from the last 30 days (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).
公网:天眼地址(半年内记录) 报单:提供身份证 优点介绍:出现居住地址 户籍地址 个人关联名下常用支付账号 关联名下公司 婚姻记录 人员社会人群分类等详情信息 当天回 价格不高
❤2
开同特价 单开出近5年记录 同住人出近1-3年记录 1-3天回单
❤2
强提微信提取好友 带备注 不限行业 原始文件回单 提供微信号或手机号报单 配合版提取微信好友 带备注 需有报单微信好友 简单操作 支持一切行业 报空单 境外号扣 单子本身敏感收费不给单 好友列表敏感也可以报 出单子敏感人删除掉
❤2
全国房产 (无遗漏) 港澳台人士也出 有房出全部 空收一半给图 带抵押状态 查封状态 支持埋雷测试 保售后 默认出全国范围 不可排除 不可指定 房产 商铺 车位 宅基地 有什么出什么 报单带名字身份证 源头出单 批量来谈 注:目前的房产局房产 回单带详细门牌号 其他的什么都有 房屋产权号 地址 面积 抵押状态 查封状态 回单1-3天 不含节假日 已经稳定回单过了
❤2
近期持续收到反馈行内立案假单频出,真假混出的情况,骗子通过压低价格、真假套单博取信任频频得手。再次提醒一下各位客户 同行 ,谨慎甄别单子信息,避免上当受骗 !!!
❤2
法院判决书 提供姓名+身份证号码报单 原告或者被告都可以查 默认出最新一个案件(法院判决后的案件才能查)空收一半 不管是民事、刑事、行政处罚,只要是法院判决的都能查(不是市面上垃圾大数据版本)私聊看板
👏9❤7🎉5🔥5👍3
独家高德地图轨迹 老线回归 稳定回单 渠道在线 就秒回单 独家渠道 全网唯一 同行代理找我拿价格 利润拉满 历史所有去过地址 历史所有打车记录 高德机票记录 高德订酒店 能出酒店记录 他历史旅游记录+时间 所有导航记录 没有遗漏 概率出车牌号 只要在高德上使用过的都能显示 抓人神器 比美团 邮政 各种外卖快递都好 敏感提前说加钱出 不提前说收费不出单! 报单提供 姓名 身份证 手机号
👍24❤2
精准位置 精准移动位置 中午12点——凌晨1点 二网位置 中午12点——凌晨1点 三网位置 晚上21点——凌晨00:30分
👏9🎉8🔥3❤2👍2
微信支付宝流水 一月 三月 半年 一年 两年 三年 微支价格调整 新单重新问价
❤10🎉7👍7🔥7👏3
平台账号评论 目前只有 抖音 提供抖音号报单 能出多少出多少 提取一年内的所有评论内容 带时间 带链接 点击链接即可进入评论原帖(原视频) 杜绝造假可能 已有多名客户通过此业务发现对象不正常留言 早报早回 基本全天秒 保真不包漏
❤16👏13🔥13🎉11👍11
名下资产回完 稳定 继续上 排队3-7出 目前最好最全的法院执调渠道 银行卡微信支付宝余额基金股票保险都能出
京东商城地址。带购物详情,带单号, 6个月内: 最近1条 最近3条 6个月所有地址 当天或隔天回
❤1
Showing the 12 most recent of 40 posts we hold for @zkgfpd. 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.
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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“智库人工查档模板” (@zkgfpd), 7,187 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/zkgfpd.
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.