Telegram RegisterThe public register of Telegram
Telegram profile photo for MSDS gongying

Channel

MSDS gongying

@benchi005

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

55,785subscribers

+5,729 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-1002001617282
TypeChannel
Username@benchi005
Description№ 8112147302
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/benchi005

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

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@benchi005/7847 · this entry6 Aug 2026, 11:01 UTC@tongxin567888/320207 Aug 2026, 07:00 UTC1.0020 hours
@benchi005/8174 · this entry4 Sept 2026, 13:41 UTC@tongxin567888/3285815 Sept 2026, 02:06 UTC1.0011 days
@benchi005/8199 · this entry7 Sept 2026, 11:15 UTC@tongxin567888/327208 Sept 2026, 09:16 UTC0.9622 hours
@benchi005/8179 · this entry5 Sept 2026, 08:01 UTC@tongxin567888/326796 Sept 2026, 07:25 UTC0.9523 hours
@tongxin567888/326796 Sept 2026, 07:25 UTC@benchi005/8234 · this entry10 Sept 2026, 14:43 UTC0.954 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@tongxin5678885 (5/5 hand-verifiable sample passed)0.9723 hoursthis entry (4–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 604 comparable posts for this entry, running 6 August 2026 to 17 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

41,21057,22149,215.555,7857 August 202614 November 2026
66 measurements spanning 99 days, net +5,729. 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 38,808–59,623 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
14 Nov 2026, 23:5555,785-106
11 Nov 2026, 21:4855,891+31
10 Nov 2026, 02:0955,860-191
8 Nov 2026, 16:4656,051-124
7 Nov 2026, 07:0956,175-133
6 Nov 2026, 07:5756,308-28
5 Nov 2026, 08:4956,336-11
4 Nov 2026, 07:1056,347-103
3 Nov 2026, 09:0256,450-22
2 Nov 2026, 08:5856,472-82
1 Nov 2026, 09:3656,554-91
31 Oct 2026, 12:5456,645-36
30 Oct 2026, 14:0656,681-113
29 Oct 2026, 13:0756,794-24
28 Oct 2026, 14:2656,818+1
27 Oct 2026, 17:2156,817+11
26 Oct 2026, 15:1756,806-41
25 Oct 2026, 11:5156,847-29
24 Oct 2026, 11:0656,876-28
23 Oct 2026, 08:0556,904first reading

Engagement

1,028 posts held, back to 6 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 209 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.03%
avg views ÷ 55,785 subscribers
Avg views / post
2,250
276 posts measured
Reaction rate
0.182%
reactions ÷ views · ER floor
Posts in window
277
of 1,028 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 17 November 2026
Posts held1,028 (6 August 2026 – 17 November 2026)
Views total620,799
Reactions total1,128
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 02:06 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

Photos
≈6,100
Videos
≈786
Links
≈3,190

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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 14m
Average length
18s

Measured directly from 251 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

4,060 reactions across 883 posts, in 15 distinct kinds. The most used accounts for 87.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3,54287.2%
❤‍🔥872.14%
👍751.85%
👏651.60%
💔621.53%
🔥601.48%
🍌501.23%
👎501.23%
👌491.21%
🎉60.148%
👀60.148%
💯50.123%
😁10.025%
🙏10.025%
🤩10.025%

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 883 of the 1,000 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 4,060 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 August 2026 to 17 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.

Recent posts

Telegram’s own ‘edited’ marker: 9 of 277 posts held from the last 30 days (3.25%) 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).

17 Nov 2026, 01:33 UTC≈2,140 views1 reactionsread 17 November 2026
Photo

😄⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️😄 需求商品:douyin老号 商品介绍:douyinOP数据2-9年老号,做过项目的不要,违规的不要 价格: 私 联系人: @tutu77889990 交易方式:必须支持担保交易 交易身份:必须梅赛德斯会员

❤1

16 Nov 2026, 15:08 UTC≈2,320 views3 reactionsread 17 November 2026
Photo

🤓🤓🤓🤓🤓 ⚡️⚡️ 😘 一站式综合娱乐平台 😘 视讯 · 电子 · 棋牌 · 捕鱼 · 体育 ✈️TG一键登入: @jlyl 🤓 一键注册登录 · 无需下载 🤓 用户真实验证 · 长期口碑 🤓 充值提現高效 · 资金安全 ⚡️ 官方直营 · 信誉保证 ⚡️ 稳定运营 · 实力平台 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎁【 三重首存好礼】VIP专属首存大礼包,最高赠送⚡️⚡️⚡️⚡️⚡️ 🎁【每周VIP周奖励】每周达到VIP流水要求,最高领取⚡️⚡️⚡️⚡️⚡️⚡️ 🎁【亏损救援转运】当日电子捕鱼棋牌亏损救援金,最高赠送⚡️⚡️⚡️⚡️⚡️ 🎁【每日红包不断】每日三波幸运红包雨助力转运🧧🧧🧧🧧 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 👍金乐官频: @jinle 👍金乐娱乐: @jlyl (认准四字id) 👍官方招商: @blkf (认准四字id) 👍VIP 客服 : @hhkf (认准四字id) 👍官…

