就在今天 新加坡警方抓了 太子集团 账房主管 陈秀玲(Karen Chen Xiuling,又名Karen Chen),她涉嫌与太子集团创始人陈志有关联的多家公司进行欺诈。陈秀玲是多家新加坡公司的董事, 与此同时,金贝集团(原太子集团旗下)的 Telegram 在线钱包 X Wallet 也进行了紧急维护,并更换了所有用户的充值地址。
Signed 皮娅妹

Channel
@fuporiji
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
20,665subscribers
-16,765 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001877308372 |
|---|---|
| Type | Channel |
| Username | @fuporiji |
| Description | 关注富婆日记 飞机跑的最快的女记者 投稿皮娅妹 @piyameibot 免费NFT担保 皮娅 @piya |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 92 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/fuporiji |
Crypto & trading — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
@fuporiji was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 04:06 | 20,665 | -240 |
| 5 Nov 2026, 05:36 | 20,905 | -6 |
| 4 Nov 2026, 08:17 | 20,911 | -183 |
| 3 Nov 2026, 07:37 | 21,094 | +134 |
| 2 Nov 2026, 07:35 | 20,960 | -332 |
| 1 Nov 2026, 05:20 | 21,292 | -163 |
| 31 Oct 2026, 06:36 | 21,455 | +533 |
| 30 Oct 2026, 09:28 | 20,922 | +795 |
| 29 Oct 2026, 10:51 | 20,127 | -499 |
| 28 Oct 2026, 07:20 | 20,626 | -353 |
| 27 Oct 2026, 03:50 | 20,979 | -344 |
| 26 Oct 2026, 02:49 | 21,323 | -359 |
| 24 Oct 2026, 23:37 | 21,682 | -404 |
| 24 Oct 2026, 00:20 | 22,086 | -408 |
| 22 Oct 2026, 22:45 | 22,494 | -400 |
| 21 Oct 2026, 23:46 | 22,894 | -649 |
| 20 Oct 2026, 17:06 | 23,543 | -699 |
| 19 Oct 2026, 17:04 | 24,242 | -232 |
| 18 Oct 2026, 18:07 | 24,474 | -451 |
| 17 Oct 2026, 20:50 | 24,925 | first reading |
157 posts held, back to 29 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 130 pages of Telegram’s post history, 20 posts per page.
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 13 of 51 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 157 (29 July 2026 – 6 November 2026) |
| Views total | 126,680 |
| Reactions total | 106 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 03:04 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.
Lifetime counters from Telegram’s own channel header, read 7 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.
Measured directly from 11 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.
197 reactions across 38 posts, in 4 distinct kinds. The most used accounts for 48.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6228546656237787272 | 95 | 48.2% | |
| custom 6201935653052092324 | 50 | 25.4% | |
| custom 6228893354587856148 | 39 | 19.8% | |
| custom 6059992687635864246 | 13 | 6.60% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 50 of the 157 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 197 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 157 most recent posts we hold, published 29 July 2026 to 6 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @fuporiji. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 157 most recent posts we hold for this entry, published 29 July 2026 to 6 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 18 of 51 posts held from the last 30 days (35.3%) 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).
就在今天 新加坡警方抓了 太子集团 账房主管 陈秀玲(Karen Chen Xiuling,又名Karen Chen),她涉嫌与太子集团创始人陈志有关联的多家公司进行欺诈。陈秀玲是多家新加坡公司的董事, 与此同时,金贝集团(原太子集团旗下)的 Telegram 在线钱包 X Wallet 也进行了紧急维护,并更换了所有用户的充值地址。
Signed 皮娅妹
😂昨晚这笔交易挺有意思! 958,888U 的 NFT 交易,买方把全款打给了皮娅然后就打电子消失了2个小时,卖方也直接把 NFT 转到了皮娅指定地址。 相当于买卖双方把钱和货都交给了皮娅,双边资产同时托管! 958,888U 的交易款,加上对应的 NFT 货物,皮娅两边一起接相当于200万U! 有皮娅在,2000000usdt交易也不用慌,安全交付才是最重要的!👑 @fupo @piya
Signed 皮娅妹
完成交易 958888u!
Signed 皮娅妹
另外一位粉丝投稿 使用苹果小火箭用机场上tg也被逮着了 地区福建 中国移动 ,手机被断网了,现在要恢复网络需要工作证明和营业执照 公司门牌和工作照!
Signed 皮娅妹
🚨 翻墙也被后台标记了? 今天有粉丝反馈,去派出所办事时,被民警告知自己经常翻墙,使用的是中国移动流量,用的是福利来代理。 同时今天X(推特)上也有人称,去移动营业厅办理业务时,被工作人员提醒自己经常翻墙,后台甚至被标记为黄色。 ⚠️ 富婆日记提醒: 翻墙上网请遵守法律法规,不要从事违法活动。 有跨境上网需求的朋友,可以考虑国际漫游 eSIM 或香港卡,减少对传统 VPN、代理的依赖。 但要注意:eSIM 不等于匿名,也不代表无法追踪。
Signed 皮娅妹
如果可以,我要俩个弟弟,有腹肌的那种。 咱三把日子过好才是最重要的。
custom 62285466562377872722
Signed 皮娅妹
全网机器人都卡顿了,你的机器人还好吗?
custom 62019356530520923243custom 62285466562377872721
Signed 皮娅妹
币安刚刚发布了初步调查报告,梳理了他们是如何被朝鲜黑客,盗取了 60 多亿美金。 某位币安软件工程师,在求职网站上挂着简历,结果一位自称项目总监的人,主动联系他,说有个潜在岗位想聊聊。 对方安排了一位 HR 跟他视频面试,真人露脸。为了让他放下戒心,这位 HR 还把自己的社交账号发给了他,上面有他本人的生活照和视频,看着就像真实存在的人。 然后到了第二轮面试,对方换到一个常用的聊天软件上,跟一位自称是这家公司 CEO 的人聊,但其实公司是假的。 等面试快结束时,对方让他下载一份代码题,作为技术测试,结果这位币安员工,在工作电脑上下载运行了它。 这份代码,在安装环节偷偷自动执行,把电脑上一个正常的开发工具 pyenv,换成了带木马的版本,然后跟黑客的服务器连上,还会自己清理痕迹。 就连币安当时的杀毒软件,也没查出来。 从这台电脑开始,朝鲜黑客一步步渗透内部,摸进了交易所的钱包系统,一个多月后币安被盗了 60 多亿美金。
custom 62285466562377872721
Signed 皮娅妹
洪马来发布声明 我无法放弃巨大利润,我决定重新开放赌场,让柬埔寨再次辉煌!!!
Signed 皮娅妹
金将军终于不在沉默了, 严重申明,这些被盗的币都跟我无关! 不要把什么锅都甩给我! 不过我觉得,将军还是在嘴硬罢了。 决定性的证据就是:Binance 和 Bitget 的被盗资金,现在流到了同一个地址。 再加上,社交攻击 & 作案手法 & 洗米手法高度相似,基本可以断定就是朝鲜搞的。
Signed 皮娅妹
今天休息吧,明天把群设置一下,再来
custom 62285466562377872724
Signed 皮娅妹
火山哥 就是 飞机的珠穆朗玛峰!
Signed 皮娅妹
Showing the 12 most recent of 157 posts we hold for @fuporiji. 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.
@fuporiji edited 2 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 14 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.
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.
@fuporiji named 8 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 11 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“富婆日记” (@fuporiji), 20,665 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/fuporiji.
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.