Telegram RegisterThe public register of Telegram

Channel

盛丰担保公告

@sf444

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

29,833subscribers

-196 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002625268083
TypeChannel
Username@sf444
Description🌀 一键关注盛丰 https://t.me/addlist/mYt6qLFEW_5iMjhk
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/sf444

Growth

29,83330,02929,9318 August 2026 — 30,029 subscribers8 August 2026 — 30,029 subscribers9 August 2026 — 29,961 subscribers10 August 2026 — 29,864 subscribers11 August 2026 — 29,893 subscribers12 August 2026 — 29,833 subscribers8 August 202612 August 2026
6 measurements spanning 4 days, net -196. 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 29,804–30,058 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:3729,833-60
11 Aug 2026, 10:1229,893+29
10 Aug 2026, 07:3329,864-97
9 Aug 2026, 06:4229,961-68
8 Aug 2026, 06:4530,029no change
8 Aug 2026, 06:3630,029first reading

Engagement

13 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.99%
avg views ÷ 29,833 subscribers
Avg views / post
891
13 posts measured
Reaction rate
0.109%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 1 of 13 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 12 August 2026
Posts held13 (4 August 202612 August 2026)
Views total11,585
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 21: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.

What this channel posts

Photos
333
Videos
20
Links
30

Lifetime counters from Telegram’s own channel header, read 12 August 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
16s
Average length
16s

Measured directly from 1 video 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54292130372633405151100.0%

Custom emoji. One 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 count beside it isTelegram’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 1 of the 13 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 4 August 2026 to 12 August 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

12 Aug 2026, 16:35 UTC291 viewsread 12 August 2026

盛丰网通告: 本公司不对任何工作人员未授权(私下合作)任何业务进行兜底和承担赔付 包含私下借款,周转为由等一切可能性,并不意味着带有盛丰马甲就有权限和保障,请所有人注意‼️ 本通知为提前告知避免未来产生不可避免的矛盾和纠纷

Signed 盛丰网

11 Aug 2026, 17:24 UTC680 viewsread 12 August 2026
Photo

这个cs 5000都跑路 🆔ID: 8730535900 👤名称: CC 🌐用户名: @cfcf178 📱手机号: 🆔ID: 8282308808 👤名称: 朵朵 🌐用户名: @duoduo98158 📱手机号:

9 Aug 2026, 21:07 UTC917 views1 reactionsread 12 August 2026
Photo

