Telegram RegisterThe public register of Telegram
Telegram profile photo for fugui156

Channel

fugui156

@fugui156

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

8,464subscribers

+7,925 since we began measuring on 16 September 2026

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

Register entry

Telegram ID-1003518616740
TypeChannel
Username@fugui156
Description№ 8099678915
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 September 2026
Last confirmed live13 November 2026
Measurements held30
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/fugui156

Topic

Other / unclassifiable — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 70% 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. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@quanyi/49710 Sept 2026, 01:36 UTC@fugui156/170 · this entry10 Sept 2026, 01:37 UTC1.002 minutes
@fugui156/196 · this entry30 Oct 2026, 15:50 UTC@quanyi/51630 Oct 2026, 15:50 UTC1.00under a minute
@fugui156/198 · this entry31 Oct 2026, 05:31 UTC@quanyi/51731 Oct 2026, 05:31 UTC1.00under a minute
@fugui156/202 · this entry2 Nov 2026, 08:43 UTC@quanyi/5212 Nov 2026, 08:43 UTC1.00under a minute
@fugui156/207 · this entry8 Nov 2026, 10:06 UTC@quanyi/5268 Nov 2026, 10:06 UTC1.00under a minute
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
@quanyi15 (7/8 hand-verifiable sample passed)1.00under a minutethis entry (10–5)

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. 5 of the 5 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 22 comparable posts for this entry, running 10 September 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @quanyi. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 18 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

53911,7376,13816 September 2026 — 539 subscribers16 September 2026 — 539 subscribers18 September 2026 — 540 subscribers3 October 2026 — 11,732 subscribers7 October 2026 — 11,736 subscribers12 October 2026 — 11,737 subscribers14 October 2026 — 11,736 subscribers16 October 2026 — 11,735 subscribers17 October 2026 — 11,732 subscribers18 October 2026 — 11,731 subscribers20 October 2026 — 11,717 subscribers21 October 2026 — 11,680 subscribers22 October 2026 — 11,584 subscribers23 October 2026 — 11,532 subscribers24 October 2026 — 11,400 subscribers25 October 2026 — 11,335 subscribers26 October 2026 — 11,238 subscribers27 October 2026 — 11,160 subscribers28 October 2026 — 11,104 subscribers29 October 2026 — 10,981 subscribers30 October 2026 — 10,875 subscribers31 October 2026 — 10,806 subscribers1 November 2026 — 10,755 subscribers2 November 2026 — 10,697 subscribers3 November 2026 — 10,684 subscribers4 November 2026 — 10,469 subscribers5 November 2026 — 10,229 subscribers6 November 2026 — 9,326 subscribers9 November 2026 — 8,882 subscribers13 November 2026 — 8,464 subscribers8,46416 September 202613 November 2026
30 measurements spanning 59 days, net +7,925. 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 30
Measured (UTC)SubscribersChange
13 Nov 2026, 21:198,464-418
9 Nov 2026, 07:498,882-444
6 Nov 2026, 08:269,326-903
5 Nov 2026, 09:4510,229-240
4 Nov 2026, 09:0610,469-215
3 Nov 2026, 06:3610,684-13
2 Nov 2026, 07:1110,697-58
1 Nov 2026, 08:4810,755-51
31 Oct 2026, 11:4910,806-69
30 Oct 2026, 11:5610,875-106
29 Oct 2026, 10:4910,981-123
28 Oct 2026, 09:1611,104-56
27 Oct 2026, 08:4811,160-78
26 Oct 2026, 07:4111,238-97
25 Oct 2026, 09:0211,335-65
24 Oct 2026, 11:0911,400-132
23 Oct 2026, 08:5711,532-52
22 Oct 2026, 11:3511,584-96
21 Oct 2026, 06:1011,680-37
20 Oct 2026, 06:0611,717first reading

Engagement

51 posts held, back to 24 July 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 32 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.43%
avg views ÷ 8,464 subscribers
Avg views / post
206
30 posts measured
Reaction rate
0.37%
reactions ÷ views · ER floor
Posts in window
30
of 51 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 2 of 30 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 18 November 2026
Posts held51 (24 July 2026 – 18 November 2026)
Views total6,165
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 14:53 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
74
Videos
3
Links
4

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 22s
Average length
41s

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

12 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 91.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1191.7%
👍18.33%

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

Measured over the 51 most recent posts we hold, published 24 July 2026 to 18 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: 2 of 30 posts held from the last 30 days (6.67%) 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).

18 Nov 2026, 08:51 UTC78 viewsread 18 November 2026

