Telegram RegisterThe public register of Telegram
Telegram profile photo for 永盛支付24h零风险 自助跑分灰产项目

Channel

永盛支付24h零风险 自助跑分灰产项目

@YSZF222

On this record: Growth · Engagement · Posts · Citations · Cite this entry

14,094subscribers

-1,812 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001667710654
TypeChannel
Username@YSZF222
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 live28 August 2026
Measurements held20
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/YSZF222

Growth

14,09416,11115,102.57 August 2026 — 15,906 subscribers8 August 2026 — 15,933 subscribers9 August 2026 — 16,031 subscribers10 August 2026 — 16,006 subscribers11 August 2026 — 16,052 subscribers12 August 2026 — 16,104 subscribers13 August 2026 — 16,081 subscribers15 August 2026 — 16,111 subscribers16 August 2026 — 15,961 subscribers17 August 2026 — 15,797 subscribers18 August 2026 — 15,618 subscribers19 August 2026 — 15,432 subscribers20 August 2026 — 15,358 subscribers21 August 2026 — 15,051 subscribers23 August 2026 — 14,741 subscribers24 August 2026 — 14,550 subscribers25 August 2026 — 14,355 subscribers26 August 2026 — 14,322 subscribers27 August 2026 — 14,243 subscribers28 August 2026 — 14,094 subscribers7 August 202628 August 2026
20 measurements spanning 21 days, net -1,812. 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 13,791–16,414 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 12:5614,094-149
27 Aug 2026, 14:0414,243-79
26 Aug 2026, 13:2114,322-33
25 Aug 2026, 13:0214,355-195
24 Aug 2026, 13:4214,550-191
23 Aug 2026, 00:4814,741-310
21 Aug 2026, 15:3615,051-307
20 Aug 2026, 15:2315,358-74
19 Aug 2026, 16:1515,432-186
18 Aug 2026, 18:2215,618-179
17 Aug 2026, 18:3315,797-164
16 Aug 2026, 17:3315,961-150
15 Aug 2026, 00:0716,111+30
13 Aug 2026, 15:3816,081-23
12 Aug 2026, 14:1416,104+52
11 Aug 2026, 11:3616,052+46
10 Aug 2026, 08:5316,006-25
9 Aug 2026, 07:5416,031+98
8 Aug 2026, 08:3815,933+27
7 Aug 2026, 19:4615,906first reading

Engagement

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

ERR · 30 days
76.9%
avg views ÷ 14,094 subscribers
Avg views / post
10,800
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 22 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 August 2026
Posts held22 (16 February 202623 August 2026)
Views total43,380
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 04:43 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.

Recent posts

23 Aug 2026, 15:33 UTC≈4,560 viewsread 28 August 2026
Video

😀【做单教学】 🏪【下单平台】 😀【常见问题】 🫡【料性说明】 🫡【人工客服】 🫡【无法联系】 ------------------------------------- 目前为数不多的不用押,小风险项目,每天搞个3000块已经很不错了,其实就是让你去收赌徒的钱,有支付宝账号即可开工,花5分钟时间看一下教学就懂了,实在有什么不懂的可以问客服

16 Aug 2026, 14:17 UTC≈9,820 viewsread 28 August 2026

🔔通知:北京时间23:00-0:00 每天的该时间段是系统清算当日流水时间,会关闭所有通道,届时0.00将准时开启。请各位尽量避开该时间段进行洗金 — 永盛支付 🤡🤡🤡🤡🤡🤡🤡

5 Aug 2026, 18:52 UTC≈15,100 viewsread 28 August 2026
Photo

📣付款通知 使用支付宝备用通道支付时,请务必: ① 按订单商品价格手动输入(非欠费总额) ② 输入错误将导致订单无法自动生效。 如操作有疑问,请暂停并优先咨询客服。望相互转告。

1 Aug 2026, 11:32 UTC≈13,900 viewsread 28 August 2026
Photo

📣8月1日更新用户反馈,最近做单比较丝滑,可以依账号质量权重来适当调整接单数量,避免刚做就风控。有其他更好的领取办法我也会第一时间和大家分享 📣平台所有的支付方式都是各种生活缴费,游戏充值,合理规避大家的洗资风险,如遇到无法支付,风险提示,请根据指示操作或返回平台切换使用其他支付通道,所有通道都可正常来回切换使用,下发的都是支付宝口令 👉👉【点击进入24小时自助平台】 👉👉【点击观看新用户视频教程】