盛丰网公告📣: 近一个月多次收到黑客攻击 钱包病毒,随着ai的进步关于钱包安全问题频发,为升级安全和审计 1:明日会更换盛丰部分钱包地址,上押客户在上下押金的同时必须跟群里 @sf88 @sf99 确认✅ 2:yypay对于大客户提现将会延迟5分钟左右到账,保障被骗人员及时拦截(今天就是因为盛丰网这边出款太快了,防止被 @shaoye 以卖号码为由骗取13750u 如果群里跟其他人确认下就不会发生 ✅ 3:请所有商户必须升级最新款苹果手机系统,不要购买任何网上的id,必须自己注册并且不能一个账号多用 ‼️ 4:不要毛毛躁躁不差那几分钟,能把钱包自己多签的人尽量多签证,小额建议走 @yypay 下发一样是1U提现 转账免费 ♥️ 5:大额玩家不要选择交易所,可以选择购买 Ledger 硬件钱包(必须法国🇫🇷发货)正版 6:其他建议需要大额套现的直接联系 @sf11 全国隔天送达,现金储备量充足频道 @sf2222 7

custom 54292130372633405151

Signed 盛丰网

9 Aug 2026, 12:35 UTC≈1,060 viewsread 12 August 2026
Photo

家人们,这20天有点衰,又被骗了13750u 不过这次还好,因为七天也被骗了27500u,哈哈哈哈😂

Signed 盛丰网

9 Aug 2026, 09:03 UTC880 viewsread 12 August 2026
Photo

曝光一组骗子 @xiayizu @shangyizu @kedaibiaoo 户名叫组长 跑资金盘,隔一段时间换个地址骗预付欠款24783 信息不回天天在线,原先收款地址是 TViTJm1JHQcqQVSwdQYeS9kPQWVvhPXm8t 汇款U的地址为 TBvhEyhnJxHzhWsKLbuqgeJvBeruUmiDJH 现在更换新地址TWoxkHMKFR2VEpaQsPLSEooj9zGQAjfXpB 大家注意现在这个新地址在跑量 有合作给他打过款的地址都注意下,他所有的U都汇向 TBvhEyhnJxHzhWsKLbuqgeJvBeruUmiDJH 有合作的直接卡,明吃他的资金,有问题来找我 @NanFengYiJiu

Signed 盛丰网

9 Aug 2026, 07:51 UTC830 viewsread 12 August 2026
Photo

合作几个月的商户 出现司法冻结7000元 原本规则1:3赔付 后与通道协商1:1赔付,一直拖着不处理,就说问问 几千块钱都不处理 有在合作的注意了,卡到就是赚到 骗子地址TCKg1qTjYn8t6GmRVQdmjqfXDLSGxQG9fB 以下发出的ID 全是他方人员 👤 8281501778 👦🏻 kk–Pay 🌐 @kk980113 🕑 最後同步時間 06/08/2026 👤 8628707150 👦🏻 小宝 👪 chem 🌐 @chemxiaobao 🕑 最後同步時間 06/08/2026 👤 6662055057 👦🏻 等风停 🌐 @bj88194 🇨🇳 Chinese 🕑 最後同步時間 13/07/2026 👤 8121119337 👦🏻 包子 🌐 @baozi7708 🕑 最後同步時間 25/05/2026 👤 5947457557 👦🏻 香槟 🌐 @aav168 🕑 最後同步時間 06/08/2

8 Aug 2026, 09:03 UTC918 viewsread 12 August 2026
Photo

🆔ID: 5447263166 👤名称: 万兴 卡卡西 🌐用户名: @kmk78988888 📱手机号: 🆔ID: 6787350621 👤名称: 万兴迷死她 🌐用户名: @wx777777777777 📱手机号: 🆔ID: 6434213454 👤名称: 汤姆哈迪 万兴 🌐用户名: @wx0000000009 📱手机号: 万兴支付 卡卡司法不赔付,加预付了叫开机不开看信息不回,剩下的清预付不清都是已读不回

7 Aug 2026, 22:00 UTC≈1,450 viewsread 12 August 2026
Photo

总结下本次中毒原因分析提醒支付商户需要注意‼️的一些事项 2026年8月7日支付圈内被黑客盗走150万U人民币价值1000万分别在前后10秒授权后被洗劫一空,深度分析🔍得出结论如下:早在4月份已经曝光过苹果系统漏洞被黑客攻破当时版本号风险漏洞为13-17版本风险,经历了4个月后黑客已经攻破到18-26系统区间,当前最新版本为26.6 事情始末:A手机系统版本号18,B手机系统版本号26.4 2台手机分别存放2个不同的钱包为什么会被同时前后10秒盗取? 最后排查发现A手机在浏览网站的时候被病毒无感授权获得秘钥(这种病毒根本无需你打开助记词和密码即可全部获取你的秘钥) 有人好奇为什么A手机跟B手机不同的钱包而且隔着几千公里会同时中招? 排查发现A手机因版本号太低中毒之后因为跟B手机同时登录一个ID导致B手机最新版同样中毒,一样泄露了私钥被盗 应该注意什么? 1:不要去点击任何网站,通过公开数据表明访问网站可以无感对版本号18

Signed 盛丰网

7 Aug 2026, 14:56 UTC933 viewsread 9 August 2026
Photo

🆔ID: 8764294351 👤名称: 叶一茜 🌐用户名: @pfeneg 📱手机号: 一直在提醒,为什么老板们还不在意这种骗子的骗术,希望大家不要放松警惕,上押必须必须必须 @sf88 @sf99 确认地址

6 Aug 2026, 14:58 UTC915 viewsread 9 August 2026
Photo

半年前 我家还在做三方时跟他合作承兑业务 打了一笔3000u的款拖欠半年 一直没还钱 还把我另一个号拉黑了 半年时间我一直没催过他 今天上号就看见他把我号拉黑了 有合作的抓紧卡 🆔ID: 6872457345 👤名称: 日富一日 🌐用户名: @rifuyiri88 📱手机号: 🆔ID: 8115943772 👤名称: 道天 🌐用户名: @Ayne_88888 📱手机号:

6 Aug 2026, 01:45 UTC900 viewsread 9 August 2026
Photo

👤 8430071808 👦🏻 畅盈 蓝鲸(此账号仅限商谈) 🌐 @cylanjing888 🕑 最後同步時間 03/08/2026 👤 8697671156 👦🏻 畅盈 罗杰 🌐 @cyzhifu79636 🕑 最後同步時間 14/07/2026 👤 7958517369 👦🏻 畅盈 心结(夜班客服)🌛 🌐 @changying8988 🕑 最後同步時間 05/07/2026 👤 8600312362 👦🏻 畅盈 口味王(白班客服)☀️ 🌐 @cyzhifu9899 🕑 最後同步時間 05/07/2026 👤 7361400489 👦🏻 畅盈 邓超 🌐 @changychaoge 🕑 最後同步時間 06/08/2026 畅盈支付已跑路地址 只进不出 有合作的卡住他的钱 TBCcShAqLU7jwqsdL9zaMPQ4kq6mTVBw1L

5 Aug 2026, 09:47 UTC831 viewsread 9 August 2026
Photo

@SF999 为盛丰网综合打造的全新“准客户”群组,进入需要门槛 😀😃😀😃😀😃 入群申请 担保用户 @sf88 @sf99 球盘中户 @sf55 @sf77 盛丰娱乐 @sf33 @sf44 现金用户 @sf11 数字用户 @sf00 @bnbb @ddss 综合特邀 @sf66 @sf22 系统用户 @sfxt

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

Citation-graph rank

Citation-graph rank — 200,934 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 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.

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

“盛丰担保公告” (@sf444), 29,833 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sf444.

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.