Telegram RegisterThe public register of Telegram
Telegram profile photo for 天网调查人工频道

Channel

天网调查人工频道

@tianwangrg

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

33,741subscribers

+667 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-1003375145195
TypeChannel
Username@tianwangrg
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/tianwangrg

Growth

33,07433,77033,4227 August 2026 — 33,074 subscribers8 August 2026 — 33,087 subscribers9 August 2026 — 33,160 subscribers10 August 2026 — 33,198 subscribers11 August 2026 — 33,316 subscribers12 August 2026 — 33,418 subscribers13 August 2026 — 33,502 subscribers14 August 2026 — 33,586 subscribers16 August 2026 — 33,657 subscribers17 August 2026 — 33,770 subscribers18 August 2026 — 33,741 subscribers33,7417 August 202618 August 2026
11 measurements spanning 11 days, net +667. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 32,970–33,874 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 11:3733,741-29
17 Aug 2026, 12:2533,770+113
16 Aug 2026, 04:1833,657+71
14 Aug 2026, 18:0633,586+84
13 Aug 2026, 07:0433,502+84
12 Aug 2026, 04:0633,418+102
11 Aug 2026, 07:0233,316+118
10 Aug 2026, 04:1433,198+38
9 Aug 2026, 04:1133,160+73
8 Aug 2026, 01:1733,087+13
7 Aug 2026, 18:0133,074first reading

Engagement

10 posts held, back to 18 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.34%
avg views ÷ 33,741 subscribers
Avg views / post
2,140
9 posts measured
Reaction rate
0.101%
reactions ÷ views · ER floor
Posts in window
9
of 10 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 8 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held10 (18 July 202629 July 2026)
Views total19,240
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 00:51 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

20 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 70.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1470.0%
👍525.0%
🤮15.00%

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 9 of the 10 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 18 July 2026 to 29 July 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

29 Jul 2026, 07:59 UTC≈3,790 views4 reactionsread 18 August 2026
File

下周新版本公网名下卡 增加不良资产数据,新版本无人可以模仿,加量不加价 最稳定名下卡 隔天回单 周日休息 不良资产就是这个卡号的活跃度近期使用次数频繁,名下卡保真不保漏,系统又多少出多少! 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

3👍1

28 Jul 2026, 07:09 UTC≈3,750 views3 reactionsread 18 August 2026

五年人物轨迹 🙂 五年开同 🙂 回单:3 天左右回单 稳定出单 老版本回归 稳定且遗漏小 嘎嘎出单 😟😟😟😟😟😟😟😟😟 😵 敏感收费不给单行列😵 公检法 军人以及其家属 国有企业 明星 记者 网红 媒体 报刊 律师 总裁 研究院 董事长 上市公司等 公司法人(注册资本超过200w的) 落马退休干部 教授 教师 国家三甲医院职工 🫥云搜标记为 干部 党员 一律算敏感 不接受扯皮 别说退休多久了 现在的渠道太屌他说敏感就敏感没得办法🥲 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

3

27 Jul 2026, 07:18 UTC≈2,500 views0 reactionsread 18 August 2026
Photo

手机号码冻结封禁 四网:移动/联通/电信/广电 1-5天出结果 封禁30天后申诉不通过 相当于卡直接报废 申诉成功概率极低 结果1全停: 打不了电话 接不了电话 发不了短信 用不了流量 结果2单停:同上(区别是可以接电话) 验证 :百度核验 致电核验(仅供参考,极个别可以接电话,无法打电话用流量) 最新报单规则 不接受扯皮 报单不撤 验收以百度标记为准 当天提交 运营商同步百度1-5天 可随时欢迎自己手机号测试 没作用支持退1赔3 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

26 Jul 2026, 09:47 UTC≈1,490 viewsread 18 August 2026
Photo

个人所得税 平替社保 看工作单位 什么用处自己想 指定一年记录 天花板级别业务 带工资带单位 当天回 看工作,看敏感,看收入必备项目 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

25 Jul 2026, 07:23 UTC≈1,420 views2 reactionsread 18 August 2026
Photo

全国房产 开 首套 二套 3-5个工作日回单 空不收费 不可排除车位宅基地 无遗漏·支持埋雷打假 地区房当天回 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

1👍1

24 Jul 2026, 09:36 UTC≈1,570 views1 reactionsread 18 August 2026
Photo

警务通人脸识别 回单 只接受备注,敏感收费不回 提供照片+名字:对上默认出 提供照片+名字+地区:对上一条默认出 提供照片+名字+地区+年龄:对上一条默认出 带公网地址 带公网地址 带公网地址 有备注不对可以不出 不出不收费 精准人脸点射 美颜 照片不清晰 可能会识别错误 出单不扯皮 接受了报 ⚠️没备注姓名回5头相似度和身号 敏感收费不回 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

1

23 Jul 2026, 14:18 UTC≈1,430 views2 reactionsread 18 August 2026

京东购物记录 有多少出多少 全部保真 全部保真 几年前的都可以出!!! 全部带购物记录 当天渠道在就秒! 外面空的全部来 都来‼️ 不跟你们玩几条 直接全出 私聊找我拿版 手机号就可以报 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

1👍1

22 Jul 2026, 06:40 UTC≈1,730 views5 reactionsread 18 August 2026

【稳定】快递地址找人类 📦刑侦地址 【隔】老地址会问要不 📦文字邮政➕单号 多条【当隔天回】 📦常用大数据地址 【基本秒】 📦网警地址 数据 【1-3天回】 ❤️小关联 ❤️❤️一年内快递地址 带单号 主要为京东邮政极兔圆通,除邮政外,其他半年以上单号查不了 (对比常用地址) ❤️❤️真水电宽带地址(全部带户号账号,姓名身号手机报单)〔户主地址反查户主〕 ❤️❤️ 手机定位链接轨迹三月 隔天 ❤❤️❤️️一年内美团外卖地址 回单截止20号回完再来(不堵车了随便上,注意目前只要手机号报单,一年内记录保真不保漏) 带时间➕地址➕订单名字 每天限量,牛逼渠道,明天回 ❤️ 手机号报单,美团的跑腿,闪送都出 一条也收,敏感收费不回 ❤️❤️京东源头收单,有单号。 京东最近三个月,地址 京东商城快递,出 最新一条 最近2-3条 隔天回 文字京东三月内所有地址带单号 ❤️历史电商购物记录 ❤️一年短

3👍1🤮1

21 Jul 2026, 06:50 UTC≈1,560 views1 reactionsread 18 August 2026
Photo

@all白底无遗漏出入境10年恢复〔带国家〕空要回图收费,身号姓名大头报单 移民局二十年出入境记录】有遗漏 报单提供 姓名 身份证 照片。 ⚠️没证件没记录给图收费! 源头直收!当天稳定回单! 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

1

18 Jul 2026, 07:53 UTC≈2,520 views2 reactionsread 18 August 2026
Photo

提供车牌号,查最新车辆详细行驶轨迹信息,最多一百条。(部分带车辆照片) 价格2880元/360u 当天隔天出单 天网唯一客服:@TWRGkF 天网bao养业务https://t.me/TWJTbaoyang

1👍1

Showing the 10 most recent of 10 posts we hold for @tianwangrg. 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.

Citation-graph rank

Citation-graph rank — 415,415 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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 18 August 2026 — this entry's latest reading, not the date you are reading this.

“天网调查人工频道” (@tianwangrg), 33,741 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/tianwangrg.

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.