Telegram RegisterThe public register of Telegram
Telegram profile photo for 天网频道模板

Channel

天网频道模板

@TWMB_1

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,621subscribers

+757 since we began measuring on 10 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004332032182
TypeChannel
Username@TWMB_1
CreatedBetween 1 June 2026 and 9 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live4 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/TWMB_1

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

8641,6211,242.510 September 2026 — 864 subscribers10 September 2026 — 864 subscribers12 September 2026 — 929 subscribers25 September 2026 — 1,338 subscribers4 October 2026 — 1,621 subscribers10 September 20264 October 2026
5 measurements spanning 24 days, net +757. 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 750–1,735 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 17:591,621+283
25 Sept 2026, 07:211,338+409
12 Sept 2026, 17:41929+65
10 Sept 2026, 18:22864no change
10 Sept 2026, 17:47864first reading

Engagement

11 posts held, back to 9 August 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.17%
avg views ÷ 1,621 subscribers
Avg views / post
19.0
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 11 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 September 2026
Posts held11 (9 August 2026 – 10 September 2026)
Views total19
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Sept 2026, 18:22 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

Video runtime
1m 03s
Average length
32s

Measured directly from 2 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.

Reaction mix

7 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤457.1%
👍342.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 5 of the 11 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 9 August 2026 to 10 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

10 Sept 2026, 11:06 UTC19 viewsread 10 September 2026
File

美团饿了么京东闪购一年所有订单 手慢无,价格小贵 当天回单 无遗漏 带订单编号 下单人手机号 收货人手机号 收货地址 商家名称 商家地址 商家id 商品详情 身份证 电话报单 好渠道不常有 需要的抓紧来

5 Sept 2026, 06:23 UTC117 views1 reactionsread 10 September 2026
Photo

长期稳定交付 老客户来都是直接下单的 各类项目 名下资产 各种反实名 资金流水动向 欢迎咨询 大家付款要小心谨慎多核对 以保证金等名义进行二次收费的都是骗子 大家注意 减少不必要损失 特此提醒! 客服: @tianwangcha_1 双向: @TWshegongkubot

👍1

1 Sept 2026, 05:49 UTC140 views2 reactionsread 10 September 2026
Video

开线开线 降价 降价 降价 天网最牛逼的业务来袭‼️‼️ 自家技术已攻克强登美团‼️‼️ 客户提供查询人美团手机号 上去就收费不听理由 录屏回地址加近一个月订单 当天必定回不定时秒 报单包出,不会那种傻逼测试业务 客服: @tianwangcha_1 双向: @TWshegongkubot

❤1👍1

26 Aug 2026, 17:34 UTC192 viewsread 10 September 2026
Photo

抖音收货地址 出最新一条 提供:姓名身份证(抖音号或者是抖音绑定的手机号) 支持 埋雷测试 拉担保全部支持 人在就秒 代理和渠道来拿优势

23 Aug 2026, 00:05 UTC226 viewsread 10 September 2026
Photo

开房记录性价比 华住会开同 最便宜高效 华住会开同 最便宜高效 华住会开同 最便宜高效 现在华住集团的高管权限只能看名下有华住会账号的人 部分OTA平台没有记录 例如 (携程,同程,去哪儿网等) 回单个人名下的华住会账号 和入住信息以及同住人信息 等账号相关信息 同行找我拿优势价格 三天内回单 支持埋雷 Excel表格回单 私我拿模板 敏感收费扣单 报单前请自查

20 Aug 2026, 11:37 UTC206 views2 reactionsread 10 September 2026
Photo

高德强登开 姓名身份证大头报单 强登录频所有打车导航记录 在线秒中 私信看板 不一定有打车

❤1👍1

15 Aug 2026, 14:07 UTC257 views1 reactionsread 10 September 2026
Video

哈啰所有出行记录 录屏注册至今所有出行记录 截屏注册至今所有常用地址 报单提供:个户+哈啰账号(手机号) (账号可以在哈啰app上找回密码查看) 客服: @tianwangcha_1 双向: @TWshegongkubot

❤1

15 Aug 2026, 11:39 UTCviews —

天网频道模板 pinned «每日最新稳定可交付业务及价格 每天都会更新 需要什么自主查看下单 尽量减少无效沟通 个人信息类目 小 关 联 个人户籍 全家户籍 婚姻记录 学籍学历 社保单位 社保记录 医疗记录 名下手机号 个人名下卡 个人名下房 房屋地址反查 手机短信记录 个人征信报告 法院诉讼+判决 人脸识别 名下护照+出入境 公司信息类目 公司法人股东 公司档案 …»

15 Aug 2026, 11:38 UTC220 viewsread 10 September 2026
Photo

源头业务收单 全国航班记录,只要买票,未起飞的也有 一年记录 极少遗漏 也可以加钱出同行人 文字回,工作日当天隔天回 客服: @tianwangcha_1 双向: @TWshegongkubot

9 Aug 2026, 14:26 UTC250 views1 reactionsread 10 September 2026
Photo

🐉🐉😀🐉🐉🐉🐉🐉 成交只是起点,服务没有终点,首次合作后,第二次秒付款,天网查档主打服务 感谢信任🙏 😀😀😀😀😀😀😀😀 唯一客服:@tianwangcha_1 限制传话筒:@TWshegongkubot 免费社工库:https://t.me/tianwangshegongku 项目模板:https://t.me/TWMB_1/125 #抓人 #找人 #开盒

❤1

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

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

“天网频道模板” (@TWMB_1), 1,621 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/TWMB_1.

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.