滴滴最新100条 提供大头姓名身份证手机号 出最新100条滴滴数据 录频回单 不足100条只要有记录就收费 当天隔天回 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍5

Channel
@yanyanhzb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
11,141subscribers
-545 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002453334358 |
|---|---|
| Type | Channel |
| Username | @yanyanhzb |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/yanyanhzb |
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 11 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 03:17 | 11,141 | -112 |
| 5 Sept 2026, 16:15 | 11,253 | -54 |
| 3 Sept 2026, 14:01 | 11,307 | -37 |
| 2 Sept 2026, 04:55 | 11,344 | -28 |
| 1 Sept 2026, 05:18 | 11,372 | -35 |
| 31 Aug 2026, 02:11 | 11,407 | -39 |
| 29 Aug 2026, 23:54 | 11,446 | -22 |
| 29 Aug 2026, 00:35 | 11,468 | -8 |
| 28 Aug 2026, 01:32 | 11,476 | -14 |
| 27 Aug 2026, 03:53 | 11,490 | -1 |
| 26 Aug 2026, 05:17 | 11,491 | -2 |
| 25 Aug 2026, 08:05 | 11,493 | -29 |
| 24 Aug 2026, 09:36 | 11,522 | -8 |
| 22 Aug 2026, 18:48 | 11,530 | -14 |
| 21 Aug 2026, 11:18 | 11,544 | -6 |
| 20 Aug 2026, 13:05 | 11,550 | -3 |
| 19 Aug 2026, 10:23 | 11,553 | -20 |
| 18 Aug 2026, 13:56 | 11,573 | -12 |
| 17 Aug 2026, 14:34 | 11,585 | -8 |
| 16 Aug 2026, 06:36 | 11,593 | first reading |
33 posts held, back to 17 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 45 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 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 33 (17 November 2025 – 31 August 2026) |
| Views total | 29,451 |
| Reactions total | 32 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00: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.
Measured directly from 3 videos 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.
151 reactions across 30 posts, in 9 distinct kinds. The most used accounts for 48.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 73 | 48.3% | |
| ❤ | 54 | 35.8% | |
| 👏 | 6 | 3.97% | |
| 🖕 | 5 | 3.31% | |
| 🥰 | 4 | 2.65% | |
| 💩 | 3 | 1.99% | |
| 😁 | 3 | 1.99% | |
| 👎 | 2 | 1.32% | |
| 🤬 | 1 | 0.662% |
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 30 of the 33 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 151 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 33 most recent posts we hold, published 17 November 2025 to 31 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.
滴滴最新100条 提供大头姓名身份证手机号 出最新100条滴滴数据 录频回单 不足100条只要有记录就收费 当天隔天回 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍5
老客户来没二话直接下单的 货比三家 多比真实性 少比价格 多少客户因为贪图便宜 最后被骗 并且收取高额保证金等威逼利诱手段胁迫付钱 哨兵稳定经营六年! 安全稳定哦 哨兵各个项目稳步进行中! 户籍 名下资产 各种反实名 资金流水动向 欢迎咨询 大家付款要小心谨慎多核对 以保证金等名义进行二次收费的都是骗子 大家注意 减少不必要损失 特此提醒! 多少客户因为贪图便宜 最后被骗 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍2❤1
天眼查l 查档l 定位 l开房记录 l手机定位 l微信好友提取l QQ好友... pinned «找人天眼查 专业一手查档😀😃 个人户籍 身份证正反 全家户口 社保职业记录 三网手机 婚姻记录 服刑记录 开房同住 网逃查询 收款二维码反查码主 边控查询 网警地址 人脸识别 模糊找人 银行卡司法 司法口供 银行卡流水 银行卡反查 手机号定位 快递地址 美团地址 名下车 名下房 名下银行卡…»
周末爱出轨?? 怎么一到周末全是定位的兄弟 天天吃瓜啊 兄弟们看好后院 不放心的找我来看看 哨兵各个项目稳步进行中! 户籍 名下资产 各种反实名 资金流水动向 欢迎咨询 大家付款要小心谨慎多核对 以保证金等名义进行二次收费的都是骗子 大家注意 减少不必要损失 特此提醒! 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
独家高德地图轨迹 老线回归 稳定回单 渠道在线 就秒回单 独家渠道 全网唯一 同行代理找我拿价格 利润拉满 历史所有去过地址 历史所有打车记录 高德机票记录 高德订酒店 能出酒店记录 他历史旅游记录+时间 所有导航记录 没有遗漏 概率出车牌号 只要在高德上使用过的都能显示 抓人神器 比美团 邮政 各种外卖快递都好 敏感提前说加钱出 不提前说收费不出单! 报单提供 姓名 身份证 手机号 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍1
手机定位(移动联通电信广电) 用过的都说准,懂得都懂 市区能做到10米内 正常直线距离5米到50米都是正常 农村 山区 误差都会大一点 500米都有可能 温馨提醒:回地址跟链接 链接是最近的坐标图 忘周知
👍6❤1
新业务上线,停车场记录 提供信息:车牌号 通过车牌可以查询 也可以通过提供手机号给哪辆车缴费记录 3个月内的车辆出入停车场记录,涵盖几十个线上收费系统,附带关联手机号码,带经纬度,覆盖商业停车场,住宅小区收费类的停车场等,保真不保漏 在线秒回单,空不收费 节假日正常秒单!!! 比车轨更有优势,有单速度上车!!! 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍5
出入境 提供姓名证件号大头报单 当天回 回单带名下所有护照 概率带航班号 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍1
哈啰所有出行记录 录屏注册至今所有出行记录 截屏注册至今所有常用地址 报单提供:个户+哈啰账号(手机号) (账号可以在哈啰app上找回密码查看) 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
👍2
出入境 提供姓名证件号大头报单 当天回 回单带名下所有护照 概率带航班号
👍3❤1
五年医疗记录 提供:身份证号报单 回单:五年医疗记录 资料是各医院统筹后上传 接收到多少信息记录全部都出 ⚠️保真不保漏 以卫健委系统为准! 联系客服🤣 @tianyanchadangio 联系客服🤣 @tianyanchadangio 发信息给限制就联系: @tycdang_bot
❤2👍2
【手机轨迹】 复活 老版本 WIFI链接+gps轨迹,恢复。一年内所有轨迹,满5条出单收费。每天15.30之前保单当天回。 识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。
👍2
Showing the 12 most recent of 33 posts we hold for @yanyanhzb. 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.
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“天眼查l 查档l 定位 l开房记录 l手机定位 l微信好友提取l QQ好友...” (@yanyanhzb), 11,141 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/yanyanhzb.
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.