❤3

16 Nov 2026, 14:12 UTC≈2,330 views5 reactionsread 17 November 2026
Photo

有没有搞孟加拉或者菲律宾盗刷的 需要粉 远控 新工作室 懂的来对接一下

❤5

16 Nov 2026, 12:15 UTC≈2,390 views4 reactionsread 17 November 2026
Photo

需求商品:盘囗直收全球色粉/排除大陆 商品要求:✅(大量收)APP,好投放的来 ✅(大量收)所有国家FB代投 ✅(大量收)所有国家kwai代投 ✅(大量收)所有国家TT代投 ✅(大量收)所有国家谷歌代投 ✅(大量收)所有国家KOL网红资源 ✅FB TT GG kwai 一级代理商 ✅收一切华侨男数据,短信通道,保效果来 ✅TK INS 谷歌 等各种软件采集群发 ✅微信工作室站街 大量收代理✅ 💥介绍海外流量,成功对接查888u-55000u介绍费💥 联系方式:@LXIN1288 联系方式:@bx00179 交易方式:支持担保交易

❤4

16 Nov 2026, 10:18 UTC≈2,370 views4 reactionsread 17 November 2026
Photo

😀通道一览 —— ⭐️一类线上—— 亚洲区域 🧩 印度 🧩 印尼 🧩 缅甸 🧩菲律宾 🧩孟加拉 🧩马来西亚 🧩巴基斯坦 🧩泰国 美洲区域 🧩墨西哥 🧩巴西 🧩哥伦比亚 🧩 美国 🧩秘鲁 🧩阿根廷 🧩智利 🧩厄瓜多尔 🧩玻利维亚 非洲区域 (部分国家需持牌) 🧩尼日利亚 🧩肯尼亚 🧩乌干达 🧩坦桑尼亚 🧩喀麦隆 🧩科特迪瓦 🧩贝宁 🧩南非 🧩塞内加尔 🧩赞比亚 🧩卢旺达 🧩加纳 🧩埃及 全球综合信用卡 (支持全球50+国家) 🧩VISA/MASTER 交易所信用卡 🧩美国本地 🧩欧洲本地 🧩香港本地 🧩英国本地 ❗️(本地渠道需求海外主体) —— ⭐️二类线上—— 亚洲区域 🧩 印度 🧩 印尼 🧩 缅甸 🧩菲律宾 🧩孟加拉 🧩马来西亚 美洲区域 🧩墨西哥 🧩巴西 🧩哥伦比亚 🧩秘鲁 🧩阿根廷 非洲区域 🧩尼日利亚 🧩肯尼亚 🧩乌干达 🧩坦桑尼亚 🧩喀麦隆 🧩科特迪瓦 🧩贝宁 🧩南非 🧩塞内加尔 🧩赞比亚 🧩卢旺达 🧩…

❤4

16 Nov 2026, 08:47 UTC≈2,380 views4 reactionsread 17 November 2026
Photo

需要印度银行 有imps吗 渗透料 有200亿 有卡的联系我

❤4

16 Nov 2026, 07:12 UTC≈2,420 views4 reactionsread 17 November 2026
Video

😀😀😀😀😀😀 😀😀😀😀😀😀😀😀😀😀 😀 【行情一变,才知道谁有底子】 😀 平台很多,口号更多。顺风时谁都敢谈实力,真正拉开差距的,是市场波动时还能不能正常结算、照常出款。 😀 U8资金储备充足,各项业务与出款通道正常运行。 😀 正常投注,正常盈利 😀 一分不少,照常兑付 😀 不拿行情当借口 😀 大额出款,按规则执行 😅 真正的实力,不是说得多响,而是关键时候付得起、出得快。 🙂 市场有波动,U8兑付不打折。 😀 选择U8,把输赢交给游戏,把出款交给实力ht 😀 官方信息入口: 😀😀😀😀😀: u8bug.com 😀😀😀😀😀: @U8dafa8 😀U8官方客服:@U8dafa0 😀如出现网址打不开的情况,联系 @ 获取备用网址 😀😀😀😀😀😀😀😀😀

