这个是真牛逼 笑死我了 小杨哥改行拍AV了 t.me/aiav/1308 嘴哥出现的时候 我是真的笑喷了……
custom 62019356530520923241
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
31,059subscribers
-6,371 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 | 26 September 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 26 September 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 why it has no browse page of its own yet.
@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 |
|---|---|---|
| 26 Sept 2026, 13:55 | 31,059 | -3,198 |
| 19 Sept 2026, 14:36 | 34,257 | -960 |
| 17 Sept 2026, 04:58 | 35,217 | -981 |
| 15 Sept 2026, 02:01 | 36,198 | -431 |
| 14 Sept 2026, 17:40 | 36,629 | +9 |
| 13 Sept 2026, 13:37 | 36,620 | -31 |
| 13 Sept 2026, 06:21 | 36,651 | -465 |
| 11 Sept 2026, 18:15 | 37,116 | -1,095 |
| 11 Sept 2026, 07:36 | 38,211 | +12,823 |
| 9 Sept 2026, 05:59 | 25,388 | -388 |
| 8 Sept 2026, 14:21 | 25,776 | -1,357 |
| 6 Sept 2026, 01:36 | 27,133 | +1,042 |
| 5 Sept 2026, 10:38 | 26,091 | -1,978 |
| 3 Sept 2026, 18:41 | 28,069 | +25 |
| 3 Sept 2026, 11:39 | 28,044 | -411 |
| 2 Sept 2026, 10:45 | 28,455 | -80 |
| 2 Sept 2026, 02:33 | 28,535 | -1,221 |
| 1 Sept 2026, 07:26 | 29,756 | -28 |
| 1 Sept 2026, 01:05 | 29,784 | -1,098 |
| 31 Aug 2026, 04:25 | 30,882 | first reading |
96 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 82 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 9 of 42 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 96 (29 July 2026 – 29 September 2026) |
| Views total | 138,510 |
| Reactions total | 35 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 20:41 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 29 September 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 3 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.
81 reactions across 21 posts, in 4 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6228546656237787272 | 31 | 38.3% | |
| custom 6228893354587856148 | 23 | 28.4% | |
| custom 6201935653052092324 | 21 | 25.9% | |
| custom 6059992687635864246 | 6 | 7.41% |
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 32 of the 96 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 81 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 96 most recent posts we hold, published 29 July 2026 to 29 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.
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 96 most recent posts we hold for this entry, published 29 July 2026 to 29 September 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.
这个是真牛逼 笑死我了 小杨哥改行拍AV了 t.me/aiav/1308 嘴哥出现的时候 我是真的笑喷了……
custom 62019356530520923241
Signed 皮娅妹
TG公群Discover 灰产群都开始给将军打工了 曾协助国际警察,破获多起案件的链上追踪博主 ZachXBT 发现,Bitget 被盗的那 3.87 亿美元加密货币,现在有一帮中国老哥,在帮朝鲜黑客洗钱。 这帮人胆子非常大,直接跑到他们用的那些跨链、兑换服务设施的公开客服群里,催促客服帮忙处理相关链上洗钱交易,一点都不藏着掖着。 ZachXBT 提到他跟踪这帮人很久了,每次朝鲜相关黑客作案成功后,都能看到类似的洗钱手法。 现在 Bitget 被盗资金,正在通过跨链桥,在不同的公链网络之间跳来跳去,然后进 Wasabi 这种混币器里清洗。 不过从图中来看,一些同行发现这些提问者,疑似是为朝鲜黑客洗钱的人,所以回了金正恩的表情包,来嘲讽。 他表示后面还会再放更多证据。
Signed 皮娅妹
tonkeeper并不安全,助记词居然是明文保存…… 最近关于利用ios的darksword漏洞攻击案例明显增加了,其实去年本漏洞的攻击就已经开始了,今年变得非常频繁才爆出来。 现在小黑客们已经开始攻击TG的nft圈了,昨晚就有不少+888被盗走。 在此建议大家,用于保存数字货币资产的iPhone手机立即更新最新的ios系统,至少要到ios26.7,能上iOS27最好。那些公司团队舍不得花钱,还给财务使用破旧的、二手的、淘汰的老版iPhone的赶紧换了,别舍不得几千块买个新iPhone。别等到被盗了才后悔。
Signed 皮娅妹
网友投稿: 极品担保是新币的一些小股东开的,当时新币已经知道自己要死亡了,然后开了一个熊猫担保和皇冠担保,然后这2个担保走的模式都不同,然后让一个走出来。 目前皇冠担保幕后也是新币担保的人这是确定的。
Signed 皮娅妹
刘欢去世…… 过个中秋都走了2个老艺术家咯
Signed 皮娅妹
Photo, posted without a caption
Signed 皮娅妹
济公去世了
Signed 皮娅妹
查U机器人 @chau 运营方 ,客服上个月开始就没上线了,id也死了,机器人今天出现卡死的问题,不知道出现什么问题了。 替用方案 :@v999 钱包助手
Signed 皮娅妹
9种常见盗U手段,看完别再把钱包送给骗子 辛苦赚来的U,可能一次误操作就全部清零。常见 套路主要有: 1. 恶意扫码授权 扫码后诱导你连接钱包、签名或授权,骗子便可能转走资产。单纯扫码未必有事,关键是别乱签名。 2. 尾号相似地址钓鱼 骗子制造相似转账记录,地址只差几个字符。转账不要只核对开头和结尾,最好使用地址白名单并先小额测试。 3. 不明APP窃取资料 假钱包、空投工具可能读取相册、剪贴板或设备信息。相册里若有助记词截图,资产很容易被盗。 4. 剪贴板病毒 复制助记词或收款地址时,恶意程序可能读取内容,甚至偷偷替换钱包地址。 5. 钓鱼Wi-Fi 陌生公共Wi-Fi可能把你引向假网站或恶意下载页面,转账和登录钱包时尽量使用自己的移动网络。 6. 摄像头偷拍助记词 在酒店、网吧等公共场所查看或抄写助记词,可能被监控或隐藏摄像头拍下。 7. 假钱包 图标和界面做得与真钱包几乎一样,一旦输入助记词,资产控制权就交给…
Signed 皮娅妹
为什么一夜之间都在推广做德州了? @NBDZ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ @NBDZ
Signed 皮娅妹
终于拿到新手机了 全新勃艮第酒红色还是太美了
custom 62285466562377872726
Signed 皮娅妹
出圈了,由于我经常发币圈骂孙哥,现在我成了币圈KOL了。 今天新加坡2049token 居然邀请我以 KOL身份去参加10月7-8日的活动,报销迪拜-新加坡往返机酒。我给他说了,必须阿联酋头等舱,不然姐不来!
Signed 皮娅妹
Showing the 12 most recent of 96 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 5 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.
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 2 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“富婆日记” (@fuporiji), 31,059 subscribers as measured 26 September 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.