22 Jul 2026, 15:29 UTC≈15,600 viewsread 28 August 2026
Video

😀【做单教学】 🏪【下单平台】 😀【常见问题】 🫡【料性说明】 🫡【人工客服】 🫡【无法联系】 ------------------------------------- 目前为数不多的不用押,小风险项目,每天搞个3000块已经很不错了,其实就是让你去收赌徒的钱,有支付宝账号即可开工,花5分钟时间看一下教学就懂了,实在有什么不懂的可以问客服

11 Jul 2026, 15:45 UTC≈17,000 viewsread 28 August 2026

🔥温馨提示: 有些用户本身账户少于缴费或游戏充值,洗过几笔之后遇到风控暂时无法支付属于正常情况无需担心,这种切换使用其他通道或者换一个支付宝.微信.QQ账户进行支付即可 🥰🥰🥰

22 Jun 2026, 14:55 UTC≈23,100 viewsread 28 August 2026

🔔通知:北京时间23:00-0:00 每天的该时间段是系统清算当日流水时间,会关闭所有通道,届时0.00将准时开启。请各位尽量避开该时间段进行洗金 — 永盛支付 🤡🤡🤡🤡🤡🤡🤡

9 Jun 2026, 13:19 UTC≈26,500 viewsread 28 August 2026
Photo

📣6月9日更新用户反馈,最近支付宝风控严重,建议可以看下图片里我建议的方法,避免刚做就风控。有其他更好的领取办法我也会第一时间和大家分享 📣平台所有的支付方式都是各种生活缴费,游戏充值,合理规避大家的洗资风险,如遇到无法支付,风险提示,请根据指示操作或返回平台切换使用其他支付通道,所有通道都可正常来回切换使用,下发的都是支付宝口令 👉👉【点击进入24小时自助平台】 👉👉【点击观看新用户视频教程】

30 May 2026, 11:20 UTC≈25,100 viewsread 28 August 2026
Photo

✔️少部分口令领取的时候需要输入姓氏,卡密里面现在均标注的有,各位用户注意看清楚,平台早已进行补充,姓氏已经全部写在卡密里面了 ————————————————— 🫡官方唯一客服:@YSZF088 🫡限制发言私信联系: @YSZF88bot

15 May 2026, 14:57 UTC≈27,500 viewsread 28 August 2026

🔔通知:北京时间23:00-0:00 每天的该时间段是系统清算当日流水时间,会关闭所有通道,届时0.00将准时开启。请各位尽量避开该时间段进行洗金 — 永盛支付 🤡🤡🤡🤡🤡🤡🤡

11 May 2026, 07:34 UTC≈29,500 viewsread 28 August 2026
Photo

📣5月11日更新用户反馈,虽然这个兄弟非常爽快,但是建议大家还是要控制下领取口令的间隔时间,避免刚做就风控。有其他更好的领取办法我也会第一时间和大家分享 📣平台所有的支付方式都是各种生活缴费,游戏充值,合理规避大家的洗资风险,如遇到无法支付,风险提示,请根据指示操作或返回平台切换使用其他支付通道,所有通道都可正常来回切换使用,下发的都是支付宝口令 👉👉【点击进入24小时自助平台】 👉👉【点击观看新用户视频教程】

4 May 2026, 10:37 UTC≈25,200 viewsread 28 August 2026

🔔库存口令已补充!平台运营一切正常 持续稳定中! 感谢各位新老用户的陪伴,还在观望的朋友抓紧时间!机会不是每次都有,只要你执行力强,时间就是金钱💵想搞钱的速来,项目安全、稳定、长期!!!👍 再次声明我们仅此一家平台,本公司旗下无任何其他站点,谨防被骗,请认准官方唯一客服:@YSZF088 👉👉👉【点击进入24小时自助接料平台】 👉👉👉【操作教程】

Showing the 12 most recent of 22 posts we hold for @YSZF222. 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 — 125,251 of 1,622,561entries 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 15 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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“永盛支付24h零风险 自助跑分灰产项目” (@YSZF222), 14,094 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/YSZF222.

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.