❤4

16 Nov 2026, 04:22 UTC≈2,380 views1 reactionsread 17 November 2026
Photo

😄⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️😄 需求商品:孟加拉远控粉 商品介绍:一手价格 价格:谈 联系人: @hengchengjitun 交易方式:必须支持担保交易 交易身份:必须梅赛德斯会员

❤1

16 Nov 2026, 01:27 UTC≈2,410 views2 reactionsread 17 November 2026
Photo

😄梅赛德斯官方发布😄 出售三年搜索大群和搜索会员群 联系人: @hengchengjitun 交易方式:必须支持担保交易 交易身份:必须梅赛德斯会员

❤2

15 Nov 2026, 15:02 UTC≈2,460 views5 reactionsread 17 November 2026
Photo

🤓🤓🤓🤓🤓 ⚡️⚡️ 😘 一站式综合娱乐平台 😘 视讯 · 电子 · 棋牌 · 捕鱼 · 体育 ✈️TG一键登入: @jlyl 🤓 一键注册登录 · 无需下载 🤓 用户真实验证 · 长期口碑 🤓 充值提現高效 · 资金安全 ⚡️ 官方直营 · 信誉保证 ⚡️ 稳定运营 · 实力平台 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎁【 三重首存好礼】VIP专属首存大礼包,最高赠送⚡️⚡️⚡️⚡️⚡️ 🎁【每周VIP周奖励】每周达到VIP流水要求,最高领取⚡️⚡️⚡️⚡️⚡️⚡️ 🎁【亏损救援转运】当日电子捕鱼棋牌亏损救援金,最高赠送⚡️⚡️⚡️⚡️⚡️ 🎁【每日红包不断】每日三波幸运红包雨助力转运🧧🧧🧧🧧 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 👍金乐官频: @jinle 👍金乐娱乐: @jlyl (认准四字id) 👍官方招商: @blkf (认准四字id) 👍VIP 客服 : @hhkf (认准四字id) 👍官…

❤5

15 Nov 2026, 12:59 UTC≈2,410 views5 reactionsread 17 November 2026
Photo

😄梅赛德斯官方发布😄 供应商品:全球cvv数据料 商品介绍:一手 价格: 谈 联系人: @nxkos1 交易方式:必须支持担保交易 交易身份:必须梅赛德斯会员

❤5

15 Nov 2026, 10:12 UTC≈2,390 views4 reactionsread 17 November 2026
Photo

😀通道一览 —— ⭐️一类线上—— 亚洲区域 🧩 印度 🧩 印尼 🧩 缅甸 🧩菲律宾 🧩孟加拉 🧩马来西亚 🧩巴基斯坦 🧩泰国 美洲区域 🧩墨西哥 🧩巴西 🧩哥伦比亚 🧩 美国 🧩秘鲁 🧩阿根廷 🧩智利 🧩厄瓜多尔 🧩玻利维亚 非洲区域 (部分国家需持牌) 🧩尼日利亚 🧩肯尼亚 🧩乌干达 🧩坦桑尼亚 🧩喀麦隆 🧩科特迪瓦 🧩贝宁 🧩南非 🧩塞内加尔 🧩赞比亚 🧩卢旺达 🧩加纳 🧩埃及 全球综合信用卡 (支持全球50+国家) 🧩VISA/MASTER 交易所信用卡 🧩美国本地 🧩欧洲本地 🧩香港本地 🧩英国本地 ❗️(本地渠道需求海外主体) —— ⭐️二类线上—— 亚洲区域 🧩 印度 🧩 印尼 🧩 缅甸 🧩菲律宾 🧩孟加拉 🧩马来西亚 美洲区域 🧩墨西哥 🧩巴西 🧩哥伦比亚 🧩秘鲁 🧩阿根廷 非洲区域 🧩尼日利亚 🧩肯尼亚 🧩乌干达 🧩坦桑尼亚 🧩喀麦隆 🧩科特迪瓦 🧩贝宁 🧩南非 🧩塞内加尔 🧩赞比亚 🧩卢旺达 🧩…

❤4

Showing the 12 most recent of 1,028 posts we hold for @benchi005. 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

@benchi005 edited 6 posts 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
10 September 2026
Most recent edit
1 November 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @benchi005 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
26 August 2026
Most recent seen missing
7 November 2026
Median time before seen missing
17 hours
Seen missing in the last 30 days
2

Mentions

Named by 2 registered channels — 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“MSDS gongying” (@benchi005), 55,785 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/benchi005.

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.