新加坡重拳打击电诈!诈骗犯最高可被鞭刑 24下 新加坡警方明确警告,即使没有亲自参与诈骗,只要向诈骗团伙提供银行卡、SIM卡或协助转移赃款,也可能被追究刑事责任。根据相关法律,符合条件的诈骗犯罪人员最高面临24下鞭刑,协助转移资金者也可能被判监禁及鞭刑。 此外,新加坡还将限制涉诈人员使用ATM、网上银行、银行卡及手机号码等服务,违规者可能面临最长三年的限制。警方提醒,出租银行卡、代收款、帮忙转账都可能成为犯罪行为,切勿为了赚取手续费惹上牢狱之灾。

18 Nov 2026, 08:51 UTC75 viewsread 18 November 2026

研究发现中国电信光猫预装插件可窃取用户隐私与执行远程指令 V2EX论坛有开发者通过分析中国电信光猫中名为“m01-b01-inner”的预装插件,证实其具备提取手机号、IMEI、MAC地址及设备访问记录的能力,并支持远程命令执行及内网扫描。该插件运行在基于OpenWrt的LXC容器内,且因业务逻辑代码加密且不落盘,难以被用户察觉。 开发者研究发现,该插件能探测用户内网设备详情,甚至通过服务器下发指令进行URL重定向或抓取。该机制在用户不知情下自动运行,且上传数据与实名宽带账号绑定,引发隐私泄露担忧。 皮娅妹解读一下:就是国内现在光猫能精确到你家哪台设备,甚至对应到某个手机号或 IMEI在翻墙使用tg看片。原来最多知道这户人家在翻墙,现在能知道是哪个人在翻墙。

17 Nov 2026, 09:29 UTC101 viewsread 18 November 2026
Photo

FBI派专案组赴斯里兰卡!联合当地警方调查跨国电信诈骗网络 据斯里兰卡媒体《Daily Mirror》及新加坡亚洲新闻台(CNA)等媒体报道,11月16日,美国联邦调查局(FBI)应斯里兰卡政府请求,派遣专门调查团队前往斯里兰卡首都科伦坡,与当地警方联合调查跨国电信网络诈骗案件。 此次行动由FBI夏洛特外勤办公室派员参与,预计持续至11月22日,重点针对当地涉嫌从事网络诈骗活动的犯罪团伙展开调查,同时协助识别受害者、追查诈骗资金流向,并调查幕后组织者及相关犯罪网络。 据报道,此次合作将重点运用数字取证、电子证据分析及网络犯罪调查技术,为斯里兰卡警方提供专业支持,协助当地执法部门掌握诈骗团伙的运作方式及跨境资金转移情况。 美国方面指出,跨国网络诈骗团伙正在利用不同国家和地区作为犯罪据点,通过跨境渠道转移非法所得,给国际执法工作带来挑战。 此次FBI派员赴斯里兰卡,标志着美斯双方进一步加强跨国网络犯罪调查合作,也反映出国际…

17 Nov 2026, 09:29 UTC88 viewsread 18 November 2026
Photo

兄弟们,发财的机会来了 美国政府开价1000万美元,买一个缅甸电诈园区的内部消息。 今天,美国驻缅甸大使馆转发了一张悬赏海报:妙瓦底附近的泰昌电诈园区,还有它背后的洗钱网络,谁提供的线索能帮美国查扣、追回赃款,最高奖1000万美元。 泰昌不是一个园区,是一串。1.0、2.0、3.0,别名还有Ko Soi赌场、Kyauk Khat赌场、青松。地盘是缅甸克伦邦的武装组织DKBA的,园区是2020年DKBA将领赛觉拉和中国投资者合伙建起来的,专骗美国人,也关着被贩运进去强迫干活的人。 美国其实去年就动手了。2025年11月,财政部制裁了整个DKBA和赛觉拉本人,司法部和FBI还专门成立了“电诈中心打击部队”。泰昌用来行骗的网站被FBI查封过一批,还有约3000万美元加密货币被申请扣押。 制裁了一年,园区还开着。所以这次换打法了:悬赏要的不是人头,是钱的下落——谁在管账,钱从哪走,钱包在哪。 举报方式海报上有

16 Nov 2026, 04:24 UTC129 viewsread 18 November 2026

推出加密货币支付试点!外国游客可用USDT、USDC扫码消费 11月13日,据彭博社报道,泰国正式面向外国游客推出加密货币支付应用WORPT,游客无需开设泰国银行账户,就能将加密货币兑换成泰铢,在当地商店、餐厅扫码消费。 目前,该应用支持USDT、USDC兑换泰铢,并通过泰国常用的PromptPay二维码完成支付。需要注意的是,商家实际收到的仍然是泰铢,并非加密货币。 据了解,WORPT由Wipay与Waan Exchange联合开发,创始人包括泰国正大集团谢国民家族成员Chaval Jiaravanon,目前在泰国证监会TouristDigiPay监管沙盒框架下试运行。

