Telegram RegisterThe public register of Telegram
Telegram profile photo for huitudashifangpian

Channel

huitudashifangpian

@huitudashiFangpian

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

2subscribers

-83,000 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001669764438
TypeChannel
Username@huitudashiFangpian
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 October 2026
Measurements held28
Confirmed unchanged3 times, most recently 9 October 2026
On Telegramt.me/huitudashiFangpian

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 52% 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.

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 word for word 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@huituruanjian/630125 Mar 2026, 08:24 UTC@huitudashiFangpian/231 · this entry25 Mar 2026, 08:24 UTC1.00under a minute
@huituruanjian/630411 Apr 2026, 04:40 UTC@huitudashiFangpian/234 · this entry11 Apr 2026, 04:40 UTC1.00under a minute
@huituruanjian/630919 May 2026, 12:33 UTC@huitudashiFangpian/239 · this entry19 May 2026, 12:34 UTC1.00under a minute
@huituruanjian/631020 May 2026, 14:00 UTC@huitudashiFangpian/240 · this entry20 May 2026, 14:00 UTC1.00under a minute
@huituruanjian/631227 May 2026, 11:26 UTC@huitudashiFangpian/242 · this entry27 May 2026, 11:26 UTC1.00under a minute
@huituruanjian/63158 Jun 2026, 11:25 UTC@huitudashiFangpian/245 · this entry8 Jun 2026, 11:25 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@huituruanjian14 (8/8 hand-verifiable sample passed)1.00under a minuteeven

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. None of the 7 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 8 March 2026 to 4 August 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).

Across the whole group of 2, the earliest publisher we hold is @huituruanjian. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 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

283,00241,5027 August 2026 — 83,002 subscribers8 August 2026 — 82,947 subscribers9 August 2026 — 82,882 subscribers10 August 2026 — 82,805 subscribers11 August 2026 — 82,739 subscribers12 August 2026 — 82,681 subscribers13 August 2026 — 82,625 subscribers14 August 2026 — 82,584 subscribers16 August 2026 — 82,517 subscribers17 August 2026 — 82,454 subscribers18 August 2026 — 82,423 subscribers19 August 2026 — 82,403 subscribers20 August 2026 — 82,390 subscribers21 August 2026 — 82,363 subscribers23 August 2026 — 82,290 subscribers25 August 2026 — 82,256 subscribers25 August 2026 — 82,216 subscribers27 August 2026 — 82,185 subscribers29 August 2026 — 82,172 subscribers29 August 2026 — 82,154 subscribers30 August 2026 — 82,152 subscribers1 September 2026 — 82,120 subscribers2 September 2026 — 82,088 subscribers3 September 2026 — 82,040 subscribers4 September 2026 — 81,752 subscribers7 September 2026 — 81,042 subscribers10 September 2026 — 80,575 subscribers12 September 2026 — 2 subscribers7 August 202612 September 2026
28 measurements spanning 36 days, net -83,000. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
12 Sept 2026, 21:182-80,573
10 Sept 2026, 20:0080,575-467
7 Sept 2026, 18:3981,042-710
4 Sept 2026, 20:3681,752-288
3 Sept 2026, 04:1882,040-48
2 Sept 2026, 03:0482,088-32
1 Sept 2026, 00:0582,120-32
30 Aug 2026, 19:4782,152-2
29 Aug 2026, 23:1382,154-18
29 Aug 2026, 00:5782,172-13
27 Aug 2026, 01:2282,185-31
25 Aug 2026, 23:3382,216-40
25 Aug 2026, 00:1882,256-34
23 Aug 2026, 10:5682,290-73
21 Aug 2026, 21:0482,363-27
20 Aug 2026, 16:3682,390-13
19 Aug 2026, 17:5682,403-20
18 Aug 2026, 19:1482,423-31
17 Aug 2026, 17:5482,454-63
16 Aug 2026, 14:1482,517first reading

Engagement

23 posts held, back to 8 March 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 75 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 23 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
26m 22s
Average length
1m 53s

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

Recent posts

3 Sept 2026, 08:16 UTC751 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✨增加100+模板,并修复了已知Bug 👌支持网页版/桌面版! 👌支持手机/Mac/Win! 👌支持保存文本内容! 🆗支持一键收藏模版! 🆗支持一键搜索模版! 👌支持一键对比原图! 👌支持放大缩小图像! 🆗支持图像模版多开! 👌状态栏一比一复刻! 👌支持素材库任选素材! 👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗

29 Aug 2026, 07:36 UTC887 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✨增加130+模板,增加多个节点提升响应速度,并修复了已知Bug 👌支持网页版/桌面版! 👌支持手机/Mac/Win! 👌支持保存文本内容! 🆗支持一键收藏模版! 🆗支持一键搜索模版! 👌支持一键对比原图! 👌支持放大缩小图像! 🆗支持图像模版多开! 👌状态栏一比一复刻! 👌支持素材库任选素材! 👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗

4 Aug 2026, 05:10 UTC≈2,290 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✨增加320+模板,并修复了已知Bug 👌支持网页版/桌面版! 👌支持手机/Mac/Win! 👌支持保存文本内容! 🆗支持一键收藏模版! 🆗支持一键搜索模版! 👌支持一键对比原图! 👌支持放大缩小图像! 🆗支持图像模版多开! 👌状态栏一比一复刻! 👌支持素材库任选素材! 👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗

21 Jul 2026, 03:15 UTC≈2,270 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✨已更新50+模板,并修复多个Bug 👌支持网页版/桌面版! 👌支持手机/Mac/Win! 👌支持保存文本内容! 🆗支持一键收藏模版! 🆗支持一键搜索模版! 👌支持一键对比原图! 👌支持放大缩小图像! 🆗支持图像模版多开! 👌状态栏一比一复刻! 👌支持素材库任选素材! 👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗

16 Jul 2026, 13:51 UTC≈1,830 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✨已更新200+模板,并新增多个网络节点优化了连接速度 👌支持网页版/桌面版! 👌支持手机/Mac/Win! 👌支持保存文本内容! 🆗支持一键收藏模版! 🆗支持一键搜索模版! 👌支持一键对比原图! 👌支持放大缩小图像! 🆗支持图像模版多开! 👌状态栏一比一复刻! 👌支持素材库任选素材! 👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗

3 Jul 2026, 02:22 UTC≈2,430 viewsread 11 September 2026

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! 👌【近期客户反馈有人员诽谤绘图大师,绘图大师团队在此申明:绘图大师不存在任何后门或病毒,请确保您是在 @pitu 频道中下载的正版软件,同时请各用户定期多次电脑杀毒,避免因下载其他不良软件而导致中毒】 ps:在tg中冒充者很多,请一定认准 @pitu @htds @huitu

8 Jun 2026, 11:25 UTC≈3,210 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✦本次更新素材库功能已完善并全面上线,优化了下载速度,修复已知Bug 👌【近期多人反馈被冒充者欺骗,请大家在转账前点击官网的联系客服按钮确认,避免被骗】 💎支持102个交易所:CashappㆍCoinbaseㆍCoinbasewalletㆍCrypto.comㆍCrypto钱包ㆍBinanceㆍBitgetㆍBitget钱包ㆍBybitㆍBybit钱包ㆍImtokenㆍKrakenㆍKucoinㆍLbankㆍNDAXㆍNewtonㆍOkxㆍMetaMaskㆍMEXCㆍStrike钱包ㆍTrustㆍBingxㆍBitflyerㆍBithumbㆍBitkeepㆍBitMartㆍBitoproㆍBitpieㆍBit…

30 May 2026, 10:46 UTC≈2,980 viewsread 11 September 2026

👌Telegram隐藏了中文语言选项,需要通过特定的链接或特定行为触发来激活。为避免您下载到第三方恶意语言包,以下是官方提供的最新中文语言包链接: 简体中文: https://t.me/setlanguage/zh-hans-raw 繁体中文: https://t.me/setlanguage/zh-hant-raw 使用方法: 在已登录 Telegram的设备上 ,直接点击上面的链接,Telegram 会弹出提示,询问是否切换语言,点击确认即可切换为中文界面。

28 May 2026, 08:50 UTC≈2,310 viewsread 11 September 2026
Video

👍🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗🆗 【绘图大师】是一款支持网页版、桌面版的炫富恶搞神器,支持上万模版图片真实度达到1:1,绘图是全网唯一无毒绿色商家! 【请您加入绘图4字频道 @Pitu 人工客服7*24小时在线为您服务! ✦绘图大师重磅推出素材库功能!该功能已上线并稳定使用! 👌【近期多人反馈被冒充者欺骗,请大家在转账前点击官网的联系客服按钮确认,避免被骗】 💎支持102个交易所:CashappㆍCoinbaseㆍCoinbasewalletㆍCrypto.comㆍCrypto钱包ㆍBinanceㆍBitgetㆍBitget钱包ㆍBybitㆍBybit钱包ㆍImtokenㆍKrakenㆍKucoinㆍLbankㆍNDAXㆍNewtonㆍOkxㆍMetaMaskㆍMEXCㆍStrike钱包ㆍTrustㆍBingxㆍBitflyerㆍBithumbㆍBitkeepㆍBitMartㆍBitoproㆍBitpieㆍBitsoㆍBits…

27 May 2026, 11:26 UTC≈1,960 viewsread 11 September 2026
Photo

⚠️原机器人被封禁,原有数据已转至新机器人! @duihuandashi_bot Telegram会员开通、TRX兑换、Stars星星购买、链上地址监控(自动黑U检测)一体化智能服务机器人。 🆗「TRX兑换」汇率实时 · 极速到账 🆗「TG会员」一键开通 · 批量开通 🆗「星星购买」低价秒充 · 量大优惠 🆗「地址监控」链上异动 · 即时推送

23 May 2026, 06:41 UTC≈2,180 viewsread 11 September 2026
Photo

活动仅剩7天! 👌活动截止:2026年6月1日23:59

Showing the 12 most recent of 23 posts we hold for @huitudashiFangpian. 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.

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.

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

“huitudashifangpian” (@huitudashiFangpian), 2 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/huitudashiFangpian.

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.