14 Nov 2026, 10:30 UTC166 viewsread 18 November 2026

Bitrace 分析师称新币担保创始人重返担保市场,汇旺支付团队另建平台 据 Bitrace 情报分析师 Yuri在 X 披露,新币担保创始人已重新开展加密货币交易担保业务,并再次在这一非法市场占据主导地位。 汇旺支付运营团队在出售其 Telegram 网赌门户后,随即建立了一个仅面向网赌业务的新担保平台。Yuri 还称,金贝集团旗下的担保平台、支付工具及线下赌场仍在运营,多个与汇旺担保关系密切的网赌运营方接手了大量 Telegram 公开群组,并独立运营或与第三方担保平台合作。Yuri 认为,联合执法打击了原有担保和支付平台,但只要网赌、欺诈和盗窃等上游犯罪仍在持续,就可能出现新的担保平台和非法支付工具

12 Nov 2026, 07:47 UTC211 viewsread 18 November 2026
Photo

这是一段 TG desktop 的攻击Demo展示,利用了一个TG 0DAY漏洞。 通过这个漏洞,你只需要点击攻击者的机器人 /start,无需任何交互,无需任何点击,看到消息的一瞬间即可RCE。 我问了ai,ai建议不要随便乱点机器人了。特别是群发让你点机器人。

11 Nov 2026, 05:17 UTC196 viewsread 18 November 2026

与特定加密货币平台进行交易的相关事项 这是一般性公告,此处提及的产品和服务可能不适用于您所在的地区。 鉴于美国金融犯罪执法局(FinCEN)近期将MEXC列为“重大洗钱关注对象”(Primary Money Laundering Concern),币安将无法继续处理涉及上述认定所涵盖的加密资产服务提供商及平台的交易,具体包括以下实体: MEXC Global Limited MEXC Estonia OÜ GIDA Technology AG MXC Global Ltd MEXC Global Foundation Ltd MEXC Singapore Pte Ltd MEXC (Comoros) Ltd MEXC MEXC Global MEX Global Ltd MX Global LTD MEX Exchange(曾用名) MEXC 其他关联方或关联实体 因此,请勿通过币安直接或间接向上述实体转账、接收来自上述实…

10 Nov 2026, 16:10 UTC183 views0 reactionsread 18 November 2026
Photo

📱苹果用户一定注意! 苹果手机又出漏洞了,装错一个App,钱包里的U可能被无感偷走 11月8日,有个开发者在 GitHub 上公开了一个苹果漏洞,名字叫 worse_query。 用大白话说:苹果本来给每个 App(沙盒)都关在自己的小房间里,互相看不到。这个漏洞能让一个 App 从小房间里溜出来,去翻别的 App 的东西,还能改。 那问题就大了。你手机里要是装了个带毒的 App,它就能借这个漏洞去翻你钱包 App 里的数据,你这边一点感觉都没有,U 可能就没了。 受影响的版本很多,iOS 26.0 到 26.7.2,还有 27.2,连 27.3 测试版都有。作者说已经报给苹果了,但到现在还没修好,代码却已经公开,网上已经有人拿它做成工具了。 用苹果的兄弟,这段时间注意: ㅤㅤㅤㅤㅤㅤㅤ

9 Nov 2026, 16:14 UTC202 viewsread 18 November 2026
Photo

一个更大的瓜: 黄乐老公是幕后老板 他把自己老婆献给黄仁勋,换取Nvidia对“新加坡洗澡卡”睁只眼闭只眼 进中国的B300的1/3,H200的1/5是夫妻俩倒腾的 这位绿帽老公,是互联网游戏圈的同行! 真TM丢人啊!

9 Nov 2026, 04:29 UTC195 viewsread 18 November 2026
Photo

塌房!英伟达CEO黄仁勋承认婚外情 董事会启动独立调查 英伟达CEO黄仁勋周日向员工发信,承认曾有婚外情并深表歉意。此前有报道称,与其保持关系的女子涉嫌为中国政府搜集情报。 英伟达董事会已成立独立委员会展开调查,以厘清国家安全及公司机密是否受影响。华尔街分析师指出,此事件对黄仁勋个人声誉造成打击,并可能引发美国国会调查及对其是否留任的审视。不过,短期内黄仁勋预计将继续留任。

8 Nov 2026, 16:10 UTC196 viewsread 18 November 2026
Photo

网友投稿:柬埔寨警方已和中国公安实现数据共享,范围涵盖柬埔寨出入境记录、在柬中国人居住登记、各类实名登记信息等。 请在柬同胞们遵守当地法律法规,请勿从事任何违法犯罪活动

Showing the 12 most recent of 51 posts we hold for @fugui156. 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“fugui156” (@fugui156), 8,464 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/fugui156.

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.